I wrote a comment a bit ago on what this adversarial interoperability [1] could look like with local LLMs and accessibility APIs [2]. Big AT Proto and Bluesky fan, as it cannot be captured ("protocols, not platforms"), but it isn't enough to have this capability only with Bluesky; it must be able to support any social network or graph. It should be a robust content processor under the user's control for any firehose they wish to consume, whether that is a REST API endpoint, an RSS feed, a plain 'ol website that the agent will login as the user as, or a closed app that the agent will use accessibility APIs to operate the app as the user.

[1] https://www.eff.org/deeplinks/2019/10/adversarial-interopera...

[2] https://news.ycombinator.com/item?id=42879342