3 ms·

I don't see what the problem was with using domains. If you're trying to claim you work for NYT then get a NYT verified account? And what ever happened to Keyb

I don't see what the problem was with using domains. If you're trying to claim you work for NYT then get a NYT verified account? And what ever happened to Keybase? That seemed like a good solution. Verify by public private key? It really seems like that could be extended. I mean we have things like attribute keys and signing keys. It seems like a solvable solution but just the platforms need to create a means for the private bodies to integrate their keys. Hell, I wish we'd have verification keys for cops and gov employees. So me a badge? No, show me a badge with a key I can scan and verify your identity. It's much harder to forge a badge with a valid key than it is to forge a badge that just looks good enough

detectd 2y ago
> And whatever happened to Keybase? They got acquired by Zoom and promptly put Keybase into maintenance mode.
mattl 2y ago
> I don't see what the problem was with using domains. DNS for your average user is too complicated. Also what should the domain name be for a journalist at the NYT? What if they leave the NYT?
- godelski 2y ago
  > DNS for your average user is too complicated. The average user doesn't need verification either. In fact, I don't think I want most users verified. It then creates a reverse incentive where anonymous accounts are distrusted by default and too much trust is given to verification. An important part of a system with free speech and not governable (the point of distributed) is to be able to freely speak. Sometimes that means hiding your identity. Especially for those in countries or societies with particularly authoritarian rule. The best way to keep people quiet is to make them afraid of their neighbor. > what should the domain name be for a journalist at the NYT? AliceBob@NYT > What if they leave the NYT? AliceBob@bsky.social Everyone has the bsky.social handle, so you revert. I'd even be happy if optional profiles could show former affiliations. But it doesn't seem like a big problem. I mean NYT shouldn't be verifying a journalist if that journalist is no longer at NYT. Their new employer should.
steveklabnik 2y ago
> If you're trying to claim you work for NYT then get a NYT verified account? Part of the problem here is consistent identity over time. People do not like changing their handles unless they want to. I'm steveklabnik.com now, but if I started working at the NYT, and had to switch to steveklabnik.nyt.com, old links break to my posts, etc. And what happens if I want to be verified by more than one org at a time? Domains (at present) can't do that.
- 9283409232 2y ago
  I feel like this could be solved with organizations like Github. Steveklabnik.com can belong to the NYT umbrella org. Like on Github, you can either be kicked out or leave the org if you wish.
  - steveklabnik 2y ago
    Right now, while it's possible to have a DID associated with multiple domains, the Bluesky app view only supports the first. Doing something like this could work, but would be a larger lift. I do agree that multiple domain-based identities would be a nice feature though.
- godelski 2y ago
  > old links break to my posts Do they? I didn't observe any breaks when I did my DNS verification. > People do not like changing their handles unless they want to I don't see it that way. On both twitter and BlueSky there are two handles. I'm sure there's a better term, but let's say "display handle" and "address handle". (On HN they're the same) People are paying attention to the Display Handle and not the address one. Most of the time the address one is even cut off and is partially hidden anyways.[0] > what happens if I want to be verified by more than one org at a time? First off, it doesn't seem like Bluesky's implementation will do this so I'm not sure why it is being brought up into this conversation. Second off, I agree that this is a desirable thing to have. It is why I was suggesting something similar to keybase (keyoxide?) or attribute keys. It definitely seems like Bluesky is intending to do something similar to the attribute keys but there's some details lacking and seems like an existing verified user needs to vet an entity prior to their ability to distribute keys. I'd also be quite happy if there was a publicly visible ledger so one could see former verifications (it's all visible via the firehose anyways, right?). [0] And there's the classic problem on typing "@" and then the person's name and not actually finding them because the search system is fucked up and is looking for the address handle. I've seen this on both sites, more frequently twitter, and even when typing the address handle directly. Apparently this is a harder problem than I'd have thought (particularly replying to someone in the thread...)

detectd 2y ago

> And whatever happened to Keybase? They got acquired by Zoom and promptly put Keybase into maintenance mode.

mattl 2y ago

> I don't see what the problem was with using domains. DNS for your average user is too complicated. Also what should the domain name be for a journalist at the NYT? What if they leave the NYT?

godelski 2y ago
> DNS for your average user is too complicated. The average user doesn't need verification either. In fact, I don't think I want most users verified. It then creates a reverse incentive where anonymous accounts are distrusted by default and too much trust is given to verification. An important part of a system with free speech and not governable (the point of distributed) is to be able to freely speak. Sometimes that means hiding your identity. Especially for those in countries or societies with particularly authoritarian rule. The best way to keep people quiet is to make them afraid of their neighbor. > what should the domain name be for a journalist at the NYT? AliceBob@NYT > What if they leave the NYT? AliceBob@bsky.social Everyone has the bsky.social handle, so you revert. I'd even be happy if optional profiles could show former affiliations. But it doesn't seem like a big problem. I mean NYT shouldn't be verifying a journalist if that journalist is no longer at NYT. Their new employer should.

steveklabnik 2y ago

> If you're trying to claim you work for NYT then get a NYT verified account? Part of the problem here is consistent identity over time. People do not like changing their handles unless they want to. I'm steveklabnik.com now, but if I started working at the NYT, and had to switch to steveklabnik.nyt.com, old links break to my posts, etc. And what happens if I want to be verified by more than one org at a time? Domains (at present) can't do that.

9283409232 2y ago
I feel like this could be solved with organizations like Github. Steveklabnik.com can belong to the NYT umbrella org. Like on Github, you can either be kicked out or leave the org if you wish.
- steveklabnik 2y ago
  Right now, while it's possible to have a DID associated with multiple domains, the Bluesky app view only supports the first. Doing something like this could work, but would be a larger lift. I do agree that multiple domain-based identities would be a nice feature though.
godelski 2y ago
> old links break to my posts Do they? I didn't observe any breaks when I did my DNS verification. > People do not like changing their handles unless they want to I don't see it that way. On both twitter and BlueSky there are two handles. I'm sure there's a better term, but let's say "display handle" and "address handle". (On HN they're the same) People are paying attention to the Display Handle and not the address one. Most of the time the address one is even cut off and is partially hidden anyways.[0] > what happens if I want to be verified by more than one org at a time? First off, it doesn't seem like Bluesky's implementation will do this so I'm not sure why it is being brought up into this conversation. Second off, I agree that this is a desirable thing to have. It is why I was suggesting something similar to keybase (keyoxide?) or attribute keys. It definitely seems like Bluesky is intending to do something similar to the attribute keys but there's some details lacking and seems like an existing verified user needs to vet an entity prior to their ability to distribute keys. I'd also be quite happy if there was a publicly visible ledger so one could see former verifications (it's all visible via the firehose anyways, right?). [0] And there's the classic problem on typing "@" and then the person's name and not actually finding them because the search system is fucked up and is looking for the address handle. I've seen this on both sites, more frequently twitter, and even when typing the address handle directly. Apparently this is a harder problem than I'd have thought (particularly replying to someone in the thread...)