On Wed, Sep 30, 2015 at 11:27 AM, Tom van der Woerdt wrote:
> Hey all,
>
> I'd like your thoughts and comments on this proposal.
>
> Tom
>
>
> PS: If you want to deliver them in person, I'm in Berlin.
>
>
>
>
> Filename: xxx-intro-rendezvous-controlsocket.txt
> Title: Load-balancing hidden service
On Wed, Oct 7, 2015 at 11:56 AM, David Goulet wrote:
> Hello tor-dev!
>
> While 028 bug triaging, we realized that we *really* need priorities to
> not be a banana field deprive of useful meaning. If you are unaware or
> don't remember, the priority field in a trac ticket can be:
>
> blocker c
> Secondly, you could probably simplify configuration by managing hidden
> service connections yourself. I believe the Stem library can do this?
Yup...
https://stem.torproject.org/tutorials/over_the_river.html
___
tor-dev mailing list
tor-dev@lists.torp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Vasilios Mavroudis wrote:
> Hello,
>
> I would like to introduce our project "Crux", which enables the
> computation of privacy preserving statistics on sensitive data. The
> project was developed at University College London (UCL) by me, in
> clos
This is a good proposal. Some bugs are higher-priority and affect
lots of users, but are really quite trivial and don't affect user
security (such as CSS bugs).
I'd add another trac change:
4) hide "milestone" field in query results, replace with "severity"
That way, we can quickly see bot
Hello tor-dev!
While 028 bug triaging, we realized that we *really* need priorities to
not be a banana field deprive of useful meaning. If you are unaware or
don't remember, the priority field in a trac ticket can be:
blocker critical major normal minor trivial
Those are "severities" *NOT* p
