In the April issue I focused on OpenAPI spec and API design: https://www.bitoff.org/the-api-dispatch-3/

Despite all the hype around “AI”, I think there's still need to educate developers about maintainable API design.

#TheApiDispatch #OpenAPIs

From the beginning, I have been aiming #Emissary in this general direction. My Fediverse server is slowly coming online (Linked Data Signatures WTF??). Shared services are built deep into its core. I hope some nascent #OpenAPIs are available when I get there.

Today, I'm committing to:

1. Implement every single Open API that improves the user experience

2. If we need an API that doesn't exist, I'll work with whoever is interested to publish one.

My utopia would look like this: instance mods, #FediDevs, and other communities set aside the fear of centralization and embrace the opportunity to create better products for end users. #OpenAPIs will make this safe and reasonable.

Just like the search engine menu in your browser, instance admins (or even end users) should be able to switch whichever content cache they're using seamlessly. ABCDirectory starts indexing too many nazis? Cancel your subscription and turn on XYZDirectory instead.

This is a critical point in #Fediverse development. More centralized services are coming, and we can either build them well or poorly.

To me, "doing it well" means creating standardized #OpenAPIs so anyone can operate an independent service. Bonus points if you publish an #OpenSource reference server, too.