Welcome to today’s daily kōrero!
Anyone can make the thread, first in first served. If you are here on a day and there’s no daily thread, feel free to create it!
Anyway, it’s just a chance to talk about your day, what you have planned, what you have done, etc.
So, how’s it going?
Yep, that same issue with Kbin.social keeps happening. There are currently 130+ instances that are lagging behind lemmy.world.
Because of our special setup, we are getting the posts and comments through almost immediately but the votes are lagging quite a bit at the moment. The last couple of days have been pretty bad. This graph shows lemmy.nz in red, and aussie.zone in orange as a comparison. We are doing better than them now because of the pre-fetching setup we have (which also results in all the lemmy.world posts and comments with no votes). But it’s currently getting worse. Lemmy.world are investigating options for rate limiting kbin.social so they don’t send too much at once.
And here’s a graph of the lag time. We are back up over 8 hours now. Lemmy.nz in yellow, aussie.zone in green:
I know it’s annoying and I apologise for that! This is one of those growing pain things.
No need for the apology, was just curious what was going on. :)
It is an interesting issue though, going to the extent of rate limiting other instances. I wonder if it’s just a capacity issue, or a flaw in ActivityPub’s design? Just thinking out loud on how Lemmy can handle future growth.
Mastodon uses ActivityPub and has been around a lot longer, I suspect that our issues are specific to the lemmy implementation, and I suspect there is a lot we can learn from Mastodon. But I’m afraid I don’t have the skills to contribute so I’ll just sit back and let the people with the skills sort it out 🙂