From fad7fc95e073313ffd17d238d3c10d6fc24d4d4c Mon Sep 17 00:00:00 2001
From: ndurner <>
Date: Wed, 11 Mar 2009 21:59:57 +0000
Subject: [PATCH] add ND and libtahoe_webapi, FOSS'ification of the w32 client
[Imported from Trac: page GSoCIdeas2010, version 7]
---
GSoCIdeas2010.md | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/GSoCIdeas2010.md b/GSoCIdeas2010.md
index b0a9143..052206c 100644
--- a/GSoCIdeas2010.md
+++ b/GSoCIdeas2010.md
@@ -8,7 +8,10 @@ What could a smart student do in one summer, if they didn't need to worry about
* Shell friendly errors. When cli (the shell command tool) is failing, it would be good, for shell users, to have a nicer output in text format, not html/css. The latter could be kept for webgui errors only.
* 'tahoe sync'. The proposed #601 bidirectional sync option would be great for using tahoe as we would with dropbox (). 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 pratical 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 have many machines and alternate use between them, like a notebook, a home desktop and an office desktop, for instance.
* sshfs working properly in linux boxes. Yeah, my Fedora 9 isn't ok with trunk revision, it keep showing me the same first level directories in any level :)
+ * 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
# Mentors
Who is willing to spend about five hours a week (according to Google) helping a student figure out how to do it right?
-
+
+ * [Nils Durner](http://ndurner.de) (C/C++ work)