> a standard

Like a specification[^0], which is exactly what ActivityPub is and what federation in Forgejo is built around?

[0]: https://en.wikipedia.org/wiki/ActivityPub

I'm sure that sentry and co could spend a few bucks and commit a KPI in one of their upcoming quarters to figure out the activity pub spec and support integrating with it if their hearts desired. It's a chicken egg problem and we all know chickens exist. It's clear that the centralized model is getting left behind, especially as the EU is moving away from US services and they continue to invest in open source, European-based alternatives like Codeberg and Forgejo.

The communication protocol is not what I mean here. The feature-sets and capabilities around "pull requests", "reviews", "comments", "checks", "issues", "projects", "deployments", "releases", etc are all different across platforms. You have to integrate bespoke for each platform. There is no universal standard for how CI/CD, deployment tracking, project management, etc are done.

Yes, Sentry or whoever else could build a Codeberg integration, or a Forgejo one, or a Gitlab one. But these would all be bespoke. There is no standard. So the one with the biggest market share ends up with the most integrations. This is where we are today.

I'm all for open standards. But I don't even know of a proposal for such a standard.

Sure, with AI tooling, you can vibe code your own browser extensions or other integrations in some cases. But for a lot of platforms, that just won't cut it. That's before we even get into the maintenance burden of that.

Unlike GitHub's universal standard? Forgejo already has a near 1:1 github action format for forgejo actions. You can even use github actions in forgejo. You cant have AI build it out for a few tokens? Why are you so certain of failure?

Interfaces exist in programming languages. The strategy pattern is one of the gang of four patterns. I'm sure a good engineer or an AI can figure it all out or is that too hopeful? Unless Sentry engineers or AI are too incompetent to make adapters? I hope not, the market is in big trouble if a dev tooling org cant make tools for where devs are