7 ms·
How do you deal with individuals that may not have a domain? What do you tie their scope to?
by lucacasonato 3y ago
How do you deal with individuals that may not have a domain? What do you tie their scope to?
- WorldMaker 3y agoThis is a joke: GitHub account name. If it is good enough for Golang, …
- lucacasonato 3y agoDoesn't this get us right back to where we started from? Where you don't want users to be able to register arbitrary names :)
- WorldMaker 3y agoCorrect. That's a big part of why it was a joke. (It's also a contributing factor in why I wonder if golang itself is in fact a prank.)
- deredede 3y agoNot if the system is built for DNS first. If a company/individual/organisation has a domain name, they are expected to use the domain. It is much less of an issue if someone has kik.users.registry.com when the company publishes packages under kik.com.
- postalrat 3y agoSubdomains on a service that will do authentication for cheap or free? Your packages could be published for lucacasonato.imbroke.com
- int_19h 3y agoUse URN instead of just a domain name. A domain name (with some schema) is obviously a subset, but anyone who doesn't want or need one can then use uuid: URNs. The XML ecosystem did it that way for namespaces, and I think that it is still the most flexible and the most future-proof approach, since you can always add new schemas as needed.