Good to know
Lemmy currently miss a sync feature across servers. Meaning that by moving, one loses all subscriptions and messages.
The real solution should be a distributed network to support federation, instead than a plain federated one, i.e. an automated redistribution of users and loads across servers (lemmy instances).
I don't know how they are planning to manage it on the long run
Ah, I wondered if that's what it was - I found a Star Wars community through a web search and it said there were 2.5k subscribers, but it only shows 1 subscriber (me) when I view from an app.
I think it's a good idea to sum these statistics, but not for all instances (as it will be super easy to hijack with fake instances). Admin should manually select instances they trust and get the subscribed count summed.
Huh. I have 140-something showing as subscribed on c/cocktails and maybe 15 participating actively in a way I can see (commenting or posting) but it doesn't even exist in that lemmyverse link. Just an empty community called "cocktail" and a midwest social one.
tfw kbin communities aren't listed. rip.
In fact, the subscriber count on c/Games is on lemmy.world itself 8.67K and on lemmyverse.net 7.9K. What gives?
Hello there, and welcome to our community! I hope you like it in here.
Could you please include some body text as to why should people know this, and how would that help them? It’s our second rule. Thank you :)
What's the reason to show local counts anyways? Is there more to it than a "because we can, and it was easy to implement"?
I'm curious if there are any reasons which I don't see, and doubtful they outweigh the caused unclarity.
Most people only care about total numbers, I suppose.
I want to preface this by saying that I really don't know anything about Lemmy, but I can see where subscriptions are managed by the subscribers servers in a federated situation: the community's server might not even know who is subscribed to it since the subscribers server might be responsible for pulling data.
But any individual subscribers server would know about other users on that server that are subscribed to that community
Main reason for showing accurate user counts across instances is to give an idea of how active the communities are at a glance.
People will probably think twice about joining a community with low numbers, and it normally also causes those communities to be harder to find in the first place.
Not sure how lemmy implements this, but I suppose it's not a trivial task in such decentralized environment. Imagine 10 users from instance A subscribed to instance B and then instance A went permanently down. If B holds number of subscription requests it's now out of date. If B has to poll every instance it's federated with it's additional arguably unnecessary load. So yeah local subscriptions are a low hanging fruit. I guess one way to solve it is to have some independent authority that keeps track of sub counts in case those are (made) public and queryable
Are you sure? I don't think so. It shows users with data on the instance. A one subscriber instance will still show hundreds or thousands depending on how much federated content there is.
Yeah, just added a bunch of comms and it often showed 0 subscribers while I know from lemmyexplorer there's way more.
Somehow decentralisation is bad and we need centralisation to make a thriving ecosystem
You Should Know
YSK - for all the things that can make your life easier!
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must begin with YSK.
All posts must begin with YSK. If you're a Mastodon user, then include YSK after @youshouldknow. This is a community to share tips and tricks that will help you improve your life.
Rule 2- Your post body text must include the reason "Why" YSK:
**In your post's text body, you must include the reason "Why" YSK: It’s helpful for readability, and informs readers about the importance of the content. **
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding non-YSK posts.
Provided it is about the community itself, you may post non-YSK posts using the [META] tag on your post title.
Rule 7- You can't harass or disturb other members.
If you harass or discriminate against any individual member, you will be removed.
If you are a member, sympathizer or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people and you were provably vocal about your hate, then you will be banned on sight.
For further explanation, clarification and feedback about this rule, you may follow this link.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- The majority of bots aren't allowed to participate here.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
Partnered Communities:
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
Community Moderation
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
Credits
Our icon(masterpiece) was made by @clen15!