TLD discussion

[bytemaster]

${YOUR_BITSHARES_DNS_NAME}.bitshar.es

[fuzzy]

Perhaps using a system such as the gTLD from ICANN: http://newgtlds.icann.org/en/about/program

And creating categories based on geography or industry.

Ex:  .newyork
       .restaurant

very much like this...though it might make things more difficult to remember if there is no real standard convention.

Meaning just "the" Bitshares TLD, or various TLD's that might be useful if implemented?

.nomen
.nm
.key
.ident
.comp

I love .key...plays upon both Security Keys (implying the power of encryption) and also indirectly markets Keyhotee. 

[HackFisher]

We are not constrained in *any way* by the existing system, we just want to play nice with other namespaces and make it somewhat familiar to users.

Will it be greater if we can be compatible with existing DNS system, so that someone could setup a traditional DNS server (connect to chain as part of db), others can set to this DNS to replace original.

As in this way, it could be possible for the Internet to migrate from traditional dns tech to DAC-based DNS without influence user experience and user's habit.

I always wonder that the revolution can happen silently and smoothly, and it could be more powerful.

[yellowecho]

.bts!
.dac isn't bad either.
.www would be fun, heh

[bitbro]

.dac


Sent from my iPhone using Tapatalk

[mf-tzo]

  for the .p2p

I have some silly questions and I might not been able to express them correctly:

If I buy or create the domain name zeus.p2p will this be reflected in the usual internet world? I mean will there be zeus.p2p as an internet domain name and someone might want to pay me $ to get that name? I assume yes but then...
I can buy google.p2p (which doesn't exist) and definitely someone will buy it at some time and if not anyone in here, google will do so in the future...

Again apologies if this is stupid but I want to have it clear in my head of what we are doing...

[MrJeans]

.p2p

[mint chocolate chip]

.p2p

[toast]

.dom  !

[jae208]

.bns for Bit Domain Shares
.tst  for Toast
.bym  for Bytemaster
.dae   for decentralized autonomous entity
.soc  for social network
.bit  we might make better use of .bit than namecoin can

[SuanBing]

I like .dac

[toast]

We are not constrained in *any way* by the existing system, we just want to play nice with other namespaces and make it somewhat familiar to users.

[bitbadger]

Unfortunately, .name is already in use since 2001:
http://en.wikipedia.org/wiki/.name

There are ICANN applications for .free:
https://gtldresult.icann.org/application-result/applicationstatus/viewstatus

.key looks pretty catchy and makes sense.

Using two-letter name is problematic since those have always been reserved for ccTLDs.

Storing names in UTF-8 can cause compatibility problems, it's safer to require that all names including non-ASCII characters be converted to punycode first. Many applications and standards assume that Unicode domain name is equivalent to its punycode representation, and BTS DNS resolvers should always treat them as equivalent. Spoofing names using homoglyphs can be a problem; traditional TLDs normaly solve that by restricting allowed characters to one or several writing systems, BitShares DNS is for global use and can't easily solve that (I think Firefox shows domain names in punycode when they are not considered safe).

Wow, I did not realize that all 2-letter TLDs had been reserved for future ccTLDs.  Makes sense, I guess, but damn.  Also, the committee that approves new TLDs will apparently turn down ones that are very similar to existing TLD's, so .nam is probably not an option, and even .nom might be turned down.

As for the rest of your points, I guess it comes down to how compatible Bitshares DNS is aiming to be with the existing DNS system.  I do think that the existing system is understandably but needlessly tied to Latin characters, and a "native" Chinese/Russian/Thai/Arabic/etc. DNS system that doesn't rely on transliteration would be welcome.  Then again, the existing DNS system has quite a network effect going (pun intended) and it would be very hard to dislodge from its perch.

[etherbroker]

.bts is good but we should take .dac too


remember bts will trade all over the internet on exchanges, so the letters "bts" will come to mean "bitshares" pretty fast

[lynx]

Unfortunately, .name is already in use since 2001:
http://en.wikipedia.org/wiki/.name

There are ICANN applications for .free:
https://gtldresult.icann.org/application-result/applicationstatus/viewstatus

.key looks pretty catchy and makes sense.

Using two-letter name is problematic since those have always been reserved for ccTLDs.

Storing names in UTF-8 can cause compatibility problems, it's safer to require that all names including non-ASCII characters be converted to punycode first. Many applications and standards assume that Unicode domain name is equivalent to its punycode representation, and BTS DNS resolvers should always treat them as equivalent. Spoofing names using homoglyphs can be a problem; traditional TLDs normaly solve that by restricting allowed characters to one or several writing systems, BitShares DNS is for global use and can't easily solve that (I think Firefox shows domain names in punycode when they are not considered safe).