Hi Guys
I today received notification from DO that they have changed their
Terms of Service and Acceptable Useage policies. Having read those
changed notices it is clear to me that DO are no longer really Tor
friendly. They do not allow exits and whilst my guard relay there
(at roof.rlogin.net wit
Why not run it until they spot it and shut it down?!
-Original Message-
From: tor-relays On Behalf Of mick
Sent: 15 October 2020 11:42
To: tor-relays@lists.torproject.org
Subject: [tor-relays] Shutdown of my digital ocean guard relay
Hi Guys
I today received notification from DO that t
Greetings relay operators!
Tor has now embarked in a 2 year long scalability project aimed, in part, at
improving the network performance.
The first steps will be to measure performance on the public network in order
to come up with a baseline. We'll likely be adjusting circuit window size,
cell
On Thu, 15 Oct 2020 11:41:52 +0100
mick wrote:
> Hi Guys
>
> I today received notification from DO that they have changed their
> Terms of Service and Acceptable Useage policies. Having read those
> changed notices it is clear to me that DO are no longer really Tor
> friendly. They do not allow
On Thu, 15 Oct 2020, at 13:09, Dr Gerard Bulger wrote:
> Why not run it until they spot it and shut it down?!
I assume they'll send him a big bill for all of the bandwidth that he
uses :).
___
tor-relays mailing list
tor-relays@lists.torproject.org
https
On Thu, 15 Oct 2020 13:09:49 +0100
"Dr Gerard Bulger" allegedly wrote:
> Why not run it until they spot it and shut it down?!
>
Because the last time they changed the rules (when they introduced
charging for bandwidth) I got hit (automatically) with a big bandwidth
charge despite having been to
On 15.10.2020 16:24, mick wrote:
On Thu, 15 Oct 2020 13:09:49 +0100
"Dr Gerard Bulger" allegedly wrote:
Why not run it until they spot it and shut it down?!
Because the last time they changed the rules (when they introduced
charging for bandwidth) I got hit (automatically) with a big bandwi
> KISTSchedRunInterval=2
>
> We are still missing 1 authority to enable this param for it to take effect
> network wide. Hopefully, it should be today in the coming hours/day.
since it is in effect by now
https://consensus-health.torproject.org/#consensusparams
could you publish the exact time
On 15 Oct (23:40:34), nusenu wrote:
> > KISTSchedRunInterval=2
> >
> > We are still missing 1 authority to enable this param for it to take effect
> > network wide. Hopefully, it should be today in the coming hours/day.
>
> since it is in effect by now
> https://consensus-health.torproject.org
On Thu, Oct 15, 2020 at 11:40:34PM +0200, nusenu wrote:
> since it is in effect by now
> https://consensus-health.torproject.org/#consensusparams
> could you publish the exact timestamp when it came into effect?
One can learn this from the recent consensus documents, e.g. at
https://collector.tor
On 2020-10-15 10:24, mick wrote:
On Thu, 15 Oct 2020 13:09:49 +0100
"Dr Gerard Bulger" allegedly wrote:
Why not run it until they spot it and shut it down?!
Because the last time they changed the rules (when they introduced
charging for bandwidth) I got hit (automatically) with a big bandwi
11 matches
Mail list logo
