Ok, it seems that the option of activating Tor for .onion relays is the bare minimum we should do.
The question is now, as a project, do we want to offer more privacy straight out of the box or not.
I am leaning towards also using Tor for:
1. Relays gathered from the Outbox model that are not in the user's relay list.
2. All relays that require Auth (no IP-Pubkey link)
3. All DM relays
By default.
More ideas are welcome.
Vitor Pamplona
npub1gc…fnj5z
2024-09-10 00:06:04
Author Public Key
npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5zPublished at
2024-09-10 00:06:04Event JSON
{
"id": "82a37cc977ac93eb8e9b21bb6657776883e45b5f1aeff9cc0c3c8b959e1f7cbc",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1725926764,
"kind": 1,
"tags": [],
"content": "Ok, it seems that the option of activating Tor for .onion relays is the bare minimum we should do. \n\nThe question is now, as a project, do we want to offer more privacy straight out of the box or not. \n\nI am leaning towards also using Tor for: \n1. Relays gathered from the Outbox model that are not in the user's relay list. \n2. All relays that require Auth (no IP-Pubkey link)\n3. All DM relays\n\nBy default. \n\nMore ideas are welcome.",
"sig": "82b71a8b78203c32785ed3bc238bb31c7b17f485233732227b81e0a39af3b5875ab731d761b36628057e4f8df18098f3cd1abe105544a37aa4a4b7200c4c5243"
}