Thank goodness I only openly supported piracy from 2019 to 2023 with 5 different accounts lmao
Dodged a bullet there
Now is a good time to remind users that you are placing some trust in the instance that you use. Lemmy is not anonymous. It is pseudo-anonymous. Your instance can do pretty much anything with your account up to and including turning your account into a sock puppet, and they know exactly where you’re connecting from.
With that said, it’s a lot better than most social media today that actively tries to violate your privacy at every turn.
To add to this: some instances require your email address, and others don’t.
Obviously there are plenty of other ways you won’t be really anonymous, but if it’s important to you, one step in mitigating issues is not to have an email associated with your account.
What about using something like a protonmail address for all social media email?
A good strategy, but still less secure by definition than no email at all.
Iirc proton mail has a backdoor. Though they likely won’t be used outside of ‘nať-sećurity interests’.
Guys, this is fact, also downvotes aren’t private.
Piracy is part and parcel of the global economic system, and since that system hasn’t changed since time immemorial, well it always has been too.
[This comment has been deleted by an automated system]
@skullgiver @Fonz It is possible; you have to set it up yourself and you won’t federate with many places.
Hosting Lemmy or Mastodon on Tor or I2P isn’t hard; you just host it, and link your Tor/I2P daemon to it same as any other website. But you have to be aware you’ll be cut off from the majority of other instances. You’ll be running standalone.
I am not sure about Lemmy, but Pleroma supports feeding all your federation traffic through a proxy; you can use one called fedproxy to split out your I2P federation traffic through your I2P daemon, and likewise for Tor. I am not currently running this on my server. It should still work for other fedisoftware than Pleroma. https://docs.akkoma.dev/stable/configuration/i2p/
[This comment has been deleted by an automated system]
@skullgiver Yes, there are many ways to make sure your server connects to Tor and I2P sites. But that’s what the guy who ISN’T running a Tor/I2P site has to do, to federate with the Tor/I2P site. If you’re running the Tor/I2P site you can’t really do much on your side to enable federation.
Cloudflare won’t help because you need inbound connections. Some VPNs support *transient* port mapping designed for BitTorrent, but good luck trying to claim a stable port number for any significant length of time, never mind port 443 (which I’m sure is outside of the allocation range anyway). You’d have more luck trying to find a VPS provider crazy enough to let you pay anonymously with cryptocurrency with just a pinky promise that you’re not hosting child porn. Or just don’t federate.
[This comment has been deleted by an automated system]
I mean you can very much onion route to a regular server, if it allows connections from Tor.
Unfortunately Tor means it’s very hard to IP ban abusers, so a lot of services automatically ban common Tor exit nodes.
[This comment has been deleted by an automated system]
This is basically true. You need to have certain DNS configurations you cannot afford on Tor hidden services to federate, and while you still could be listening on a Tor hidden service, clearnet servers would still need to reach you to federate.
On top of that, even if you somehow manage to do that, either youre federation trafic goes through Tor (lmao how to DDoS Tor in 1 step), or It doesn’t and all servers can see your public IP, which deafeats the purpose.
[This comment has been deleted by an automated system]
LOL, that’s cute. Reddit doesn’t even know my real email address.
