It’s called a single-point of failure in Engineering.
Funny enough it wasn’t even a technical one but a contractual one.
Maybe there is some kind of lesson here on the risk of delegating critical structural elements to 3rd parties that rent rather than own that which they’re selling …
A centralized system wouldn’t have this problem since the only reason they can’t just use another domain name is because of refederation. A great example of this happening is piracy websites, which notoriously get shutdown only to pop up five minutes later with a new domain.
This is actually a critical flaw IMO in federated applications as a whole. Not being able to change domain names makes your entire platform (as an instance runner) tightly coupled to the initial decision you make when first setting up the instance.
It’s called a single-point of failure in Engineering.
Funny enough it wasn’t even a technical one but a contractual one.
Maybe there is some kind of lesson here on the risk of delegating critical structural elements to 3rd parties that rent rather than own that which they’re selling …
Unfortunately that has always been the nature of TLDs
For that instance, yes. For the whole of Lemmy, no. Everything else keeps on chugging along.
Indeed.
Imagine if this had happenned to a centralized system like Reddit…
A centralized system wouldn’t have this problem since the only reason they can’t just use another domain name is because of refederation. A great example of this happening is piracy websites, which notoriously get shutdown only to pop up five minutes later with a new domain.
This is actually a critical flaw IMO in federated applications as a whole. Not being able to change domain names makes your entire platform (as an instance runner) tightly coupled to the initial decision you make when first setting up the instance.
I think its called “redundancy L”