Single* Hop Onion Services (*singleness not guaranteed)
In general: stay away from qualitative or policy-based like hidden/public/secret/private, they only cause a problem later.
Stick to descriptive terms.
- alec On 23 Feb 2016 3:14 a.m., "Paul Syverson" paul.syverson@nrl.navy.mil wrote:
On Tue, Feb 23, 2016 at 01:17:42PM +1100, Tim Wilson-Brown - teor wrote:
Hi all,
It looks like Rendezvous Single Onion Services may not make it into tor
before the 0.2.8 code freeze in a few days' time.
One of the blocking issues is that it needs to be renamed.
Nick said on IRC: "RSOS is not really intelligible in the same way that Hidden Service
was."
"I want to make really sure that nobody configures this without realizing it's not anonymous"
So every name's a problem. I think "Hidden Service" was a bad name in hindsight in that it focused only on the location hiding and not on the provided authentication, and worse, it facilitated stupid pundits coining the misleading "Dark Web". That's why I like names like "Single-Onion Service" and "Double-Onion Service" that describe the technology not what it provides (which can also become a misnomer if other features of the service become prominent in use).
If you want to underscore in the name specifically the not-hidden property, then I suggest the best would be 'Rendezvous Located-Onion Service'. And Single Onion Service, would be 'Located-Onion Service'.
I think focusing in the name on such aspects is a really bad idea, but I offer this suggestion in case it is going to happen no matter what I think.
Does anyone have any suggestions? I'm out of names (and soon to start travel).
Bon Voyage, Paul _______________________________________________ tor-onions mailing list tor-onions@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions