Skip to Content.
Sympa Menu

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

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [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: Re: [opennic-discuss] .code or .codes TLD
  • Date: Wed, 14 Oct 2020 16:12:41 +0100
  • Authentication-results: mxback4q.mail.yandex.net; dkim=pass header.i= AT hng.ovh
  • Envelope-from: hayden.ng AT hn.fyi

I was not aware of that no, thankyou for pointing it out, like I say, these are all theories of what can be done. And with the api, I wrote some sparse documentation:
https://documenter.getpostman.com/view/13027629/TVRkaTtd#aee01ec7-085a-484e-bfc6-303229c5b722
 
Now looking at the big picture, a lot needs to be added, but even if there is a structure for domain registration API's, I won't end up following it anyway.
 
And thankyou for your feedback, it's just one of the possibilities of uses for this TLD, Who knows? messy.code, Actually, I quite like that.
 

10:02 am, 14 October 2020, Erich Eckner <opennic AT eckner.net>:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, 14 Oct 2020, Nicholson-Goult Hayden 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.


Certificates for what? SSL? Do you run an acme server? Which? Are you
aware of https://wiki.opennic.org/opennic/tlshttps://wiki.opennic.org/opennic/tls ?
 

  
 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.


Can you link some documentation for the api? Is this some standard thing
or some self-written purpose-centered api? (I have no clue, if there
exists some standardization for domain-registration apis)
 

  
 What do you think?


As I said before: This sounds nice to me. (I would register useless.code
for my cgit repo, though :-D)
 

 --
 Hayden NG


regards,
Erich

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl+GvoMACgkQCu7JB1Xa
e1qbjhAAjfDWYmudhBZYh8KJELnIwWQcuEGZtuGIxwgkmaW3+ojaMMe4tUK5FAJ9
QwNKuUK8p7MRLSvwuBG2hnizyVVf5MaDe38mDgh3+rpYeOyuUR3gKi6bvF9KRxsB
IPheYvVOzGbpcgedG/oD0Y2wCd657bgVVjXtp+Am6YrRFYvioY1dEtctpvfREg8V
W3XyK6tZLX99By2z4ce/Qt7FgJMEO+uKiS6OgGKcCQeXz3v1LL/PCDJGfwk2r5K5
h9q6K+jW+aLYeNxl/L8gx3/kljP/xD7ZTyRWLbTbca5NdtXycD4PkT4M8L0bVdU1
RbPxiw1/ZNOIZYUD3/EYNIldMF/ix2QBLhE+Q+LFiga20f/mGUJ7TuIcOMGamlxe
e28oTjU3+uAM2cQVrLqJrMLOuA23wMBpXmeEV21K+HLsaqR+VhsGJ0uChNB+cCPB
32hmOo/ItCImcoTSMMF7qlq/HEG0sNl2DqqdLrBK0HekkdF+p7R73fsoWCqKZ3Vz
WsKHp2Ezg2XQswKvIE7gXbARAxm0HRR7afbQ4m4riPa861lCMtxPhzhbqGSGfZ5n
Cd2f3Cdv3qh42wolKL+7QsHtcZLf+VPIFVv6OVTkidukhnWwiSXNi76voZx0YMea
+818GftW2OsL+WO1P9wFRqiBD22C7yRJvyzipA4w6albL24v+Ao=
=qyvm
-----END PGP SIGNATURE-----



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




--
Hayden NG



Archive powered by MHonArc 2.6.19.

Top of Page