Yes, but I wish more people understood it better.

The vast majority of what I've read around various ActivityPub implementations (I'm noodling on my own extremely slowly), is basically "Just stick this value in @ context and move on", there doesn't seem to be a lot of love for it.

it's less "people don't like confrontation" and more "people don't universally agree to all terms". it's a real problem *if* you don't want to bludgeon everyone into accepting a de jure or de facto central registry. here, "de jure" is W3C and "de facto" is Mastodon, but make no mistake, you get bludgeoned either way... unless you explicitly allow for disagreements.

The real purpose of grotesquely overengineered standards like ActivityStreams — standards so absurdly complex that they needed their own toolchain just to generate the code you were then expected to finish by hand — was never merely interoperability. It was gatekeeping disguised as architecture.

Make the standard complicated enough, verbose enough, and expensive enough to implement, and the lone programmer disappears from the picture. At that point, only a medium-sized company, a large corporation, or some well-funded foundation can realistically afford to build something that actually works.

It is one of the oldest tricks in the corporate playbook: bury a perfectly understandable problem under committees, abstractions, ontologies, tooling, generators, and architectural piety until the jungle of independent hackers — the people who build things because they are curious, stubborn, or simply having fun — is effectively locked out.

Then, of course, everyone solemnly congratulates themselves on having created an “open standard.”

Fortunately, reality had other plans.

The project failed.

You are not wrong. There are two ways to approach the problem of namespace collisions.

Technically, that's JSON-LD, and socially, which is talking to the other party and sharing the name space or choosing a different name.

Maybe JSON-LD was invented because people don't like confrontation hehe

But, the fact that it hasn’t *really* caught on makes it a bit of a pain to try to do it right.