Discuss mailing list

[postmaster <postmaster AT welcome.factoryfouroh.net>]

To make an attempt to prevent possible collision with others in the 
future, to make it even more inclusive, and to give it a little 
personality I would also consider .bysyntax, .allsyntax .atozsyntax.  
This way scripts, and even something like "CNC programs" maybe included, 
and I doubt ICANN or anyone else would ever consider those TLZs. I also 
liked the 'messy' idea, so .messyntax is something different entirely.

On 2020-10-15 05:50, Jelle Besseling wrote:
> > btw: Originally, you also spoke of ".codes" tld. I just had a look at
> > icann's list of tlds 
> > (https://data.iana.org/TLD/tlds-alpha-by-domain.txt)
> > and it appears, that this one already exists.
>
> .code seems better to me either way, .codes sounds like it is meant
> for "secret codes" or encodings. I like .code as a TLD, it feels
> similar to .dev, but .dev is Google operated and forces HSTS. https is
> good, but I don't like them forcing it, so I would support an opennic
> alternative in the form of .code
>
> -- Jelle

--
Low-Cost No-Risk Pilots for Transitioning to Industry 4.0 - a Linux User 
Group for the Manufacturing Sector