We can standardize that ZeroTier networks should have their domain name as their network name; then, if the domain name has a TXT record matching the network name, we can display the network's domain name as "confirmed"/"corroborated" - so instead of displaying the long string as the network's name, we show its proposed name as its actual name (and in a different format than the network ID names, e.g. with a badge). For security we'd need the TXT record to be secured by DNSSEC (I believe deSEC does this). For a separate issue (implementing personal registries), perhaps the operator can assign their own petname to the network to have that be displayed as the network's name; but it'd be displayed differently from a DNS-based domain name.
It would also be nice to highlight the different parts of the network ID names in backgrounds of different colors, while still allowing them to be highlighted/selected and copied as a single unit.
We can standardize that ZeroTier networks should have their domain name as their network name; then, if the domain name has a TXT record matching the network name, we can display the network's domain name as "confirmed"/"corroborated" - so instead of displaying the long string as the network's name, we show its proposed name as its actual name (and in a different format than the network ID names, e.g. with a badge). For security we'd need the TXT record to be secured by DNSSEC (I believe deSEC does this). For a separate issue (implementing personal registries), perhaps the operator can assign their own petname to the network to have that be displayed as the network's name; but it'd be displayed differently from a DNS-based domain name.
It would also be nice to highlight the different parts of the network ID names in backgrounds of different colors, while still allowing them to be highlighted/selected and copied as a single unit.