On 31/01/2004, at 12:32 PM, David Masover wrote:
| Another good idea would be a 'freenet browser', something like Gecko or
No, it wouldn't. Gecko is for rendering (and I'd guess that WebKit is also). It takes html and renders it. Freenet currently uses html, and will probably continue to use it (at least for browsing).
I am quite aware of what WebKit and Gecko do.
It doesn't use http, of course, but adding a freenet:// URL style wouldn't change things too much, since you need the key first anyway -- it's going to be a long address no matter what. All that would do is allow for URLs to be to somewhere other than localhost, which can already be done (not sure if it has) by the server itself. This is better, because it doesn't require modifying a browser, and so far there's only one server.
Or 192.168.0.1 in my case.
And if you wanted to do such a thing, or the "privacy features auto-set", you would do it as a browser extension -- notice when it's a freenet url, and don't do things like caching it. For this, you'd probably just specify a particular host:port that is a "freenet url".
And how many browsers do that? Sure, I'm not sure about writing a plugin, since most of the time they can only add processing for different MIME types, whereas a different browser using a freenet:// protocol could connect through FCP and do things like simplify splitfiles, insertions and the like with an interface that normal users could use. Sure, there's things such as fiw, but it's not the easiest of things to use. Having the whole feature set in one application would make it a lot nicer.
-- Phillip Hutchings [EMAIL PROTECTED] http://www.sitharus.com/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
