The post says community posts go “to their backend at blacksky.app instead of your PDS, the same way a centralized platform like Twitter would.” This is incorrect. Look at communityXrpc in community.ts — it uses the atproto-proxy header through the PDS.
That means the flow is: your client → your PDS → PDS validates your credentials → PDS mints a service auth JWT signed by your keypair → PDS forwards to Blacksky’s AppView. Your PDS is fully in the authentication loop. This is standard ATProto service proxying, not a Twitter-style bypass.
The flows in the post are simplified as much as possible, because I wanted audiences that don't have a technical understanding of the protocol to be able to follow what is going on.
/**
* Make an XRPC call to a community.blacksky.feed.* endpoint.
*