This could be a test of whether anyone enforces a moderation policy here.
On 14-01-21 05:59 PM, julien.robi...@free.fr wrote:
> Hi Mike,
>
> What you said is very interesting, it was the missing part for me to
> understand why the weight of the relay in the consensus can drop (or rise
> again)
Hi Mike,
What you said is very interesting, it was the missing part for me to understand
why the weight of the relay in the consensus can drop (or rise again) so
quickly (sometimes 3 times per day) without being caused by any change of used
bandwith on the network cable of the dedicated machine
Hi Mateusz,
If there wasn't any network connection then the script
would not give the right traceroutes even though the script will still run
(with empty traceroute results). So if it is not too much of a trouble
please restart the script and please make sure that the network is
ac
On 20 Jan 2014, at 02:57, Anupam Das wrote:
> Dear Tor relay operators,
> We have recently received a good rate of
> participation by relay operators to our measurement project. To give everyone
> an idea of the current participation rate we have hosted a li
Also keep in mind that what the bandwidth authorities actually measure
is not total capacity but spare stream capacity (by downloading large
files through at least 5 different two hop circuits times for each
relay). They then use this stream throughput measurement to create a
multiplier to multiply
Dear list members,
We have seen a small amount of odd entries like "slash24-proxy" in the
"phases completed" column at the scoreboard:
http://128.174.241.211:443/relay_scoreboard
It was a small script bug and Anupam is going to fix it today. No data is
lost, please check back with the scoreb
Hi Karsten, and thank you very much for your answer.
Few days ago I have re-started my 2 tor daemons (same identity, ArachnideFR94
and ArachnideFR94v2) on same the server on which I had these huge falling
down/rising up/fall down again consensus weight problems. They started back
from nearly 0
Hi starlight, hi Julien,
the bandwidth scanner system is quite complex, so it might be the case
that part of it is broken. But from this thread that's hard to say, and
it's impossible to know what part needs fixing.
Want to help us debug the problem(s) you observed?
Here are a few possible star
