3 ms·

So instead of having one global registry you have many local registries. If registries are also identified by UUID then you say pfraze dot com in the <registry

So instead of having one global registry you have many local registries. If registries are also identified by UUID then you say pfraze dot com in the <registry uuid> registry. I like this because then you can have registries that correspond 1-1 with other real-life things that can be internally consistent without having to worry about global uniqueness, like a registry of all registered businesses in a state, or all trademarks, etc. The next step is to create a system for "peering agreements" between registries, or meta-registries.

pfraze 4y ago
You can, but any shared address book needs to have a very clear scope of applicability. Basically: any users that are communicating need to either share the same registry, or have some clear indication that they aren't in order to avoid significant mishaps. I'm not totally sure how you accomplish that.
- kixiQu 4y ago
  <del>The federated approach would be the same way that we distinguish cooluser@gmail.com from cooluser@proton.me; in this case, the server part would just determine who you're asking to map cooluser to a UUID.</del> Actually, this is handled pretty clearly in the example article.