On Sat, Mar 5, 2011 at 4:49 PM, Arne Babenhauserheide <arne_...@web.de>wrote:
> On Monday 14 February 2011 09:08:28 Michiel de Jong wrote: > > I may remember this incorrectly, but I think when I tried out freenet, > it's > > a desktop application, and not a localhost http service, right? > > Freenet is a localhost http-service. I already used it remotely quite often > by > just tunnelling the port via SSH to another computer. > > It uses public keys for identifying pseudonyms, and it automatically > loadbalances popular data (which is much faster than seldomly requested > data). > > Also there already is an example of a Javascript-based App on Freenet with > a > freenet extension as data provider (Sone, still experimental but already a > cool twitter/identi.ca replacement). > > → http://127.0.0.1:8888/USK@nwa8lHa271k2QvJ8aa0Ov7IHAV- > > DFOCFgmDt3X6BpCI,DuQSUZiI~agF8c-6tjsFFGuZ8eICrzWCILB60nT8KKo,AQACAAE/sone/28/ > > So it might be possible to create an unhosted freenet extension which > allows > using freenet as data server which the unhosted Javascript applications on > websites could use. > Still, since you're already distributing the web app, i don't see so much added advantage in separating the app from the data (which is what unhosted is all about). it makes sense to put javascript into freenet extension, but not so much putting it into unhosted web apps, i think? > > Best wishes, > Arne
_______________________________________________ Devl mailing list Devl@freenetproject.org http://freenetproject.org/cgi-bin/mailman/listinfo/devl
