this post was submitted on 13 Jun 2023
21 points (100.0% liked)
Technology
37712 readers
168 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In short, yes it will take longer to "catch up".
The longer answer, be patient. This is an issue that will be resolved. I'm sure that the admins are doing their best to get the instance up & running ASAP.
From my experience during the great Twitter migration to Mastodon, you saw the same thing. Especially the "main instance(s)", mastodon.online and mastodon.social in this case, were overloaded to the brim. After a day or two, the sysadmins and developers were able to stabilize the instance.
The sysadmins in this case were responsible to keep the servers up and running (and scale up where needed). The developers because their code hasn't been "battle tested" for this level of interaction. So changes were needed, to optimize and squash bugs.
I hope this helps 😊
Edit: fat fingers, ie fixed typo
This is a fantastic point. I watched several migration waves from Twitter to the Mastodon/*oma/*key network over the course of Nov-Feb and each became less impactful as instances and developers understood better how that traffic would flow. Consider also that those platforms had also been around for a few years already.
Lemmy and kbin are very, very young still, so it will be great to see them develop over the course of the coming months. I expect the next couple weeks leading to the June 30 3PA closures on Reddit will be spent preparing for another wave.
Oh definitely that the next couple of weeks will be spent preparing for a new wave. I wouldn't be surprised if that was the reason why Lemmy.ml was down. Yes I know that it was because of a server migration but, that server migration also didn't happen for no reason ;-)
The first migration wave to Mastodon was very bad. I still remember, that following a person was nearly impossible. Not to mention the fact that, even if you could follow someone, it didn't automatically meant their messages ended up in your feed.
I know for example that version 0.17.4 of Lemmy (that was released 2 days ago) already has some database optimizations.