David Goulet:
>> - removal reason
> Proximity of fingerprint indicates a clear attempt at insertion in the
> hashring for an (some) onion address.
Are you also trying to find the matching onion address(es) that the
given relay IDs would become HSDirs due to their position on the ring?
Out of
> Not enough bandwidth for a guard as far as i can tell.
That's my thought as well. Quoting Roger from a recent thread (from here:
https://lists.torproject.org/pipermail/tor-relays/2016-December/011519.html):
"You need to get in the top 25% of the relays by speed. "Speed" in this case
refers
Hi,
Not enough bandwidth for a guard as far as i can tell.
--
Sincerely yours / M.f.G. / Sincères salutations
Sebastian Urbach
---
Those who surrender freedom for security
will not have, nor do they deserve, either one.
Hi all,
I've had a relay running for 41 days, with Flags: Fast HSDir Running Stable
V2Dir Valid...but no Guard flag.
My impression from "Lifecycle of a new relay" at
https://blog.torproject.org/blog/lifecycle-of-a-new-relay is that the Guard
flag should be added within about 2 weeks of
I reopened, since I find it confusing as well:
https://trac.torproject.org/projects/tor/ticket/12692
https://github.com/RaphaelBergmann/atlas/commit/140b66694b5e47478a91e8c625f2298571e442d6
signature.asc
Description: OpenPGP digital signature
___
On 03/03/2017 10:05 AM, Jivan Amara wrote:
> My relay, which was recently restarted has a value of 'never' for
> 'Descriptor Published'.
> Is this a problem & if so how would I remedy it?
>
> https://atlas.torproject.org/#details/880EA01C702B372843A309AAE71BCBE36213C9CA
>
I should also mention
My relay, which was recently restarted has a value of 'never' for
'Descriptor Published'.
Is this a problem & if so how would I remedy it?
https://atlas.torproject.org/#details/880EA01C702B372843A309AAE71BCBE36213C9CA
___
tor-relays mailing list
