4 ms·

There is a pluggable name resolution proposal: https://gitweb.torproject.org/torspec.git/tree/proposals/279-naming-layer-api.txt https://gitweb.torproject.org/

by nikcub 9y ago

There is a pluggable name resolution proposal: https://gitweb.torproject.org/torspec.git/tree/proposals/279-naming-layer-api.txt https://gitweb.torproject.org/torspec.git/tree/proposals/279... You'd be able to run namecoin and other systems edit: to add, I haven't yet completely bought into the new onion services. I like a lot of the security improvements, but it is really going to depend on how name resolution works and how authenticating endpoints will work for users. Running a pluggable name resolution system means we can try out different solutions and see which takes off organically and practically.

asn_tor 9y ago
Yes indeed the naming issue is important and needs to be addressed. We are currently pretty busy with stuff so we haven't even started implementing the aforementioned proposal (or considered whether it's a good idea). BTW check out this link for some survey results that point out that onion length might not matter so much since the legacy onions were already unrememberable: https://lists.torproject.org/pipermail/tor-dev/2017-September/012464.html https://lists.torproject.org/pipermail/tor-dev/2017-Septembe... Cheers and thanks for keeping the discussion fruitful :)