This is part of the overall concept of the fediverse and the activitypub protocol.

Think of it this way - what is the difference between Twitter and Instagram? They’re very similar. The one key difference being that Instagram requires you to include a picture. But you can include pictures in Twitter too. So wouldn’t it be nice to be able to see Instagram accounts from your Twitter account? Speaking only of the technology and not the content or corporate shenanigans that is. (by the way, Pixelfed is an activitypub clone of Instagram, and it can interact with Mastodon)

What if you have an idea for a microblogging platform, but it’s a little bit different from the vision that the developers of Mastodon have? You can try to submit code to Mastodon’s code base but there’s no guarantee they’ll accept it. You can fork Mastodon, but then you have to work within the framework that they’ve laid.

Or you can create your own platform. The benefit is, you can implement the same set of interoperability standards that the community has agreed upon. You don’t have to attract all the users to your service to the exclusion of other services.

So why is all of this a good thing? There are a few reasons. If Mastodon starts heading in a direction that users dislike, they aren’t stuck with Mastodon. For example, if they started behaving like Twitter, users could just jump to a different platform, but they would be able to continue to interact with Mastodon users who choose to stay.

If someone has a much better idea for a platform and puts the time and effort in to make it truly great, there’s no reason for users to be stuck on a now inferior platform.

And if one software package tries a cool new feature that Mastodon doesn’t presently have, and that feature catches on, Mastodon and other services can choose to also implement the feature. It increases competition, but also increases potential for collaborative development.