original text: https://bin.disroot.org/?610558726777a450#6xmYwbxAr7KsoKqe1QHrEjZU63b2UqiPvuiUKBMPuSjp

However you may need an ai to help you understand the text at this link.

I’ve simply had this translated from my native language into English. My English isn’t good enough to write this myself.

I think it is time to stop reposting the same privacypack screenshot 50 times.

> man woman

No manual entry for woman

I make like-minded friends. They don’t use WhatsApp either.

E-mail —> Tuta

Alias —> addy (or cloudflare)

Cloud Storage —> Filen

VPN —> NymVPN (or MullvadVPN)

Calendar —> Tuta Calendar (or fossify calendar)

Lumo —> DuckAI

Authenticator —> Ente Auth

Wallet —> Cake Wallet

Docs —> CryptPad, NextCloud Office

Pass —> KeePass, Vaultwarden

Signal (Molly) —> SimpleX

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.

deleted by creator

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.

• Computer: Librewolf + Helium
• Mobile: Ironfox + Cromite