• Blogging plugin, with bookmarks, photos, files, etc.
  
  

  ---

  
  Edited on 2007-03-23 14:01:34 by MatthewToseland [add a proposal for F2F stuff]
  
  Additions:
  - Better support for traditional F2F functionality: "Darknet" should become "Friends", you should be able to set trust levels on your peers, see their bookmarks, easily exchange instant messages (perhaps via e.g. a GAIM plugin), have shared folders, browse their Thaw indexes (and possibly their global queues) etc etc.
  
  

  ---

  
  Edited on 2007-03-23 13:50:36 by MatthewToseland
  
  Additions:
  - Ability to see (some of?) your friends (peers) indexes (or perhaps queues) combined with the ability to follow links between indexes
  
  

  ---

  
  Edited on 2007-03-22 16:06:14 by JeromeFlesch [Fix my english (minor minor minor change)]
  
  Additions:
  - Or you can be imaginative, all suggestions are welcome :)
  
  Deletions:
  - Or you can be imaginative, all suggestion are welcome :)
  
  

  ---

  
  Edited on 2007-03-22 08:17:38 by JeromeFlesch [Add some idea related to Thaw]
  
  Additions:
  - More plugins in Thaw :
  
  Deletions:
  - More plugins in Thaw :
  
  

  ---

  
  Edited on 2007-03-22 08:17:07 by JeromeFlesch
  
  Additions:
  - A moderable board system (similar to the Frost one, but moderable) : Some specs are already available here, but they *must* *be* *redesigned*. May be integrated in Thaw.
• More plugins in Thaw :
  • N2NTM (Node To Node Text Message) (would require some modifications in the node ; see the Thaw plugin 'PeerMonitor' for the UI)
  • A journal plugin : Keeping a trace of every downloads / insertions the user did
  • Or you can be imaginative, all suggestion are welcome :)
    
    

    ---

    
    Edited on 2007-03-19 18:34:41 by MatthewToseland [link to NewSpiderIdeas]
    
    Additions:
    - More work on searching Freenet: better UI, FCP support, support for searching Frost, multiple indexes, aggregating indexes, a plugin to construct an index site from a spider, etc. See NewSpiderIdeas.
    
    Deletions:
    - More work on searching Freenet via spiders and indexes. Currently we have: Various spiders, Librarian (search plugin which downloads an index published by a spider and searches within it, uses an old format, indexes don't scale), Thaw's indexes (these are basically file lists but the format can be used by spiders), Frost's filesharing system etc. Jobs to improve this: Port Librarian and the built-in spiders to use Thaw's XML-based index format. Support for huge indexes (splitting up indexes into multiple files). Support files as well as pages. Search for files in Frost messages and indexes. Make the spider easier to use - make it a full external plugin, make it able to save its progress to disk, etc. Include extra metadata (size, type, successfully downloaded, etc) from Thaw indexes and from downloading the files. Make an FCP interface, then a Swing GUI to interface to the core plugin. Etc.
• A freesite spider with automatic freesite categorization, based on meta tag information, and automatic insertion of new index editions, written in java, possibly with swing interface (integrated in Thaw ? :), or as a plugin. May produce either a freesite or a search index or both.
  
  

  ---

  
  Edited on 2007-03-19 17:54:07 by MatthewToseland [reorder and elaborate on easier means to join darknet]
  
  Additions:
  - Implement unit tests for the support classes of freenet and the (in)famous caught bugs. Unit tests for as much of the code as possible would be great, and the more advanced tests may involve setting up multiple nodes in the same VM with crypto turned off etc.
• Easier means to join the darknet. One-time invites, invites with only an IP and password, out of band verification, etc. Several threads on this on the tech list recently. Other suggestions: Auto-generated installer package including an invite which you can give away, plugins for IM clients to make adding darknet peers easy etc.
  
  Deletions:
  - Easier means to join the darknet. One-time invites, invites with only an IP and password, out of band verification, etc. Several threads on this on the tech list recently.
• Implement unit tests for the support classes of freenet and the (in)famous caught bugs
  
  

  ---

  
  Edited on 2007-03-19 17:50:19 by MatthewToseland [update easier-means-to-join]
  
  Additions:
  - Easier means to join the darknet. One-time invites, invites with only an IP and password, out of band verification, etc. Several threads on this on the tech list recently.
  
  Deletions:
  - Easier means to join the darknet. One-time invites, invites through passwords, etc. Look at recent threads on the tech list for inspiration.
  
  

  ---

  
  Edited on 2007-03-19 17:49:03 by MatthewToseland [try to combine spider ideas into a single blob]
  
  Additions:
  - More work on searching Freenet via spiders and indexes. Currently we have: Various spiders, Librarian (search plugin which downloads an index published by a spider and searches within it, uses an old format, indexes don't scale), Thaw's indexes (these are basically file lists but the format can be used by spiders), Frost's filesharing system etc. Jobs to improve this: Port Librarian and the built-in spiders to use Thaw's XML-based index format. Support for huge indexes (splitting up indexes into multiple files). Support files as well as pages. Search for files in Frost messages and indexes. Make the spider easier to use - make it a full external plugin, make it able to save its progress to disk, etc. Include extra metadata (size, type, successfully downloaded, etc) from Thaw indexes and from downloading the files. Make an FCP interface, then a Swing GUI to interface to the core plugin. Etc.
  
  Deletions:
  - More work on searching Freenet. We have the basics, but there is loads of work to do: Better integration of Librarian with fproxy, support for huge indexes, the new XML-based file format that Thaw uses, a better (easy to use) spider, possibly support for files and frost posts as well as pages ...
• A file spider that fetches keys from various sources (Frost messages, FUQID queue, the file utility mentionned above, etc.) make an index with additional meta-data (name, type, size, comment, date of last successfull download, etc...) and insert it.
  
  

  ---

  
  Edited on 2007-03-19 17:42:19 by MatthewToseland [invites]
  
  Additions:
  - Easier means to join the darknet. One-time invites, invites through passwords, etc. Look at recent threads on the tech list for inspiration.
  
  

  ---

  
  Edited on 2007-03-10 21:16:54 by MatthewToseland [wiki system not valid]
  
  Additions:
  - A wiki system on freenet. NOTE: This is being implemented at the moment by one of the developers. It is not therefore a possible SoC project.
  
  Deletions:
  - A wiki system on freenet
  
  

  ---

  
  Edited on 2007-03-10 21:11:21 by MatthewToseland [formatting]
  
  Additions:
  - Better NAT support: Implement UP&P, NAT-PMP, TURN and related technologies (we already have STUN and ARKs, but we need more). Note: Implement with an eye to security. We already use STUN, but STUN is centralised and we can't use the listen port for that reason, so it doesn't detect port forwards. UP&P may actually be a safer way to get our IP address. Would be good to be able to identify whether we are NATed without using centralised services (we get packets from X but not from Y...). Also note that according to this paper∞ and here∞, 80% of NAT routers are full-cone, so we may not need UP&P for port forwarding - but this hasn't been our experience so far, we need more data.
  
  Deletions:
  - Better NAT support: Implement UP&P, NAT-PMP, TURN and related technologies (we already have STUN and ARKs, but we need more). Note: Implement with an eye to security. We already use STUN, but STUN is centralised and we can't use the listen port for that reason, so it doesn't detect port forwards. UP&P may actually be a safer way to get our IP address. Would be good to be able to identify whether we are NATed without using centralised services (we get packets from X but not from Y...). Also note that according to [http://nutss.gforge.cis.cornell.edu/pub/imc05-tcpnat.pdf∞ this paper] and [http://www.guha.cc/saikat/stunt-results.php∞ here], 80% of NAT routers are full-cone, so we may not need UP&P for port forwarding - but this hasn't been our experience so far, we need more data.
  
  

  ---

  
  Edited on 2007-03-10 21:10:49 by MatthewToseland
  
  Additions:
  - Better NAT support: Implement UP&P, NAT-PMP, TURN and related technologies (we already have STUN and ARKs, but we need more). Note: Implement with an eye to security. We already use STUN, but STUN is centralised and we can't use the listen port for that reason, so it doesn't detect port forwards. UP&P may actually be a safer way to get our IP address. Would be good to be able to identify whether we are NATed without using centralised services (we get packets from X but not from Y...). Also note that according to [http://nutss.gforge.cis.cornell.edu/pub/imc05-tcpnat.pdf∞ this paper] and [http://www.guha.cc/saikat/stunt-results.php∞ here], 80% of NAT routers are full-cone, so we may not need UP&P for port forwarding - but this hasn't been our experience so far, we need more data.
  
  Deletions:
  - Better NAT support: Implement UP&P, NAT-PMP, TURN and related technologies (we already have STUN and ARKs, but we need more). Note: Implement with an eye to security. We already use STUN, but STUN is centralised and we can't use the listen port for that reason, so it doesn't detect port forwards. UP&P may actually be a safer way to get our IP address. Would be good to be able to identify whether we are NATed without using centralised services (we get packets from X but not from Y...). Also note that according to <a href="http://nutss.gforge.cis.cornell.edu/pub/imc05-tcpnat.pdf">this∞ paper</a> and <a href="http://www.guha.cc/saikat/stunt-results.php">here</a>∞, 80% of NAT routers are full-cone, so we may not need UP&P for port forwarding - but this hasn't been our experience so far, we need more data.
  
  

  ---

  
  Edited on 2007-03-08 17:44:30 by MatthewToseland [note on security]
  
  Additions:
  - Better NAT support: Implement UP&P, NAT-PMP, TURN and related technologies (we already have STUN and ARKs, but we need more). Note: Implement with an eye to security. We already use STUN, but STUN is centralised and we can't use the listen port for that reason, so it doesn't detect port forwards. UP&P may actually be a safer way to get our IP address. Would be good to be able to identify whether we are NATed without using centralised services (we get packets from X but not from Y...). Also note that according to <a href="http://nutss.gforge.cis.cornell.edu/pub/imc05-tcpnat.pdf">this∞ paper</a> and <a href="http://www.guha.cc/saikat/stunt-results.php">here</a>∞, 80% of NAT routers are full-cone, so we may not need UP&P for port forwarding - but this hasn't been our experience so far, we need more data.
  
  Deletions:
  - Better NAT support: Implement UP&P, NAT-PMP, TURN and related technologies (we already have STUN and ARKs, but we need more).
  
  

  ---

  
  Edited on 2007-03-08 15:33:55 by MatthewToseland
  
  Additions:
  - Implement new plugins providing for instance IM notification of completed requests from the global queue (first part of this is to make the node generate alerts when requests are completed, and to implement UI to fetch a currently unavailable site from the failure page and notify with a link when done; second is to tie this in to external plugins for email, IM, RSS notifications)
  
  Deletions:
  - Implement new plugins providing for instance IM notification of completed requests from the global queue
  
  

  ---

  
  Edited on 2007-03-07 20:05:53 by JeromeFlesch
  
  Additions:
  - A freesite spider with automatic freesite categorization, based on meta tag information, and automatic insertion of new index editions, written in java, possibly with swing interface (integrated in Thaw ? :), or as a plugin. May produce either a freesite or a search index or both.
  
  Deletions:
  - A freesite spider with automatic freesite categorization, based on meta tag information, and automatic insertion of new index editions, written in java, possibly with swing interface, or as a plugin. May produce either a freesite or a search index or both.
  
  

  ---

  
  Edited on 2007-03-07 19:57:39 by NextGens [advice the viewer to come and meet us on irc]
  
  Additions:
  Connecting to IRC (#freenet on irc.freenode.net) and asking one developer for guidance/advices is probably a good idea.
  
  

  ---

  
  Edited on 2007-03-07 19:54:31 by NextGens [reinstate toad's changes]
  
  Additions:
  - A freesite spider with automatic freesite categorization, based on meta tag information, and automatic insertion of new index editions, written in java, possibly with swing interface, or as a plugin. May produce either a freesite or a search index or both.
  
  Deletions:
  - A freesite spider with automatic freesite categorization, based on meta tag information, and automatic insertion of new index editions, written in java 1.4, possibly with swing interface, or as a plugin. May produce either a freesite or a search index or both.
  
  

  ---

  
  Oldest known version of this page was edited on 2007-03-07 19:52:13 by NextGens []
  
  Page view:

  The Free Network Project Summer Projects 2007

Example Proposal Ideas

• More work on searching Freenet. We have the basics, but there is loads of work to do: Better integration of Librarian with fproxy, support for huge indexes, the new XML-based file format that Thaw uses, a better (easy to use) spider, possibly support for files and frost posts as well as pages ...
• A freesite spider with automatic freesite categorization, based on meta tag information, and automatic insertion of new index editions, written in java 1.4, possibly with swing interface, or as a plugin. May produce either a freesite or a search index or both.
• A file spider that fetches keys from various sources (Frost messages, FUQID queue, the file utility mentionned above, etc.) make an index with additional meta-data (name, type, size, comment, date of last successfull download, etc...) and insert it.
• A wiki system on freenet
• Revamp the plugin system. We have the beginnings of a new plugin system, but it needs more work. A well-designed plugin system *should* enable untrusted plugin support, as well as simpler goals such as a clean API that doesn't involve calling into the guts of the node every time you want to fetch a page, and auto-updating of plugins over Freenet.
• A Python / C / Ruby / [your favorite language] library to interface with FreenetFCPSpec2Point0
• Packages for debian/redhat/etc
• A Freenet wrapper tailored towards being easy to install, run, and upgrade on OSX
• Denial-of-service-resistant link-level encryption via JFKi
• Transport plugins.
• Better NAT support: Implement UP&P, NAT-PMP, TURN and related technologies (we already have STUN and ARKs, but we need more).
• Revamp the cache to use an ARC∞ algorithm for greatly improved efficiency.
• Implement unit tests for the support classes of freenet and the (in)famous caught bugs
• Implement new plugins providing for instance IM notification of completed requests from the global queue
• Implement "update over mandatory" update

How to sign up

Requirements

• You must not overbook yourself. Working on your Freenet project should be your main activity for the entire summer.
• You must be willing to provide weekly status reports at a minimum
• You will be expected to learn how to use Subversion, Mantis, and other Freenet tools

Proposal Guidelines

Frequently Asked Questions

Page History :: 2007-03-23 14:04:26 :: Owner: MatthewToseland :: Search: