It’s hard to take Meta’s effort with more open APIs like ActivityPub seriously when their own Threads API is so locked down, requiring frequent re-approval. Open APIs shouldn’t make developers jump through hoops, over and over. Enough with the gatekeeping already.

@manton The more posts like yours I see, the more I think Meta is doing ActivityPub on Threads just for show. Adding to all the technical jargon that I don’t quite understand, why are they taking so long to fully implement it? It feels like they are moving at a snail’s pace on purpose.

@manton The more posts like yours I see, the more I think Meta is doing ActivityPub on Threads just for show. Adding to all the technical jargon that I don’t quite understand, why are they taking so long to fully implement it? It feels like they are moving at a snail’s pace on purpose.

@manton I agree, but for Meta, it might involve security due to their scale. Maybe they could extend re-approval intervals or stop it after repeated clean reviews? If they allow unrestricted access, we might risk facing another Cambridge Analytica situation eventually?

@manton louder so @mosseri can hear in back. If they’d publish a timeline of how the open part of their API is being implemented for indie developers trying to connect with it, tha would go a long way too.

@starrwulfe That would be great! More documentation and transparency wouldn’t hurt.

@manton I could understand them re-approving you if you weren’t using the API often but I’d imagine Micro.blog is doing it thousands of times a day?

@fahrni Pretty sure it’s the same for all apps regardless of usage.