I think that is a bad idea. You don't know enough about a relay to have
a clue about what the underlying hardware looks like from any of that
metrics.
Simple example: You have a 8 core 16 threads cpu, run 4 instances, each
node pinned to 2 threads and a 10 gig pipe, you will run each tor
On 06.08.2019 12:57, ger...@bulger.co.uk wrote:
Thanks. I just could not see how Fail2ban would work on an ORport.
What log would it look at? What criteria for the jail? The fai2ban
on my non-tor VPS does not yet work with IPv6, which is partly the
nature of IPV6 rather than a programming
It was nothing personal at all.
My point was and is: You can’t substitute a German non profit with this
organisation.
Even if you could, torservers.net are supporting all the others smaller orgs,
not the other way around.
Thats a lot of work organising orgs and also avoiding unnecessary work
Hi Rob,
> On 8 Aug 2019, at 22:15, Rob Jansen wrote:
>
>> On Aug 6, 2019, at 5:48 PM, Roger Dingledine wrote:
>>
>> On Tue, Aug 06, 2019 at 05:31:39PM -0400, Rob Jansen wrote:
>>> Today, I started running the speedtest on all relays in the network. So
>>> far, I have finished about 100
Hi!
So I initially just wanted to share a tool/service which I think
addresses some of the issues I noticed in projects, when people get
burned out because of all the paperwork involved. I replied further to
mostly address some, from my perspective, misunderstandings about this
tool/service. By
> On Aug 6, 2019, at 5:48 PM, Roger Dingledine wrote:
>
> On Tue, Aug 06, 2019 at 05:31:39PM -0400, Rob Jansen wrote:
>> Today, I started running the speedtest on all relays in the network. So far,
>> I have finished about 100 relays (and counting). I expect that the
>> advertised bandwidths
