undefined

I’d love to add something original to this post, but you’ve pretty much covered it.

To your point about corporate overlords: many of us loved Reddit until we realized it was a cesspool (for any number of reasons) and moved on, and it’s almost a shameful thing to admit we ever liked Reddit at this point.

To put it more simply: we just love federation and we love the format. We could always jump ship to Mastodon or any other federated platform, but long form discussion is what I believe drives adoption of Lemmy in particular the most.

I mean, that sure does suck but because most everyone is using the same tracker I don’t think it’s that big of an issue on i2p.

Is it fishy to travel without luggage? I’ve done it tons of times, who knew?

I don’t think it’s necessarily horrible but with slow WAN speeds it might be worth it to set up a DNS caching server and potentially caching proxies for whatever services you use (this used to be easier for generic HTTP before encryption).

For example, macOS has Content Caching for caching Apple software updates. You can also cache repositories for several Linux distributions, Docker, stuff like that too.

You need to configure your browser to first use the proxy that i2p is offering. From there, just browse to any eepsite (hostname ending with .i2p). For torrents, you’ll likely want to check http://tracker2.postman.i2p.

If you’re up to no good you probably want to visit an innocent site first to make sure your browser is sending the DNS query via i2p (or better yet, run your own DNS server that blocks all .i2p queries).

You can still use http://tracker2.postman.i2p or any other trackers on i2p (if they exist, it’s been awhile). You’ll just copy/paste the magnet links much like a traditional BitTorrent client.

I will say if you go this route, it does take quite some time to build enough tunnels for it to start working quickly. In other words, i2p feels much faster than Tor but not at first. I’d suggest browsing as many eepsites as you can just to get it going.

I use XD. It’s still a web-based client but it’s much more smooth than I2PSnark. I also much prefer i2pd over the clumsy Java stuff of “default” i2p.

https://xd-torrent.github.io/

Honestly I’m at the point where I just rent the discs and rip them losslessly (BDMV for movies, MKV for TV shows).

You can have your TMHI connect over Ethernet to a switch where you'll have ports then there you can get your wired connections and your point to points and your mesh network all off that switch. If you need more ports add another switch.

I’d much rather go this route too, using “mesh” for WiFi just sounds like too much chaos for me. It’s not sexy, but it’s a lot easier to maintain and upgrade (the individual parts).

Why not ditch the mesh and go with a properly switched network with Ethernet as the backhaul? Your latency is likely already hosed using cellular for WAN, why add even more as traffic boings around a bunch of mesh nodes?

I’m not subscribed here and yet I comment

“Your climate is warmer than mine so I gotta prove how tough and skilled I am”