> To summarize the benefits of your system: > > Prevention of "future spamming" > Prevention of namespace conflicts > > Why is this better than the current client-side solutions for these > problems? > > The solution to future spamming is to have the index maintainer maintain a > prefix index in which he periodically places the prefix for a key > index. So if you want to publish to Steve's Key Index, you go to the key > index "SSK at blalalajjajsjsjsk/date", read out the prefix, say "qodoa". Then > you insert your key into qodoa-x. > > The solution to namespace collisions is to use SSK indices.
What you've just described above is very similar to what I call a code file. Part of the purpose of DSKs is to automate the process of looking up this code, and to adopt a standard convention for handling data submissions. DSKs could even be done client-side if that's what you prefer. The DSK makes things transparent/automatic and standardized. ============================================================= = Adrian Lopez <adrian2 at caribe.net> ========================= = if (ideals != reality) return frustration; ================ ============================================================= _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl >From devl-admin at freenetproject.org Wed Apr 11 02:10:04 2001 Return-Path: <devl-admin at freenetproject.org> Received: from hawk.freenetproject.org (postfix@[4.18.42.11]) by funky.danky.com (8.9.3/8.8.7) with ESMTP id CAA31329 for <danello at danky.com>; Wed, 11 Apr 2001 02:10:03 -0400 Received: from hawk.freenetproject.org (localhost [127.0.0.1]) by hawk.freenetproject.org (Postfix) with ESMTP id 751EF581B6; Tue, 10 Apr 2001 22:52:05 -0700 (PDT)
