Any lessons from EchoFeed's closure?

What can I learn from the demise of EchoFeed? Earlier this year, when I heard about this service, I looked into it to see if it could be useful. It wasn’t, thanks to Micro.blog’s ability to cross-post to Bluesky, Mastodon and more. Plus, at first it looked like an experiment more than anything else. I didn’t know EchoFeed’s long-term goals. I was on the breaks.

I’m wary of one-person services like EchoFeed. Another example is FeedPress. I like this service a lot, but I think there is only one person behind it, and it’s owned by a parent company which I know nothing about. It’s not entirely clear from this post what their mission is. What happens if this guy decides, or the parent company says, it’s no longer viable? Moving off EchoFeed might be a pain for people who need cross-posting capabilities. I highly doubt these people are willing to move to Buffer.

The same could be said about moving off FeedPress. It would be a pain in the ass to reconfigure all my feeds. The same torment applies to Micro.blog itself (or Scribbles.page, for that matter!). What is the future of Micro.blog if something bad happens to its founder? What is the continuity plan? Micro.blog has done everything it can to enable data portability and ownership, but moving things around, even if you own most parts, is not as easy as it sounds. In today’s world, nothing is permanent, and planning for this is mandatory.