On Tuesday 13 May 2008 20:33, Ian Clarke wrote: > 2008/5/13 Matthew Toseland <toad at amphibian.dyndns.org>: > > > Being bundled is one of our best hopes for getting Freenet widely > > > deployed, we need to be encouraging it, not looking for reasons not to > > > do it. Freenet is a platform on which we want people to build apps. > > > The best way to encourage that, given that Freenet isn't already > > > widely deployed, is to make it easy for those apps to bundle Freenet. > > > > Okay, how do we make it easy to bundle Freenet? > > Streamline the installation process, minimize the amount of user > interaction required - make it easy for an app's installer to provide > whatever startup information Freenet might need.
Heh, that's your answer to everything! :) If the app wants to specify *everything* then they can just bundle the files in their own installer, force their own settings, and not send the user to the wizard. This may in fact be the easiest option in most cases, certainly it's what they will do if they want freenet to be "invisible". We could maybe provide hooks to skip stages where appropriate otherwise. But launching a browser would distract from whatever it is they are installing with Freenet, no? > > > > > , because of the overhead (in every sense): > > > > - Exchanging noderefs. > > > > > > Not necessary if they use opennet - the app that bundles Freenet would > > > be responsible for encouraging the user to behave correctly. > > > > You think they would? :) > > Hopefully, either way, its their responsibility as the "primary" app, > not ours. Certainly, its no reason for us not to try to make Freenet > easy to bundle. I hope this isn't simply a cunning plan to reduce our support load. Right now that's not a big problem imho. > > > > It would be the responsibility of the app bundling Freenet to explain > > > these things to the user. > > > > Sure, but for a lot of apps, this is a blocker. For example, the mainstream > > version of Thingamablog can't realistically bundle Freenet. We are here > > talking about apps which are specifically written for Freenet, or plugins to > > mainstream apps, the plugin being specifically written for Freenet. > > Of course, not every app will bundle Freenet, but we need to make it > easy for those that can. > > Ian. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20080513/a3020180/attachment.pgp>
