Gregory's Server@rauschma some sort of cryptographically signed key ought to be possible. It would probably be very difficult to devise a scheme of reasonably compact keys that would guarantee that two different users could ever generate the same key, but you could make is statistically very unlikely.
|
6 comments
 @rauschma Given that choice, tying user ids to server ids, especially given that we now have pretty good user migration tools, looks like a very reasonable choice. #2/2  @simon_brooke One simple approach we could copy from Bluesky: @rauschma That's an awful lot of complexity which gets you back to the same dilemma you had in the first place: either the user owns their own domain name (hosted on the domain name system) *and* a server they can point that domain name at; or they're dependent on someone else to host it. I don't think you win anything at all. @simon_brooke @rauschma If the registry with which you have registered your domain disappears, (for technical, legal, financial etc. reasons), then you have absolutely lost your identity. This is the same problem. Domain registries are these days just commercial entities like any other, and they're frankly often not at the more ethical end of the commercial entity spectrum. |
@rauschma Having said this, however, of course email addresses are also domain name system dependent. And if we had a system of user ids independent from server ids, then we would need some sort of registry which resolved a user id to the address of the place where that user's content could be found, which would be one of
1. Centralised; or
2. Hierarchical, like DNS; or
3. Easily manipulated by bad actors
#1/2
@rauschma Having said this, however, of course email addresses are also domain name system dependent. And if we had a system of user ids independent from server ids, then we would need some sort of registry which resolved a user id to the address of the place where that user's content could be found, which would be one of