-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > Yea, already thought about that one. I'll make it perfectly clear that > including specific nodes in hypertext is *forbidden* in the protocol. Making something forbidden in a protocol, but still supported in code does not make it *not happen*. Abuse of the NNTP protocol is an example.
> How do we enforce this? We'll basically have two ways of interpreting a > URL depending on how it's entered. All URLs in hypertext go through a > special function that disallows specific node references. Riiiiight.. Thats kludgy at best. Thats like saying, "I want to keep people out of my yard, so I'll build a fence. But I want to be able to let people in sometimes, so I'll leave a section out. But to keep bad people out, I'll hire someone to watch the hole in the fence" Never mind that he might fall asleep or be bought off. > So assuming that a good >90% of people don't hack up the webbrowser to get > around this (there's no good reason for it) this will be a strong > incentive to make it comply with our URL rules. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5FwJOpXyM95IyRhURAs2bAKDUT9RStFCF92KueFiUwmefp+xOmACg0jAO szQNkNxntRwVaDx4M0BWbg8= =sYlV -----END PGP SIGNATURE----- _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
