I propose that before 0.8.0, we separate the opennet question, and get the
wording right.
After 0.8.0, we need a big push for darknet.
Basically the objectives would be: (most of these are configurable)
- Make darknet secure by fixing the Pitch Black attack.
- Make it faster (more connections) by connecting to FOAFs and implementing
bloom filter sharing and download sharing.
- Make single-use invites we can give to people, and ensure they work despite
NATs by using our friends and FOAFs.
- Give friends a trust level and a visibility level.
- Share downloads and bookmarks persistently, and rewrite the UI to make chat
easier.
Some specific ideas:
Fixing the Pitch Black attack! Without this fix, darknet can be DoS'ed far too
easily.
Show our friends to our friends (configurable globally and per-friend). Make it
easy to add them as real friends, possibly with out-of-band verification ("call
them and exchange this random password"). Equivalent to social networking "you
might know these people".
Automatically connecting to our friends' friends (at HIGH not MAXIMUM) to get
enough peers quickly.
Create one-time invites we can send to people. Possibly include the installer.
Use our friends, and possibly our friends-of-a-friend, to help with
bootstrapping i.e. with dealing with NAT issues.
A per-peer trust level, and get rid of the friends security level in the wizard.
Mark each of our downloads, uploads and bookmarks with the level of trust of a
friend with whom we want to share it (none, high, normal, low).
Make a good user interface for our friends downloads, including a search
function and a list per friend.
Bloom filter sharing, but only on darknet.
Make downloading the shared files fast, using Freenet itself and direct
download from possibly multiple friends. (Note that this data is probably not
in their datastores, but only in their client caches and/or on disk).
Make f2f chat work considerably better.
Rewrite the darknet UI, in general: The friends page should show name,
connection status, any recent direct messages, the "status" (IMHO we need a
status as well as name; this should probably be a global message so we keep
prior ones?), a link to a page with all messages (which can of course be
deleted), bookmarks and files.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20101208/8b793847/attachment.pgp>
