There’s a bot that’s tracks Lemmy communities for Active User Growth and Subscribers Growth each day and posts it to the following community.
https://feddit.nl/c/trendingcommunities
Check out the trending communities and join the ones you like!
There’s a bot that’s tracks Lemmy communities for Active User Growth and Subscribers Growth each day and posts it to the following community.
https://feddit.nl/c/trendingcommunities
Check out the trending communities and join the ones you like!
Your actual browsing of lemmy is moderately private, provided you trust your server.
But nothing else is. By design, it’s pretty easy for anyone who wants to track activity on any federated platform to do so. They’re extremely open.
You shouldn’t.
especially if you run it yourself. If you don’t have a loaded sawed off sitting near your server rack in case the machine spirit within grows too strong, you aren’t servering correctly.
Makes me think of this classic:
Not exactly. Many of the big instances have Cloudflare (or similar) sitting between you and the server, providing the HTTPS layer while watching everything you read and write on Lemmy. In cryptography circles, we call this a man-in-the-middle.
Your instance (sh.itjust.works) is one such instance, by the way, as is lemmy.world.
That applies to most of the internet, and Cloudflare has a long track record of not abusing that position, though.
Well, Cloudflare is not all that old, and we can’t see what they do with our data, so I would say it has a medium-length record of not getting caught abusing that position. But that’s not the point.
The point is that most Lemmy users’ actual browsing is in fact not private between them and their server. Many instances have a big network service corporation like Cloudflare watching everything read or written by every user, so that info is available to anyone with sufficient access or influence there, like employees and governments.
Not exactly, but it does apply to a great many of the biggest web sites, so we could say it applies to much of the internet’s traffic.
And that’s part of the problem. Cloudflare is in a position to watch much of what people do on the web, across many unrelated sites and services (often including domain name lookups), and trivially identify them. This includes whatever political, religious, or NSFW posts they’re reading on Lemmy, and who they are when they log in to their bank accounts.
In any case, I replied not to be pedantic, but just to let our community know that they shouldn’t assume their reading habits on Lemmy are safely anonymized behind a made-up username, or confidential between them and their instance admins. If your instance uses a provider of DDOS protection or HTTPS acceleration, as many big instances do, then the walls have ears.
That’s fine, and in principle I understand the threat, but I think there are plenty of security experts who choose to just use cloudflare because some of the services they provide genuinely require their scale and they have a pretty steady history of making very measured decisions about where they need to leverage their position to improve security.
There’s never been any indication that they’re collecting more than they need to or exploiting it beyond the scope of the service they provide, and several scenarios where they have refused to cooperate with governments trying to do invasive things. I absolutely think “moderately secure” still applies to traffic routed through cloudflare.
The whole point of Lemmy and the Fediverse as a whole is to decentralize, so everyone routing through a single service (Cloudflare) seems to go against that.
The point is to not be compelled to a central service. Choosing a provider that does a better job is perfectly fine.