Re: [tor-dev] Prop-279 for Onion Alternative Name Representations (Re: Error-Correcting Onions with Bech32)

2018-01-12 Thread meejah
Yawning Angel writes: > It's worth keeping in mind that no one to my knowledge has implemented > prop 279 in the tor code itself, though there is (IIRC) a python kludge > that kind of allows development. Said kludge is here, for completeness:

Re: [tor-dev] Prop-279 for Onion Alternative Name Representations (Re: Error-Correcting Onions with Bech32)

2018-01-01 Thread Yawning Angel
On Mon, 1 Jan 2018 08:45:57 + nullius wrote: > On 2017-12-31 at 10:48:52 +, Yawning Angel > wrote: > >This is pointless because internationalized domain names are > >standardized around Punycode encoding (Unicode<->ASCII), and said > >standard

Re: [tor-dev] Prop-279 for Onion Alternative Name Representations (Re: Error-Correcting Onions with Bech32)

2018-01-01 Thread nullius
On 2017-12-31 at 10:48:52 +, Yawning Angel wrote: This is pointless because internationalized domain names are standardized around Punycode encoding (Unicode<->ASCII), and said standard is supported by applications that support IDN queries. I am firmly against

Re: [tor-dev] Prop-279 for Onion Alternative Name Representations (Re: Error-Correcting Onions with Bech32)

2017-12-31 Thread Yawning Angel
I commented on the ticket but I'll do it here for completeness sake: On Sun, 31 Dec 2017 10:12:53 + nullius wrote: > I also proposed changes to permit the UTF-8 characters required for > representing names in languages other than American English, and some > other

[tor-dev] Prop-279 for Onion Alternative Name Representations (Re: Error-Correcting Onions with Bech32)

2017-12-31 Thread nullius
On 2017-12-31 at 14:23:39 +1100, teor wrote: Please read the naming layer API proposal before writing your proposal: https://gitweb.torproject.org/torspec.git/tree/proposals/279-naming-layer-api.txt In particular, if you added a unique top-level domain (.bech?), you would