Another problem intrinsic with the Fediverse: data interoperability across software and accounts.

There is a software suite that my company has been hosting out, but which as of the last few days has become "abandonware" by the developers. The repos still exist for it, the code is all free and open-source, but the developers behind it have publicly announced that they are walking away from it and moving onto other things and that the project is effectively dead unless some community members want to fork things to continue hacking at it. So, now our company is left with this software that no longer has any further development, bug fixes, support, etc. to exist (and our company had been one of the financial contributors to it). Whatever, is what it is, but this is just an example of my point:

Data portability and interoperability on the Fediverse is basically non-existent. Let's say that one day Mastodon, or Mitra, or Pleroma, or Misskey development suddenly halts and ceases entirely. Let's assume there are no interoperable living forks therein, and nobody stepping forward to continue working on the project. What does an instance maintainer do? Data between different ActivityPub server implementations is not interoperable. There's no real way to move from a Misskey instance over to a Mitra instance if Misskey suddenly EoLs or becomes abandoned as a project, e.g.. The only real solution in these scenarios is to start over entirely from scratch and take the L on all that data and user information/content.

I am not even going to bring up AT Protocol/Bluesky since ATP/BS is de facto centralized and the centralized + tightly-controlled nature of the software stack nullifies any possible issues or questions regarding data interoperability, etc.. However, to my knowledge, Nostr, for example, does not have this problem whatsoever since Nostr is moreso a distributed network vs. a strictly decentralized network (but, being distributed, is also de-facto decentralized) and data is ephemeral. I.e., on Nostr there is no "one" single repository for user content/data; there is no "one" single point of failure (like an ActivityPub server going down).

I don't really see any good way or method of solution for this. I guess data impermanence and losing servers/instances and accounts and content therein is just a fact of life and reality for the Fediverse, one that die-hard Fediverse users have already accepted and generally embraced. But, I don't know if that's necessarily a good thing or something that ought be just accepted with a shrug. I wonder if Fediverse projects like FEP-ae97 somehow provide a solution to problems like this or not.