Working with the Threads API reminds me of how frustrating it was to work with Facebook’s main app API years ago, and any silo API that requires manual approval like the App Store. The bureaucracy is at odds with Meta’s claim of supporting the open web and fediverse.

@manton I really disliked working with Facebook’s API. They kept changing things in breaking ways, for no reason.

@manton I really disliked working with Facebook’s API. They kept changing things in breaking ways, for no reason.

@manton I really disliked working with Facebook’s API. They kept changing things in breaking ways, for no reason.

@manton Facebook’s words not matching their actions? Quelle surprise.

@manton Meta ≠ Open web

@paulrobertlloyd Sigh, I know.

@manton when I worked at Snapfish, I had to integrate Facebook, Instagram, Flickr, and several other APIs to retrieve user photos. The Facebook API was definitely the worst to work with.

@manton Coming to Micro.blog soon? What features?

@pratik Automatic cross-posting to Threads from your blog, very similar to our support for other existing platforms.

@manton Awesome. Will replies to our Threads posts show up in Mentions?

@pratik Not in the initial release. Right now I'm not sure how much more I want to invest in Threads beyond the basics, but we'll see.

@manton The language of Mosseri's announcement wasn't encouraging either. https://www.threads.net/@mark.stoneman/post/C8YveNqO7mc/?xmt=AQGzd_M1FacFs7XJEXjVl_L4DMemXnvIYMw4OpARVG9F1g

@markstoneman Yeah, I never expected a full API because they don't want to give up ad revenue by letting third-party apps have control over the app experience. But I'm just generally disappointed that they haven't done more.

@manton 100% agree. Very hostile to real world usage.

@lexfri @manton Drafts integrates with ~18 services via OAuth and I was still like, “I got do *what* to get useful long-lived tokens”