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

Re: [tor-talk] A proposal for redesigning Tor-Launcher for better usability

2017-03-12 Thread Nicolas Vigier
On Sun, 12 Mar 2017, irykoon wrote: > > # Related Research > A detailed and published > [research](https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-58.pdf) > conducted in 2015 also addressed the problem [1]. In that research, the > researchers firstly did a small-scale user behavior

[tor-talk] A proposal for redesigning Tor-Launcher for better usability

2017-03-12 Thread irykoon
Hi everyone! I am Iry. Currently, I have been working on the anon-connection-wizard, a Python-clone of the Tor Launcher which aims at providing Tor users with a graphical instruction on configuring the Tor. During the development process, I realized some problems shared by both

[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,

Re: [tor-talk] exit probability 0.0000%

2017-03-12 Thread Udo van den Heuvel
On 12-03-17 00:27, scar wrote: > My node also was used recently for dorkbot traffic, please see my > message on Fri, 10 Mar 2017 15:04:02 > -0500 for details and reply there if can so we can keep the information > together. I got similar 'info' from my ISP as