Does the community subscriber count only show statistics from that instance? For example, I have accounts on two servers and I wanted to find popular communities across the fediverse. For the most popular community, two different instances show different numbers for subscribers and users/month. For example, the top listing for these two instances is this:
https://lemmy.world/communities?listingType=All&page=1
[email protected] 10.4k 12.9k
https://lemdro.id/communities?listingType=All&page=1
[email protected] 34 8.48k
Interesting, I feel like that active-users column is new in lemmy v0.18.x, I don’t remember that being there and I didn’t initially read your post clearly enough to understand that bit.
Here’s my best-guess at what’s going on. It’s purely speculation, but speculation informed by study of how lemmy does other things in general and also by lots of exposure to system designs:
They obviously do not though, so what’s the skinny?
lemmy.world
andlemdroi.id
are both relatively new servers. When the first user on an instance subscribes to a community, their server tells the instance’s server “I want you to send me a copy of all new posts and comments going forward… also send me the most recent dozen or so just to get me started”. There’s no historical backfill. So you don’t expect to see post and comment counts match. I guess that makes them useless.lemdro.id
is missing actual posts and comments and therefore cannot calculate the active-user counts accurately.In any event, the workarounds are the same…
This is all kind of a wreck, I’m not trying to defend any of it. Just trying to explain why it might be that way. I have basically decided that the lemmy community browser is not useful except to look up a specific community and subscribe to it. Otherwise I always use lemmyverse or the community’s instance to find info about it.
Thanks. I figured there were still bugs being worked out, but I was just curious. Your insight was very helpful.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: [email protected]