@trwnh @mat @mcc @alter_kaker @esoteric_programmer Yeah, my understanding a while back was that the canonical location is defined by reference to the DID address. The way, you can still have a canonical address even if the originating account shifts to a new address. That prevents the old PDS from retaining authority. But so much has changed since I firmed that understanding that I wasn't sure whether or not it had changed. (One would hope the procedures for determining canonicity wouldn't change.)

@mat @mcc @alter_kaker @esoteric_programmer I would think making the PDS the canonical store would conflict with the idea of credible exit. You end up either weakening the notion of canonicity since moving an account changes the canonical location, or undermining the credibility of exit since canonical location stays with a PDS the author has left.

@esoteric_programmer @alter_kaker @mcc This is curious to me, because it looks like he's running a relay as an actual relay, just passing along data, which would explain why it's relatively low-cost. But the Relay described by the Bluesky white paper was more than just a relay— it was a replacement (or rebrand) for the earlier Big Data Server that was supposed to not only pass data, but also store and index it all for the network. And I can't tell if those other, more expensive functions got offloaded to other services, or if there are two types of relays in the infrastructure, or something else.