@ThorrJo@selfhosted lol, I can relate to thay 😆. I run an event & website that was notorious for its poor performance at the beginning and end of events. A few years ago, with our servers ready to fall over, I noticed a certain query was hogging the database server's CPU. I made the tiniest fix to correctly use indexes, and we instantly went from 400% CPU usage to at most 20% (across 4 cores). 😅
Though it's been fixed for 3 years, I still see folks warning others about the slowness. 😅
(I'm using the "content warning" feature of Mastodon, and replying directly to a lemmy.world user)
EDIT: Okay the content warning didn't work, but it appears that so long as I @ someone on the server that owns the group (it doesn't have to be the group),my messages will federate correctly. Also if you can read this, Mastodon's edit federation works too. 😋
Ha, honestly I'm impressed that any of this is working at all. 😆
By the way, to anyone reading this, in my previous reply I omitted the mention of @selfhosted. The reply didn't show up on #Lemmy until @NumbersCanBeFun replied to it.
This was supposed to just be a toot to my feed sharing that I figured out how to follow groups from Mastodon. I was not expecting to stumble across how to post to groups using Mastodon too. 😅
It makes me wonder if the "thing" to dethrone #Mastodon will be an alternative server/client/app that speaks multiple #Fediverse application protocols? I'm jealous that a #Lemmy server requires a fraction of the RAM that a #KBin or Mastodon server does.
@NumbersCanBeFun Okay that was unexpected. I managed to post a new topic and reply to Lemmy.world using my Mastodon client. That was supposed to be a "thinking out loud" toot. 😅
I attached some images to my first reply, but they were ignored. I wonder if my server strips out markdown? 🤔
@ThorrJo @selfhosted lol, I can relate to thay 😆. I run an event & website that was notorious for its poor performance at the beginning and end of events. A few years ago, with our servers ready to fall over, I noticed a certain query was hogging the database server's CPU. I made the tiniest fix to correctly use indexes, and we instantly went from 400% CPU usage to at most 20% (across 4 cores). 😅
Though it's been fixed for 3 years, I still see folks warning others about the slowness. 😅