On 1/4/19, V wrote:
> "crypto" "security" "sofware dev" "support" fud re v2
"Hey, here's v2, it uses older crypto and mechanics that
are not as robust etc as v3... However v2 offers useful features
for many users, and those features are not yet available in a
newer design (volunteers to create
On 01/03/2019 11:06 PM, teor wrote:
> Hopefully, we'll have feature parity on v3 very soon. And then
> apps will migrate from v2 to v3 (or dual-stack).
>
> It's best if we transition slowly, in a planned manner. But we do
> need to transition in the next few years. Otherwise, we might have
>
On 01/04/2019 09:17 AM, s7r wrote:
> Mirimir wrote:
>> On 01/03/2019 11:06 PM, teor wrote:
>>
>>
>>
>>> Hopefully, we'll have feature parity on v3 very soon. And then
>>> apps will migrate from v2 to v3 (or dual-stack).
>>>
>>> It's best if we transition slowly, in a planned manner. But we do
>>>
Mirimir wrote:
> On 01/03/2019 11:06 PM, teor wrote:
>
>
>
>> Hopefully, we'll have feature parity on v3 very soon. And then
>> apps will migrate from v2 to v3 (or dual-stack).
>>
>> It's best if we transition slowly, in a planned manner. But we do
>> need to transition in the next few years.
Hi aurum1704,
thanks for adding so many relays.
If I may ask: Are you planing to run them long term?
Just be aware of the traffic pricing at DigitalOcean:
https://www.digitalocean.com/community/tutorials/digitalocean-bandwidth-billing-faq
| Up | Ext | JoinTime | Nickname | Version
On 1/4/19, teor wrote:
>> Node operators (tor-relays) would continue offering
>> v2 HSDir support module until such time as the reasons
>> for choosing v2 by those above are supported in v3 or vN.
>
> It's not just about feature parity.
Right. Feature parity is nice and excellent goal, till
