Re: [tor-relays] community team highlights: Relay Advocacy

2019-01-15 Thread Vasilis
teor: > Hi, > >> On 14 Jan 2019, at 11:37, Vasilis wrote: >> >> Signed PGP part >> teor: >>> Colin also asked relay operators to opt-in as fallback directory mirrors >>> (in the last half of 2018). In December, he helped rebuild the fallback >>> directory mirror list. >> >> Thank you for working

Re: [tor-relays] community team highlights: Relay Advocacy

2019-01-14 Thread teor
Hi, > On 14 Jan 2019, at 11:37, Vasilis wrote: > > Signed PGP part > teor: >> Colin also asked relay operators to opt-in as fallback directory mirrors >> (in the last half of 2018). In December, he helped rebuild the fallback >> directory mirror list. > > Thank you for working on this. > >

Re: [tor-relays] community team highlights: Relay Advocacy

2019-01-14 Thread gerard
-relays On Behalf Of Nathaniel Suchy Sent: 14 January 2019 03:23 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] community team highlights: Relay Advocacy OVH only allows Tor relays and exits on their dedicated servers, it's not allowed on VPS and Cloud. I do not believe they're

Re: [tor-relays] community team highlights: Relay Advocacy

2019-01-13 Thread Colin Childs
Hello everyone, As there is some concern / confusion about what occurred here, I wanted to take a moment to explain: After Nusenu discovered the cluster of relays on OVH not reporting contactinfo, I reached out to a contact we have at OVH to ask if they can pass along information to the user

Re: [tor-relays] community team highlights: Relay Advocacy

2019-01-13 Thread Nathaniel Suchy
OVH only allows Tor relays and exits on their dedicated servers, it's not allowed on VPS and Cloud. I do not believe they're actively checking though, you could probably get away with a non-exit relay, or even an exit relay on the reduced-reduced exit policy (brush off the occasional abuse /

Re: [tor-relays] community team highlights: Relay Advocacy

2019-01-13 Thread niftybunny
> On 13. Jan 2019, at 22:54, grarpamp wrote: > >>> communicating with OVH regarding relays without contactinfo > >> Is it *really* a good idea to poke OVH over this? >> in their ToS >> I feel this can backfire in a bad way >> is easier to ban all this "Tor" entirely? > > Though there can be

Re: [tor-relays] community team highlights: Relay Advocacy

2019-01-13 Thread grarpamp
>> communicating with OVH regarding relays without contactinfo > Is it *really* a good idea to poke OVH over this? > in their ToS > I feel this can backfire in a bad way > is easier to ban all this "Tor" entirely? Though there can be some context, in general harassing and busywork for ISP is

Re: [tor-relays] community team highlights: Relay Advocacy

2019-01-12 Thread teor
> On 12 Jan 2019, at 21:54, nusenu wrote: > > Forwarded Message > Subject: [tor-project] community team highlights -- November and December > Date: Wed, 09 Jan 2019 18:15:00 + > From: Alison Macrina > To: tor-proj...@lists.torproject.org > > Relay Advocacy >

Re: [tor-relays] community team highlights: Relay Advocacy

2019-01-12 Thread Roman Mamedov
On Sat, 12 Jan 2019 11:54:00 + nusenu wrote: > communicating with OVH regarding relays without contactinfo added to the > network. Is it *really* a good idea to poke OVH over this? Basically it's trying to imply that running Tor should be OK, but running Tor "improperly" (per your own

[tor-relays] community team highlights: Relay Advocacy

2019-01-12 Thread nusenu
FYI Forwarded Message Subject: [tor-project] community team highlights -- November and December Date: Wed, 09 Jan 2019 18:15:00 + From: Alison Macrina Reply-To: tor-proj...@lists.torproject.org To: tor-proj...@lists.torproject.org Relay Advocacy