Skip to Content.
Sympa Menu

discuss - [opennic-discuss] .code or .codes TLD

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

[opennic-discuss] .code or .codes TLD


Chronological Thread  
  • From: Nicholson-Goult Hayden <hang AT hng.ovh>
  • To: "discuss AT lists.opennicproject.org" <discuss AT lists.opennicproject.org>
  • Subject: [opennic-discuss] .code or .codes TLD
  • Date: Wed, 14 Oct 2020 06:43:53 +0100
  • Authentication-results: mxback4j.mail.yandex.net; dkim=pass header.i= AT hng.ovh
  • Envelope-from: hayden.ng AT hn.fyi

I too had a TLD idea to replace .neo, Either .code or .codes, this have many uses like:
 
[name].codes
php.code
Read.code
Lets.code
my.code
[name].code
 
 
Then possibly free code storage at store.code? I can see endless possibilities for this TLD. I already have a system for how it would work as I host my own private TLD, and maybe a self signed certificate generator for the tld. So you install the root ca, and all is trusted. I see many ways this can be used.
 
Some cool things to do with it:
- store.code  (Another GitHub Alternative)
- my.code (Registry for .code)
- api.code (API To register .code)
- our.code (Possibly a collection of code)
 
I already have the API system, all it would require is users to signup.
 
What do you think?
--
Hayden NG
 



Archive powered by MHonArc 2.6.19.

Top of Page