a better solution is to decouple the query from individual api requests by adding a caching layer. we’ll get there eventually
a better solution is to decouple the query from individual api requests by adding a caching layer. we’ll get there eventually
Ah, ok. So if lemmy.world dies, but [email protected] was federated to 2 different other instances, those instances wouldn’t be able to “talk to each other”? They’d just have snapshots that they could locally interact with, but never see anything else? So is the fate of the Lemmyverse a graveyard of communities from dead instances?
meaning you could read my reply on a community that basically no longer exists
oh really? does it actually work this way? if lemmy.world dies, can all its communities continue to live on as long as there are lemmy instances out there federated and subscribed?
I wonder about this as well – because communities are tied to a specific home instance, that instance going down affects that community, potentially killing it. Something more akin to hashtags/tags/labels wouldn’t be tied to an instance so they would be more robust, though you’d lose the moderation of a community and just have a firehose of posts/comments…
It’s called a single-point of failure in Engineering.
For that instance, yes. For the whole of Lemmy, no. Everything else keeps on chugging along.
deleted by creator
they already are