[Kye]

Wide C2S and ActivityPods support would address most of what led to the creation of AT. Lacking that, they made AT.

The rest is revealed in the developer community. AT and AP followed similar timelines for the first year or so, then diverged.

The main thing I heard from AP devs is that it's hard even before dealing with Mastodon quirks for any meaningful connection to the AP network. AP's early developer energy looks like AT's now, except AT's has been sustained for years and is only growing.

AP hasn't even managed a second conference, and that's where all the big AT stuff started at its first one. For example: Streamplace was new and awkward to use last year. This year, it was the official streaming platform with three simultaneous streams and had integration with the official ticketing system. I can't even list all the AT platforms people used to coordinate, trade info, etc during the conference. None of them had to deal with a clunky API since it's all JSON in a standard format on your PDS through a standard interface.

VODs are coming soon: https://bsky.app/profile/iame.li/post/3miahg7vlgs2w