Mastodon: @SuitedUpDev@mastodon.online

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

help-circle
  • Debian Woody > Red Hat 7.0 > Slackware 9.0 > Slackware 10 > Debian > Ubuntu > Mac OS > Ubuntu > Arch.

    At least for desktops and laptops.

    For servers I’m still primarily running Debian (and one instance I’m running Arch).

    The reason why I settled on Arch is primarily because the combination of bleeding edge and being stable enough for daily driving it. The AUR also adds sooo much, that there is nothing I really don’t need to manually install anymore.

    For servers, I basically want a rock stable system. Hence why I’ve chosen Debian Stable.


  • For all the oldies in the room, Lindows / Linspire (me included)

    Trying to merge Wine with Linux into one ““convenient”” package was overselling it at best and worst a lie. Back in '08 / '09 I tried to run it, just to see how good (or bad) it was. It was basically Debian with KDE and their special sauce on top to ““easily”” run Windows binaries. Especially in those day, WINE wasn’t as good as it is today. I think you can fill in the rest ;-)












  • Yesterday I was annoyed at wide code blocks being wrapped, instead of having a horizontal scrollbar, so I took 20 minutes of googling and hacking around with my minimal css skills and wrote a PR, it’s already merged and will probably show up on instances soon.

    Very nice!! Congratulations!

    Maybe you know more about web or android development, then you could look into contributing to the lemmy-ui or jerboa.

    Yes that’s definitely one the things I am leaning towards. On my main “gripes” with Lemmy right now, is the lack of keyboard shortcuts (think of stuff like, CRTL+enter to send a reply for example). So I wanna see if I can add that in the frontend repository.



  • 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 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