That's later, though. Now is:

- Authentication cleanup
- Get this into production
- Alpha test with some trusted folks
- Start some flavor of invite-codes thing to let people slowly try it out

Thanks!

For example, @liberalcurrents.com (I give 'em money so they're top of mind) could say that @adamgurri.liberalcurrents.com is a member, with some kind of taxonomy ("editor" in this case, maybe). Those group memberships can be surfaced on individuals' pages.

The other is the above question of organizations. It's separate from "multiple users managing a single site" (also possible!) but rather a way for organizations to vouch for their members. What that vouch means is up to them. Employees, affiliated media members, professional orgs, whatever.

Right now I have two additional identity vectors I'm thinking of:

First off is IRL verification. I have a line on a way that I can do government-ID verification that keeps data you don't give me out of my hands. (You aren't the product, you're the service buyer, so this will not be free.)

"What about organizations with multiple members?" - this is a good question, and on my list to tackle, and adds something of an expansion to the problem of identity. I'm going to go live only with online/web identities, which are good if you have some secondary signaling but are NOT sufficient.

"Fishy" accounts are ones that put an Identivine site that _is not connected to their bsky account_ into their bio. My thinking here is that it is, to a first approximation, a strong sign of impersonation, and so we can tag it and provide a signal to users that it's not on the up-and-up.

HOWEVER, everything...basically works, as of now! If you look at @ed-labeler.identivine.dev you'll see a sneak preview of what it does for Bluesky specifically - it labels accounts that are recognized, though it only defaults to showing accounts with two-way verification. It also checks for "Fishy".

I also want to remove some of the more glaringly weird bits from it because it'll cause some false-positive problems for initial users. I can tolerate the bugs; I should fix them before we go out.

After having some time to ruminate on Identivine, I've decided to fix a few things before I give it to other people.

I decided to go to a magic-links implementation of auth. I don't actually want to be in the business of holding passwords for you. @filippo.abyssdomain.expert convinced me today.