It is probably due to a number of people stopping using their alts after some instance hopping.
Also a few people who came to see how it was, and weren’t attracted enough to become regular visitors.
Curious to see at which number we’ll stabilize.
Next peak will probably happen after either major features release (e.g. exhaustive mod tools allowing reluctant communities to move from Reddit) or the next Reddit fuck up (e.g. removing old.reddit)
Stats on each server: https://lemmy.fediverse.observer/list
There are many fatal problems on Lemmy, worst of all is you can’t click this link /c/books and see every /c/book on every Lemmy instance of the fediverse. This is out of convenience to moderators and it is killing Lemmy. One people figure out communities only exist on a single instance, the promise of federation is broken and they fuck off.
deleted by creator
See https://github.com/LemmyNet/lemmy/issues/3033 It’s won’tfix/notabug
but there is this https://github.com/LemmyNet/lemmy/issues/818
and https://github.com/LemmyNet/lemmy-ui/issues/1113
“multireddit” are nice to have but they do not address this problem Which a common view for all user of an entire community across the fediverse. “Multireddit” require client to pick and choose individual communities. This means less than 1% of users will every use it. This means there will never exist a fediverse wide community around topics.
expired
Propagation and agglomeration is a problem for clients not servers. Server only need to propagate a “we have new stuff” message and it’s up to the clients to pull it and cache it. In any case, users should be able to click /c/books and see the content of all /book/ on all instances in a single location. Unless most users can do this with one click, there will not exist a fediverse wide community.
expired
Why do you think communities with the same name will have the same content?
It doesn’t need to have the same content. Same subject. Names are descriptive
They don’t but they get aglomerated together anyway for having the same name . The community is the whole, which specific instance is hosting a particular /c/book post doesn’t matter. That it is on /c/book is what matters, not that it is on Lemmy.world
But just because [email protected] hypothetically exists doesn’t mean [email protected] or [email protected] have similar enough content. You can already view these communities from any instance. You’re essentially trying to apply something like federation on top of something already being federated. They can all have very different rules and different content.
If people have to hunt each post storage location individually, then it will be as if they don’t exist to 99.99% users. What will happen is there will be one big one, and they most likely be all on the big instance, and federation becomes just a weird thing that does nothing because functionally that will be just like Reddit. Centralized servers, centralized servers under the control of a tiny priesthood.
Not at all. Reddit has communities that are similar but with different names, rules, and culture and different people use them because they want different experiences. The same is true here.
The crucial difference is that those are differentiated by having a unique name, note a unique hostname. Which hard drive a community is stored should not be considered an important aspect of that community. It only specifies who is allowed to delete and edit content posted to that harddrive
That’s like saying everyone that lives on 123 Main St is the same regardless of the city or everyone with the email “Bob” is the same regardless of what their email provider is.
Lemmy has nothing to do with email. I’m sick and tired of this incorrect analogy being used to explain how Lemmy works and people stubbornly not understanding why it’s broken because of it.
If you think it through, what you’re asking is that the communities will exist only on one server. That’s Reddit with extra steps.
I would love to see something like this where it shows you content from communities with the same name across whatever your server is federated with.
Like an all feed but in a community would be lit but idk how that would ever be added. Too much work
There is no way for a user to block whole instances, there is no way to know if you’ve been banned from a community or instance, it’s extremely easy for people to evade bans and blocks, you can’t make private communities, armies of extremists are brigading other instances and they’re exploiting Lemmy’s flaws to do it, the list goes on and on.
Lemmy blows, but give the rubes time. They’ll figure it out.
It crazy how these people can get their bs to show up in my main feed, and then if I comment on it they call me a troll
There’s instance-wide blocking on the Connect for Lemmy app, including the option to block everything or only block the communities of that instance and not users. You can make a private community by not federating with anyone on a private instance.
Those are just cop-outs. They need to be hard-coded features on the original Lemmy app. If we have to rely on third-party apps for it, we can and should just use another fediverse app entirely.
I hope someone forks Lemmy at some point.
does this also block comments, or only posts? Sync has a similar feature, but only for posts, once inside a post you’re still subjected to their comments. Which for troll communities is honestly the worst part
IMO ideally there’d be two separate options. I want to block stuff like foreign language instances or some niche instances so that I don’t see communities hosted on them, but I don’t want to block the users from those instances when they post in other communities.
That’s a trivial problem to fix client side. Same as any regular spam filter. If Lemmy gives that power server side to be moderators instead of clients, then Lemmy will become a North Korea style dictatorship like Reddit.
Good point indeed
Having multi-communities, akin to multireddits, would be handy.
discussion about that here https://github.com/LemmyNet/lemmy/issues/818
and https://github.com/LemmyNet/lemmy-ui/issues/1113
See https://github.com/LemmyNet/lemmy/issues/3033 It’s won’tfix/notabug