The goal of my project is to improve the friend-to-friend
interaction. Improved interaction between friends hopefully stimulates
the growth of the darknet. At the moment adding darknet peers doesn't
give many visible benefits to the end user.

I have made it possible to recommend files and freesites to friends. At
the downloads page there is now a button "Recommend to friends".
Pressing the button allows the user to select which friends should
receive the recommendation. There is also a field for a description of
the file.

In a similar way it is also possible to recommend a bookmarked freesite
to friends. The functionality is available at three different places:
1: http://127.0.0.1:8888/?newbookmark=key&desc=desc&hasAnActivelink=yes
2: A share link next to the bookmark in the bookmark editor. The text
   should be replaced with an image
3: When adding a new bookmark in the bookmark editor

It's possible to send recommendations to friends that are offline. In
this case the recommendations are handle in the same way as text
messages to offline users are handled.

For each received recommendation a new UserAlert is created. The alerts
are visible at the normal place(http://127.0.0.1:8888/alerts).

Received recommendations and all other alerts are also accesable as
an atom feed file available at http://127.0.0.1:8888/feed

It is also possible to send and receive text messages and
recommendations of files/freesites over FCP. Support also exist for
receiving a FCPMessage when any type of UserAlert is registered with the
UserAlertMananger, but it only works properly for static alerts. I'm
currently working on an improved architecture where there is a
difference between an alert and an event.

I'm also working on how to make the progess of file transfers
between friends visible at the uploads/downloads pages. At the moment a
new BulkTransmitter is created and started when a friend has accepted a
file offer, but it's not possible to monitor the progress. The
transfers and file offers are also not persistence over node restarts.

To solve this I have created two new classes extending ClientRequest,
ClientSend and ClientReceive. The new classes are quite different
from ClientGet and ClientPut, they don't have a FreenetURI for example.
When the user wants to send a file a ClientSend is created and a file
offer is sent to the friend. When the friend receives the file offer he
creates a ClientReceive. If the offer is accepted the BulkTransmitter
of the ClientSend is started. I'm also working on a FCP interface for
this.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20090710/da8385b8/attachment.pgp>

Reply via email to