Mastodon: @[email protected]

  • 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle
  • 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.



  • In theory, I agree with you! A 100%, but the problem is that currently Lemmy doesn’t support migrating your profile to a different server. So that already slightly complicates things. So from the get-go they are forced to make choice. A choice which isn’t clear, what potential consequences are and the fact they currently easily migrate to a different server, obviously doesn’t help.

    “Like email” is basically the same description I’ve been using to explain it to non-tech people.

    Long story short, onboarding needs to get better. But that also applies for other Fediverse projects (like Mastodon or Friendica).




  • 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 has been “battle tested” for this level of interaction. So changes were needed, to optimize and squash bugs.

    I hope this helps 😊