Not really much to describe here -- in the event that a domain is associated with an ATProto handle already, is there a need for a distinct _wisp. record to verify ownership?
Something went wrong. Try again.
Monorepo for wisp.place. A static site hosting service built on top of the AT Protocol. wisp.place
Something went wrong. Try again.
So, like with one dev account also being used to control domains for a bunch of different projects, that may then have their own handles? (Say, nekomimi.pet and wisp.place)
That seems like a use case for supporting a distinct _wisp record, but not necessarily for requiring it.
The use that I have in mind, if you're signed into an account that already has a domain associated with it, is some kind of "configure hosting for this domain" user flow, that simply uses the ATProto record you have already to validate ownership.
my worry with this has been with org accounts as well as wanting to associate domains with a different DID