Re: Distributed Drive and Increased Usage

"Ian Clarke" <[email protected]>
Newsgroups gmane.network.freenet.technical
Message-ID <[email protected]>
2008/5/13 Matthew Toseland <toad-EI5O+8PHWbJeeLb3ft/[email protected]>:
>  > 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.

>  > > , 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.

>  > 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.

-- 
Email: [email protected]
Cell: +1 512 422 3588
Skype: sanity
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.