Discuss mailing list

[Rouben <rouben AT rouben.net>]

Sounds interesting. I wonder how this would complement the .libre or .oss TLDs? I suppose .code could be used for private (not open source) projects and would be more generic?

In either case, there’s a process to propose a new TLD, but I would wait until this discussion matures a but before going forward with a formal proposal on this list.

Here’s a link to the new TLD proposal process page on the wiki:

https://wiki.opennic.org/opennic/creating_new_tlds

Rouben

On Wed, Oct 14, 2020 at 01:44 Nicholson-Goult Hayden <hang AT hng.ovh> wrote:

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

 

--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

--

Rouben