On 12/01/10 03:56, steve oliver wrote: > --------------------- Implementation --------------------- > > Instead of linking to a specific node/computer like the DNS system does > (which we don't want to do even if we could), it would be a redirect to an > existing site inserted using an SSK, etc. It would also "mask" the real SSK > URL much like the DNS system masks the IP of a public website. > > To enable this to work without building in central points of failure or > control over the whole thing (or censorship), the system would not have a > true "root" as the DNS system does, instead the node would support an > arbitrary number of FreeNS lookup and mapping spaces, which would be SSK > URLs containing a specific filename in a specific format (XML?), that would > include key pairs of FreeNS names mapped to specific SSK URLs. These tables > would be updated automatically in the background by the node, much like we > update new editions of activelinks periodically, or check for new Freenet > builds.
Hmm, could you please provide some more details? How do you spread this information in such a way that can filter out spam attacks? > New installs could include a default FreeNS lookup space much like we > include default activelinks, including mappings for common freesites to > enable out-of-the-box use. Users could then add one or more community > maintained FreeNS lists after installation. Of course this may introduce the > possibility (near guarantee, actually) of collisions, but perhaps the system > could include a relative trust system using WoT, where FreeNS domains > returned by one list are trusted more than another, or perhaps we just warn > the user that the freesite or filename they clicked points to two different > SSKs, and let them pick if a clearly trusted mapping does not exist. > > --------------------------------- Possible enhancements > --------------------------------- > > The second part of the "domain" could potentially serve as a namespace for > the backend implementation of the name lookup somehow > > Individual nodes could maintain a list of "known bad" and "known good" > FreeNS mappings, and publish them alongside WoT identity trust lists, this > may enable the entire thing to function decentralized with no true "lists" > at all. > > If we are making use of WoT, the creation of a FreeNS name for a newly > inserted Freesite could be announced simply by adding it to whatever message > digests we're already inserting from Freetalk for the day, others would pick > it up and propagate it in their own decentralized FreeNS lists. > I'm currently working on a decentralised search system (which gets its security from the WoT). This could effectively be used as a name-allocator - the process of assigning tags to documents is the same as assigning names to documents, only the names are more unique. The problem of "multiple results for the same name" is then solved just like a normal search request - you return multiple results for it, with results scored and ranked like for any other query. (if you want to have a live chat about this, come to #freenet on freenode IRC) X
