Re: [tor-talk] Possible solution to next-gen onion services UX disaster

2017-03-14 Thread George Kadianakis
Lolint writes: > Hi, > > I just thought about a possible (partial) solution to solve the "UX disaster" > of next-gen onion services, namely the very long addresses. Tor Browser > already ships with HTTPS > Everywhere, and one can easily write rules that redirect from http or https > to onion s

Re: [tor-talk] Possible solution to next-gen onion services UX disaster

2017-03-12 Thread Alec Muffett
Having lived through a period where email addresses as we know them ( f...@example.com) were pre-emptively declared to be a usability disaster zone, and seeing the resultant train-wreck of X.400 addressing being foisted upon the UK academic community as a simple, clear, and intuitive replacement:

Re: [tor-talk] Possible solution to next-gen onion services UX disaster

2017-03-12 Thread Jonathan Marquardt
On Sun, Mar 12, 2017 at 01:50:09PM -0400, Lolint wrote: > Hi, > > I just thought about a possible (partial) solution to solve the "UX disaster" > of next-gen onion services, namely the very long addresses. Tor Browser > already ships with HTTPS > Everywhere, and one can easily write rules that r

[tor-talk] Possible solution to next-gen onion services UX disaster

2017-03-12 Thread Lolint
Hi, I just thought about a possible (partial) solution to solve the "UX disaster" of next-gen onion services, namely the very long addresses. Tor Browser already ships with HTTPS Everywhere, and one can easily write rules that redirect from http or https to onion services, as an example, https