Re: [tor-dev] prop224: What should we do with torrc options?

2016-11-24 Thread ckomlo
Hi, > > 2) It also means we create an option that will get deprecated once v2 is >phased out so we are adding a "temporary" option for users to "keep >creating v2 addresses" but then will be useless and we'll deprecate and get >a whole lot confusing if for instance v4 or v5 happens in

Re: [tor-dev] prop224: What should we do with torrc options?

2016-11-24 Thread teor
> On 25 Nov. 2016, at 03:40, David Goulet wrote: > > On 24 Nov (11:13:06), teor wrote: >> >>> On 24 Nov. 2016, at 11:04, Yawning Angel wrote: >>> >>> On Thu, 24 Nov 2016 01:43:15 +0200 >>> s7r wrote: I agree that this would be "the technical way" to do it, but real world usability

[tor-dev] CollecTor Release 1.1.1

2016-11-24 Thread iwakeh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi there! another small CollecTor version is available: https://dist.torproject.org/collector/1.1.1/ The release provides two changes * CollecTor now handles a rare internal error gracefully instead of escalating the problem [0], and * hid

Re: [tor-dev] prop224: What should we do with torrc options?

2016-11-24 Thread David Goulet
On 24 Nov (11:13:06), teor wrote: > > > On 24 Nov. 2016, at 11:04, Yawning Angel wrote: > > > > On Thu, 24 Nov 2016 01:43:15 +0200 > > s7r wrote: > >> I agree that this would be "the technical way" to do it, but real > >> world usability kind of prevents us to do it this way. The spec for > >>