Also this and this

See this post. The work is sponsored by the NLnet Foundation

Lemmy core devs are actually employed full time to work on lemmy.

This is a meme, right? …right?

Vlemmy refugees flocking in?

It’d be great to support identity based on a key hash, so that it’s completely decoupled from any instances. Maybe some time in the future.

I think one should remember the happy moments to know what’s possible. If you’ve been there before, the place exists and you can get there again.

Somebody’s been crying in the shower…

Honestly, Lemmy as it is now already is way more fun and engaging than Reddit ever was for me. On Reddit, I’m mainly a lurker. Here, I want to participate.

Yeah… If you’re not making a shitpost, it’s best to write it out in full in a notepad, save, then copy & paste 😅

#Deep

I guess that works as an emergency measure. Persistent storage doesn’t affect whether the updates are processed in time, but it would act as a sort of swap to keep the memory usage manageable.

For scalability, perhaps, you could run dijkstra and route the updates using the shortest path to each federated node, in a multicast sort of way? That would make the updates scale in a O(log(N)) way, provided that activity isn’t too centralised. It would also be great to run periodic “deep scrubs” between instances to sync up each other’s activities and provide actual eventual consistency. I guess that’s kind of a liberal interpretation of ActivityPub, but I think that’s the only way to ensure real scalability.