Oh, Nathan already suggested that

[Imported from Trac: page GSoCIdeas2010, version 20]
zooko 2009-03-17 01:35:55 +00:00
parent 5bfae823aa
commit 60143bc7f0

@ -13,13 +13,12 @@ What could a smart student do in one summer, if they didn't need to worry about
* Various web frontend applications:
* An interactive tree browser web frontend.
* A blog-like app (perhaps addressing tiddly wishlist items)
* Port another light-weight server open source web app to Tahoe+javascript (calendar, photo album)
* 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
* Special scheme handling in browser add-ons
* 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.
* Retarget a webapp such as [Bespin](https://bespin.mozilla.com) to store itself on a Tahoe grid instead of on a custom (Bespin-specific) server.
# Mentors
Who is willing to spend about five hours a week (according to Google) helping a student figure out how to do it right?