ptt

Users will, of course, have to accept that I2P is slow. Still, by using i2pd, optimizing the number of tunnels, and opting for a minimalist web interface, I can create a Lemmy instance that’s quite useful for the I2P community. I’ll make sure it’s a PWA. I can implement aggressive caching.

I’m sure that won’t happen.

Yes.

If you want to stay anonymous, you can’t be lazy. — Switching to the I2P network is very simple. Once my project is finished, I can put together a short guide on the Outproxy page explaining how to access I2P.

By adding rules like “Only the X community can share posts from I2P to the Clearnet,” I can be sure I’m not disturbing the rest of the Fediverse community.

Outproxy (I2P → Clearnet) and Inproxy (Clearnet → I2P) This can be done via these methods. Alternatively, a dual-stack instance might be a much more practical approach. An instance operates both on the clearnet (lemmy.example.org) and on I2P (as an .i2p eepsite). This instance acts as a bridge: lemmy.i2p ←→ bridge instance ←→ clearnet fediverse Federation is established indirectly through this bridge.