>> Since you are all tinkering with your servers anyway, why don't you try
>> deb822-style ;-)
>
> Because that doesn't make sense for public Tor nodes, but rather for .onion
> services.
> Many ISPs and providers have a Debian and Tor mirror and I use them via
> clearnet because reliability for
Hi,
>> wget
>> -qO-https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc
>> | gpg --dearmor | tee /usr/share/keyrings/tor-archive-keyring.gpg
>> >/dev/null
>
> Is the name important?
I assume it's Debian? The onfiguration of the signing key and the repo is
c
>> On 27 Feb 2024, at 15:39, boldsuck wrote:
>> On Dienstag, 27. Februar 2024 14:52:00 CET Corl3ss via tor-relays wrote:
>>> On 26/02/2024 21:03, Toralf Förster via tor-relays wrote:
On 2/26/24 20:07, meskio wrote:
> At the moment we're
> looking for 10 new bridges for Lox.
If it ha
>> I have a relay on 152.53.17.183 / 2a0a:4cc0:1:1333::beef which is listed as
>> "German" in metrics.torproject.org, but actually it is in Austria
>
> Was just a topic here recently:
> https://lists.torproject.org/pipermail/tor-relays/2024-January/021472.html
>
> Ask geofeed from the provider an
Hello,
unfortunately this happens more often. you are not alone :-)
> Am 18.01.2024 um 20:50 schrieb NodNet :
>
> I think tor and Tor Project use IPFire's DB for GeoIP lookups, and
> 198.13.48.219 shows the following:
Yes, libloc/location is used. I had the same problem with one or two relays
> Am 01.11.2023 um 17:53 schrieb dewaj :
> [...]
> Who wants to be identified as a tor user, let alone a relay operator?
> […]
I don't like this attitude at all and I don't think it goes with the demands of
most operators either.
I have often heard on this list and elsewhere sentences like: "It
