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
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