oh also the public API comes with a guarantee that we won't break shit without notice. right now we are the only Official customers of the API so we're not super cautious about potentially breaking changes.
ah super hyped !!! im one of the private API crime doers and so I can’t wait to build some real cursed integrations using a public version
for usage, will users make their own API keys, or is OAuth planned? both are cool, just curious!
NONE OF THIS IS A GUARANTEE IT'S JUST HOW I'M THINKING ABOUT IT
initial early release will likely individual API keys/access tokens. while it does require more technical inclination for end-users, it's a million times easier for us to implement and lets us work out some kinks before we get more complicated. but we do intend to support oauth at some point.
completely makes sense !!! thanks so much for your hard work keeping this site going 
In my experience, supporting OAuth is a lot easier than writing your own API token grant. There's so many existing libraries out there that make it pretty easy to do. Also if you support OAuth it becomes very easy to also support IndieAuth, which starts to open up a huge world of IndieWeb integration.
I know this is an old post, but I do want to comment and say that I hope to see this API come to fruition! I would love to be able to integrate my cohost posts into my site :)
Gonna poke my head in here and see how things are going. We're no strangers to... how difficult creating and supporting a public API can be, so this isn't a rush. And I'll admit my motivations are somewhat selfish. 😇
some experimentation has happened but not a ton of material progress yet unfortunately (i keep getting fucked by some of the changes making it so that the app straight up Does Not Start) and we haven't had time to fully manage it yet. one of those things where i wish we had one more person so that we can multitask better.
😬😅 Understood, carry on with making it so the app will actually start. 👍
