From @cwebber and https://dustycloud.org/blog/how-decentralized-is-bluesky/

> What if a new user claiming to represent alyssa.example shows up instead, and this seems to "check out"? How do we represent posts by the previous alyssa.example to the user? The current one? I don't know how to answer these questions... do you?

Assign date ranges! Addresses are not owned, they are leased.

In your address book, annotate the contact info with *when* it was linked. “Alyssa lived at 123 Main St, since 2014-07-23 until 2023-01-19”

I guess on the other end of that, what is needed is making this information generally available to others. Keep logs, ideally verifiable logs, in a centralized directory or a DHT or whatever.

I guess the question is: how do we handle resolving something “in the past”? For DNS at least, I’m not sure if registrars keep this kind of “past information”. I assume they don’t. So it should probably be kept elsewhere. Whichever source you use is the real “network”, unless an authority exists

@cwebber

Unrelatedly: Handles are not *.bsky.app they are *.bsky.social

Also:

> It's not clear how Ben would know that the person who used to be alyssa.bsky.[social] is now alyssa.example

I think ATProto keeps track of handle rotations? See April 29, 2023 here: https://atproto-browser.vercel.app/at/trwnh.com

@cwebber