@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. 😅

@ElectroVagrant I wonder if this will work too?

(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. 😋

@Eddie I would love more interoperability. 😉

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.

(Obligitory @selfhosted for Lemmy to notice me)

Oops! I didn’t expect this to start a thread on @selfhosted (I posted this from Mastodon). Hello other Fediverse friends. 😅

@Eddie If you include the group name (@selfhosted) it seems to work, but this isn’t really practical.

@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? 🤔

* _Test_

@NumbersCanBeFun @selfhosted Oh wow, I didn’t realize this would actually cross post to Lemmy.world. 😅

Oh wow, I didn’t realize I actually cross posted to #Lemmy by @'ing the group. 😅