Although it was opened against 0.17.4, I encourage you to mention what you are seeing on this Github issue: https://github.com/LemmyNet/lemmy/issues/3222
BitOneZero
joined 1 year ago
By listing instances based on user count they’re overloading and crashing the same old servers hourly (already), instead of treating instances like a federated decentralized network.
A huge number of servers have been added to Lemmy this month, and federation protocols within Lemmy are failing in their own way. Most users do not even realize that comments, likes, and postings are not reliably duplicated between the instances. See issue: https://github.com/LemmyNet/lemmy/issues/3101
beehaw.org sees these two comments, bot others are missing.
Does anyone know what’s going on with Lemmy.ml?
Serious scaling problems with the database in Lemmy. The code was not really tested and tuned for the quantity of federation peers to replicate with, comments, votes, postings. A lot of big communities over there to replicate.
I'm seeing pending on all my remote Join to communities hosted there.
yes. In the sitewide-search in the upper right next to your profile name and notification icon. It doesn't seem to work on the community search..
I imagine major overhauls are going to happen in the next 10 days on things like this, I expect there will be a lot of confusion.
They made a mistake in the link, left off the /c/
It doesn't seem automatic in my testing, even some well established ones don't show up unless someone triggers activity.
https://lemmy.ml/c/englishlearning
I'm going to search for that in the search, that is supposed to be the way to trigger it.
EDIT: yes, after searching for that string (the full URL), it now works here locally. /c/[email protected]
That's probably a big part. Web browsers can do ad blocking. Within the official Reddit app that's way more difficult.
view more: next ›
I don't think it's the identical issue either, but a developer working on the code would probably try to fix them together.