tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

remove Building Things On Top of Tahoe -- it lives on wiki:GSoCIdeas (or its descendants do) 

[Imported from Trac: page GSoCIdeas/Notes, version 10]
zooko 2010-03-17 04:03:57 +00:00
parent 2a0138b783
commit fd18eb5567
1 changed files with 1 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
GSoCIdeas/Notes.md

@ -75,19 +75,4 @@ jumping-off point for health is #778.
* improve the FUSE frontend ([source code]source:contrib/fuse). [Tickets labelled 'fuse'](http://allmydata.org/trac/tahoe-lafs/query?status=!closed&order=priority&keywords=~fuse)
* integrate Tahoe-LAFS with the GVFS Gnome virtual filesystem
* Explore running a Tahoe-LAFS grid over [Tor](https://torproject.org) or [I2P](https://i2p2.de) to provide anonymity to servers and/or clients.
* Rescue the neglected C client library [libtahoeclient_webapi](http://allmydata.org/trac/libtahoeclient_webapi).
## Building Things On Top Of Tahoe
Difficulty: easy to hard, depending on project choice and how far you want to push it
There are a lot of applications that could potentially make good use of Tahoe replacing the typical centralized storage of flat files or SQL databases. Currently supported projects include [TiddlyWiki](http://www.tiddlywiki.com/) (one of the Tahoe developers hosts his blog using [TiddlyWiki stored in Tahoe](http://allmydata.org/trac/tiddly_on_tahoe)), [Hadoop](http://hadoop.apache.org/), and [a number of others](RelatedProjects).
There are still many useful and interesting things that have yet to be built using Tahoe. Perhaps the most promising is in the area of web applications; what applications can you think of that could make use of a highly reliable filesystem accessible from both desktops and [ <http://github.com/ctrlaltdel/TahoeLAFS-android> handheld devices]? Keep in mind that Tahoe's architecture allows sharing and delegation opportunities that are difficult or impossible to implement using other backends. Some ideas people have suggested include a calender or photo album, or porting Mozilla's [Bespin](https://bespin.mozilla.com) editor).
Nathan Wilcox wrote most of interactive tree browser frontend in JavaScript; what interesting ways might this be extended?
This is in some ways the most interesting area for development as it combines security and distributed systems problems with providing a user interface that lets a person who isn't particularly security minded operate safely by default. This is a hard problem, but offers great rewards in terms of learning, and even the ability to break new ground in safe-by-default interface design.
Required skills: HTML and JavaScript for web applications. For other tie-ins, will depend on the base project (for instance porting the git DVCS to run on Tahoe would good C-fu, with git experience helpful).
* Rescue the neglected C client library [libtahoeclient_webapi](http://allmydata.org/trac/libtahoeclient_webapi).