diff --git a/GSoCIdeas2010.md b/GSoCIdeas2010.md
index 6b738a9..e7bb829 100644
--- a/GSoCIdeas2010.md
+++ b/GSoCIdeas2010.md
@@ -1,5 +1,7 @@
 # Ideas
 What could a smart student do in one summer, if they didn't need to worry about getting a summer job to pay the bills?
+
+## Improvements to Tahoe
  * Dealing with NAT, ideally making it as easy to ignore as possible (taking advantage of upnp-igd and Zeroconf NAT-PMP)
  * Opportunistic grid membership:
    * Dynamic share migration to maintain file health
@@ -8,11 +10,16 @@ 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
+
+## Deep Security Issues
+Want to help make Tahoe support strong security properties which advance the state of the art of security and usability?  It isn't easy!  To tackle these you'll need to think carefully and to integrate security and usability, which are two halves of the same coin.  But you'll have some excellent mentors and the support of a wide community of interested security hackers. 
+
  * 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.
+ * Tahoe Cryptography Fu (Zooko: add specific projects here)
 
 ## 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?)