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

edits 

[Imported from Trac: page GSoCIdeas2010, version 26]
zooko 2009-03-17 02:03:12 +00:00
parent ee903e8de1
commit 72dc191afa
1 changed files with 10 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
GSoCIdeas2010.md

@ -8,13 +8,6 @@ What could a smart student do in one summer, if they didn't need to worry about
* 'tahoe sync'. The proposed #601 bidirectional sync option would be great for using tahoe as we would with dropbox (<http://www.getdropbox.com/>). Like the latter, the user could have a daemon which keeps things in sync in pollings within a one or two seconds schedule (maybe using inotify for uploads). In practical terms an user could have many machines pointing to the same tahoe:dir, each machine mapping this resource to a local directory, and all these machines could then have their local copies in sync, via tahoe:dir. I think this is good when someone has many machines and alternates use between them, like a notebook, a home desktop and an office desktop, for instance.
* Help with the C client library [libtahoeclient_webapi](http://allmydata.org/trac/libtahoeclient_webapi)
* Make the [Windows client](http://allmydata.org/trac/tahoe-w32-client) use only free open-source software
* Various web frontend applications:
* An interactive tree browser web frontend.
* A blog-like app (perhaps addressing tiddly wishlist items)
* *Or*, extend and improve the `tiddly_on_tahoe` implementation
* *Or*, retarget the [TiddlyWeb](http://tiddlywiki.org/wiki/TiddlyWeb) to use Tahoe as its backend storage?
* Port another light-weight server open source web app to Tahoe+javascript (calendar, photo album, [Bespin](https://bespin.mozilla.com))
* Fix Same-Origin-Policy design issue. Web content from different authors can interact in unintended ways in the victims browser, such as Javascript iterating over open windows, or peeking at a referrer header. Before this project is undertaken, the problem description and proposed solutions need careful design review and consideration! The solutions should be considered prototypes and should be backwards compatible with the Tahoe network.
* Domain Mangling approaches:
* HTTP proxy approach
@ -22,6 +15,16 @@ What could a smart student do in one summer, if they didn't need to worry about
* CAJA approach: Require all Javascript to pass the CAJA verifier in the Tahoe web frontend, then create an interface to the tahoe webapi which matches the intended capability semantics.
* Explore running a Tahoe grid over [Tor](https://torproject.org) or [I2P](https://i2p2.de) to provide anonymity to servers and/or clients.
## Building Things On Top Of Tahoe
* an interactive tree browser web frontend in JavaScript (Nathan has written most of one -- what can it grow into?)
* a blog-like web app (perhaps addressing tiddly wishlist items)
* extend and improve the `tiddly_on_tahoe` implementation
* retarget the [TiddlyWeb](http://tiddlywiki.org/wiki/TiddlyWeb) to use Tahoe as its backend storage
* Port another light-weight open source web app to Tahoe+javascript (calendar, photo album, [Bespin](https://bespin.mozilla.com)).
##
# Mentors
Who is willing to spend about five hours a week (according to Google) helping a student figure out how to do it right?
<br>