@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/
You’re right that federation will be an issue. Maybe a Cloudflare tunnel squeezed through a Tor exit node for the clearnet domain and Tor for the rest? I’m not sure if you can use multiple domains like that but ActivityPub should support it.
I don’t know if Lemmy disables/doesn’t include proxy support by default, but there are tools like graftcp to force traffic through proxies in that case.
Alternatively, you could hack together a DNS server that resolves *.onion to 127.6.6.6, where you put up a proxy that just feeds directly into Tor. This will break for HTTPS sites but Onion services rarely have HTTPS anyway.
@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.
Cloudflare has a tunnel daemon that allows you to server a website from a network that doesn’t allow any incoming connections. It’s something between a VPN and a proxy and it should work fine, even from Tor exit nodes. Other services offer similar products.
You don’t even need port 443, though most clients will probably break if you pick another port. You can host a Lemmy server on port 13847 if you want, as long as you make sure federating traffic includes the port number on outgoing traffic.
Getting two hostnames to reach the same server would be the biggest challenge, I think. I have seen some indications in the Lemmy database that may suggest the possibility of multi domain setups, but there’s a good chance this is a remnant of an old design decision that has long since been abandoned.
@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/
You’re right that federation will be an issue. Maybe a Cloudflare tunnel squeezed through a Tor exit node for the clearnet domain and Tor for the rest? I’m not sure if you can use multiple domains like that but ActivityPub should support it.
I don’t know if Lemmy disables/doesn’t include proxy support by default, but there are tools like
graftcpto force traffic through proxies in that case.Alternatively, you could hack together a DNS server that resolves *.onion to 127.6.6.6, where you put up a proxy that just feeds directly into Tor. This will break for HTTPS sites but Onion services rarely have HTTPS anyway.
@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.
Cloudflare has a tunnel daemon that allows you to server a website from a network that doesn’t allow any incoming connections. It’s something between a VPN and a proxy and it should work fine, even from Tor exit nodes. Other services offer similar products.
You don’t even need port 443, though most clients will probably break if you pick another port. You can host a Lemmy server on port 13847 if you want, as long as you make sure federating traffic includes the port number on outgoing traffic.
Getting two hostnames to reach the same server would be the biggest challenge, I think. I have seen some indications in the Lemmy database that may suggest the possibility of multi domain setups, but there’s a good chance this is a remnant of an old design decision that has long since been abandoned.