[tor-dev] UX tag

Hello devs, May I encourage you to add "UX" tag (keyword) to the tickets you're filing or working on that are related to usability in any ways? This is to get a sense of how many tickets and what workload is related to usability in tor-related products. So I want to humbly ask you to use the tag

Re: [tor-dev] Tor Messenger Beta: Chat over Tor, Easily

* Malte: > Hell yeah! What was up with the previous (unannounced) beta version that was > already lying on dist.torproject.org? We were sorting out some branding issues :) And yes, that was never announced. > I would like to see OMEMO (based on Axolotl) get more adoption. Right now >

Re: [tor-dev] Tor Messenger Beta: Chat over Tor, Easily

https://trac.torproject.org/projects/tor/ticket/17457 -- Sukhbir ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Update of prop#250: Random Number Generation During Tor Voting

Jesse V writes: > David, > > I'm in the midst of reworking my OnioNS design around prop250 (and the > security > analysis therein) and as far as I can tell these changes make sense. I like > the > 00:00 -> 24:00 change as it's more intuitive as you said. I was at first

Re: [tor-dev] Bridge Guards (prop#188) & Bridge ORPort Reachability Tests

Tim Wilson-Brown - teor transcribed 19K bytes: >> On 12 Sep 2015, at 17:26, isis wrote: >>> Tim Wilson-Brown - teor transcribed 23K bytes: On 10 Sep 2015, at 17:01, isis wrote: 2.b. If it is useful to people, then the best way I can

Re: [tor-dev] [proposal] New Entry Guard Selection Algorithm

Hello Isis, thanks for the proposal. Looks good! I think adding the logic for greater reachability of people behind FascistFirewalls makes sense and will be very helpful. Some comments on the proposal inlined below: > Filename: xxx-guard-selection.txt > Title: New Guard Selection