On Thu, Jun 02, 2011 at 01:06:35AM -0400, Robert J. Hansen wrote:
> > reviewing, testing, and deploying a significant change to the architecture
> > of the SKS keyserver network...
>
> It should be noted, incidentally, that these changes would mean it would
> no longer be the SKS network.
>
> The SKS network is, literally, the *synchronizing* keyserver network. If
> the system gets changed so it's no longer synchronizing but
> redundancy-reducing, we really need to call it something else.
Weeeelll... technically it's still synchronizing, it's just synchronizing
different subsets to different servers.
Ooooh, there's a name... the SubSet Synchronizing Keyserver Network --
SSSKS. The logo would *have* to be a snake with a cough.
> So long as we say it's "just a modification to SKS," that lets people
> think the change is small. Once we say "invent an entirely new keyserver
> protocol because SKS is clearly not what these people want", that gives an
> idea of the scope involved.
Very true.
- Matt
--
[O]ne of the requirements for writing code in Python seems to be that one
spends as least as much time promoting the language as coding in it.
-- Matt Roberds, in the Monastery
_______________________________________________
Sks-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/sks-devel
