Re: [tor-dev] [RFC] Proposal for the encoding of prop224 onion addresses

2017-01-24 Thread s7r
Hello, David Goulet wrote: > >> >> OK thanks for the useful discussion. I identified at least three feedback >> points: >> >> + Screw base58 it's not gonna work. We stick to base32. Usability will >> be "restored" with a proper name system. >> >> + Move version byte to the end of the address

Re: [tor-dev] [RFC] Proposal for the encoding of prop224 onion addresses

2017-01-24 Thread Andreas Krey
On Tue, 24 Jan 2017 12:40:00 +, segfault wrote: ... > While the addresses are definitely too long to be fun to type, there are > still use cases where the addresses will be typed. For those cases you could print them with half-spaces or similar. You can even type them but need to remove them

Re: [tor-dev] [RFC] Proposal for the encoding of prop224 onion addresses

2017-01-24 Thread Linda Naeun Lee
On 2017-01-24 08:00, David Goulet wrote: On 24 Jan (14:27:43), George Kadianakis wrote: s7r writes: > Hello George, > > George Kadianakis wrote: >> Hello list, >> >> we've had discussions over the past years about how to encode prop224 onion >> addresses. Here is the latest

Re: [tor-dev] [RFC] Proposal for the encoding of prop224 onion addresses

2017-01-24 Thread Roger Dingledine
On Tue, Jan 24, 2017 at 12:40:00PM +, segfault wrote: > But maybe it would help to separate them into groups of 4 characters, > separated maybe by a dash, which would make them look like this: > > > tbi5-tdxb-osio-tpha-wjyu-7f5p-w5tl-nvbv-fjrj-7mes-kbsn-wr2b-qbu2-t4gg.onion Check out

Re: [tor-dev] [RFC] Proposal for the encoding of prop224 onion addresses

2017-01-24 Thread Taylor R Campbell
Date: Tue, 24 Jan 2017 12:40:00 + From: segfault But maybe it would help to separate them into groups of 4 characters, separated maybe by a dash, which would make them look like this:

Re: [tor-dev] [RFC] Proposal for the encoding of prop224 onion addresses

2017-01-24 Thread David Goulet
On 24 Jan (14:27:43), George Kadianakis wrote: > s7r writes: > > > Hello George, > > > > George Kadianakis wrote: > >> Hello list, > >> > >> we've had discussions over the past years about how to encode prop224 onion > >> addresses. Here is the latest thread: > >>

Re: [tor-dev] [RFC] Proposal for the encoding of prop224 onion addresses

2017-01-24 Thread segfault
Hi George, George Kadianakis: [...] > [D3] Do we like base32??? > > In this proposal I suggest we keep the base32 encoding since we've been > using it for a while; but this is the perfect time to switch if we feel > the need to. > > For example, Bitcoin is using base58

Re: [tor-dev] [RFC] Proposal for the encoding of prop224 onion addresses

2017-01-24 Thread George Kadianakis
chelsea komlo writes: > Hey George, > > Thanks for sending this and summarizing everything! > >> [D1] How to use version field: >> >> The version field is one byte long. If we use it as an integer we can >> encode 256 values in it; if we use it as a bitmap we

Re: [tor-dev] [RFC] Proposal for the encoding of prop224 onion addresses

2017-01-24 Thread George Kadianakis
s7r writes: > Hello George, > > George Kadianakis wrote: >> Hello list, >> >> we've had discussions over the past years about how to encode prop224 onion >> addresses. Here is the latest thread: >> https://lists.torproject.org/pipermail/tor-dev/2016-December/011734.html >> >>