> This is tempting people to use this type of URL in hypertext documents,
> which is exactly what we don't want.  If someone really wants to access a
> specific Freenet server, they might as well go off and edit their ~/.freenet
> file.  I am completely for the freenet:<key> setup because it does not even
> *imply* that someone can stick a server name and port in there.  And fuck
> what the IANA says about URL formats.  Their just a centralized bureaucratic
> organization working in the interests of the corporations.  The only Internet
> standards body that I listen to at all is the IETF.

> Yes, our goal is to make documents fully decentralized.  By merely *allowing*
> a server name and port in the URL it is encouraging centralization.

We shouldn't throw it out just because it implies centralization.  If that
were the case, then we shouldn't have written http to freenet proxies.
(Greater risk of centralziation here)

Look, we need to clearly state that the server in the url is only for
special cases.  When a user doesn't have a local or close node to access
or the close nodes can't access the data.

It's meant for the user to type in, allowing for flexibility.  It
shouldn't be used for links from hypertext. (It can be blocked if
necessary from the webserver)
If you're setting up a website with links to freenet keys, there is no
incentive to tell your users to use a single entry point to freenet.


(stuff about http default port) 
> No, but that is because web usually uses that same port on all machines,
> which is the default port.
... 
> There is always ~/.freenet.
Yes, and we default to ~/.freenet.  I think we're in agreement about this
point.


How bout this idea:
We take the server in the URL as a *suggestion*.
The priority of who to contact first for the data is as follows:
1. Localhost
2. entries in ~/.freenet
3. entries in /etc/freenet.conf or appropriate master file
4. Suggested server in URL.

Fair enough?

-Larry


_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev

Reply via email to