Embed Notice

It's not worth bemoaning that #ActivityPub is, in fact, an open protocol.

And this is because it's not worth bemoaning that #SMTP is an open protocol. Or Hypertextual Transfer Protocol (#HTTP) is an open protocol.

Or for that matter that anyone can use these protocols as they see fit.

Do I like every use of these protocols? Not at all. We can't always have good things because shady assholes insist on exploiting the open web for their own greed.

The trade off is that we get to have an open web.

Now occasionally, I get people popping by who tell me, "Screw you! I don't care about an open web! I just want to keep my community intact!"

But the only reason your community exists is because we have open protocols.

If you don't think so, find me all those thriving communities still using AppleTalk or IPX/SPX. Wait. There aren't any.

And that's because the only entities that have bothered with a *closed, proprietary* protocol happen to be for-profit corporations that have largely discontinued them due to -- again, wait for it -- the prevalence of open protocols.

Which brings us to a further problem.

You can't use an open protocol while simultaneously pushing for it to be closed. The #W3C already validated ActivityPub. The proverbial cat is out of the bag.

So yes, corporations will adopt ActivityPub. That's already happening. #Meta, #Automattic, #Medium, #Flipboard -- many more to come -- are developing for it.

But openness also means you can build upon it. You can create your own thriving communities. And some of these communities can be private if you so choose.

Just as it's possible for you to build your own newsletter or publish your own webpage, it's possible for you built your own #Fediverse server.

You see, openness cuts both ways.