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 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.
@pratik Automatic cross-posting to Threads from your blog, very similar to our support for other existing platforms.
@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 oh man, it'd be really great to be able to see replies here! I just want to let my friends on threads see what I post and comment back. Don't make us have to check in on the threads app to see if someone has left a comment 🤮
