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. _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl >From devl-admin at freenetproject.org Wed Apr 11 01:39:08 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 BAA31161 for <danello at danky.com>; Wed, 11 Apr 2001 01:39:06 -0400 Received: from hawk.freenetproject.org (localhost [127.0.0.1]) by hawk.freenetproject.org (Postfix) with ESMTP id 6507958175; Tue, 10 Apr 2001 22:21:05 -0700 (PDT) Delivered-To: devl at freenetproject.org Received: from mta6-rme.xtra.co.nz (mta6-rme.xtra.co.nz [203.96.92.19])
