Although ostensibly that’s not so much a bug as a feature - so that whenever one goes down, its content remains elsewhere.
That thought will need revisiting as we get larger though, imho. Like many “downstream” instances could set their own chosen expiration dates as they receive content from the more “primary” ones… or sth.
I think all instances should have a sort of cache, while fetching data from the original server. then if a server is detected to go down, the instance “immortalizes” the cache. i think this reason something like this isnt done though is because it doesnt fit with the intention of activitypub
The Lemmy devs primarily make software that they want to have working on their home instance, Lemmy.ml. How that federates outwards to other instances, something more desirable to the Western world, is a much lower priority. Which is still quite generous to offer as FOSS to the entire world.
An instance admin can choose to immortalize content if they want, but it happens so very rarely that it’s probably not worth automating.
Although ostensibly that’s not so much a bug as a feature - so that whenever one goes down, its content remains elsewhere.
That thought will need revisiting as we get larger though, imho. Like many “downstream” instances could set their own chosen expiration dates as they receive content from the more “primary” ones… or sth.
I think all instances should have a sort of cache, while fetching data from the original server. then if a server is detected to go down, the instance “immortalizes” the cache. i think this reason something like this isnt done though is because it doesnt fit with the intention of activitypub
The Lemmy devs primarily make software that they want to have working on their home instance, Lemmy.ml. How that federates outwards to other instances, something more desirable to the Western world, is a much lower priority. Which is still quite generous to offer as FOSS to the entire world.
An instance admin can choose to immortalize content if they want, but it happens so very rarely that it’s probably not worth automating.