Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Eh, the code is very inefficient.
Yeah... Lemmy's code and the way it implements activity pub is not the greatest... A lack of batch operations means that every single federated like is an HTTP request of its own.
My favourite is having to send the activities sequentially, meaning you can very easily block the queue when a request fails.
And that's just the network architecture. Database architecture is another kind of hell. Like a simple delete operation taking multiple minutes because there's a multitude of triggers, some of which take very long. That in itself is not bad, but the fact that the api waits for all the operations to succeed or fail (or the more usual case, timeout) is bonkers. Either fix the db or do it in the background.
I was excited for Lemmy a year and a half ago, which quickly passed. Thinking of migrating my server to some alternative. If Sublinks launches eventually, I'm migrating in an instance, currently thinking of writing an api compatibility layer between Lemmy and Piefed to migrate without anyone noticing.
That would be cool!