@steve i still think the way forward is less that an activitypub client should hook into mastodon, but rather that mastodon should become the activitypub client. a lot of the ux expectations of mastodon are driven by the abstraction of the all-knowing“instance”, but this doesn’t have to be monolithic. storage and delivery can be outsourced to a generic activitypub server. but that would require people to care about activities instead of statuses.

@steve for the ux features that mastodon api provides, there is no reason to shoehorn them into ap c2s. something like search can be its own api, and it is highly dependent on which data source you use to fulfill that request. it is valid to have a mastodon instance providing a search api but being able to bypass it with a direct POST to outbox when desired. you can then let all clients know that the outbox was updated, e.g. by sending them an activity