minimal rebuttle

my minimum rebuttles, please add if you like.

we know the connection per node is random in the node.ref but we have
certain distances already decided in the private relay server side, the ircd
server is not on that public list.

Second, iip.invisiblenet.net is definitely not the iip server or even close,
it's not relevant, it's literally another node.

3rd, inform has no more information that what's in the node.ref list, all
it's duty is is to make sure routes are stable. Also, that's outside the US
either way, just by coincidence, but it doesn't hurt.

Chaining, you have the option of private relays, what we call neighbor
noding to chain your own hops by choice, and the future versions would like
to make this more user friendly.

Addressed is the plaintext into the ircd server, that doesn't eliminate
anonymity, as it's as good as a public channels knowledge of the text seen,
all we see is nick and words if we were to monitor. This is agreed that we
want to decentralize.

In response to the users becoming relays and timing attacks against dead
connections. If you look inside the node.ref at the network protocol, first
marker states closedelay: we use delay to assist against this attack, as it
delays the disconnect of a user at random intervals to make it not exactly
obvious of who is connected to what IP.

0x90
-----
I'd crawl over an acre of "Visual This++" and "Integrated Development That"
to get to gcc, Emacs, and gdb.  Thank you.