Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Wait I've figured it out ...
The centralised Internet controls .com .org .net , & if we start .p2p, there's a risk they use .p2p too. But it's not a problem because all they really control is a ' . '
But you know what's much cooler than a '.'? A '!' , and they don't control the '!'
So what about, instead of .TLD's, BitShares DNS takes control of !TLD's?
BitShares!org, Apple!Com, Party!p2p
* I think having ".p2p" as the "meta-TLD / ICANN replacement" reads like a type error. Since you'd have to type the full sub-TLD every time, and it is unambiguous with just the sub-TLD, there wouldn't actually be any .p2p domains.Agreed, there is no need for meta-TLDs.* The "no TLD" default mode for our master sales model has usability problems because all browsers nowadays have omnibars (I use mine all the time). So whatever the master sales model is, it needs its own dedicated TLD. Suppose just for this post that we call it ".agent"I don't think this is as much of an issue as you are making out to be. In chrome, you can configure your search engines to use whatever keyword you want. By default, you can type "google.com<space>search terms" and it will do what you expect. But you can also set it up to be more convenient by going into Settings -> Manage search engines, and changing the keyword to say "g". This allows me to search by just typing "g<space>search terms". Since a space before the first / means the text in the Omnibar is not a valid URL to a domain, Chrome is able to know you are not talking about the TLD g.* The solution where most ".p2p" names are from the agent model, but a few are reserved for other models, is also a mental type error. Imagine explaining "example.own.p2p was sold via ownership model, but example.pwn.p2p is a subdomain of a name sold via cost carrying model"Do users really care which model was used to purchase a domain? Only the buyers should care about that. They can afford that slight mental burden in my opinion.
The BitShares brand name is important, but each of these DACs needs both a front end retail presence (which might have a retail trade name) and a back end presence for investor/developer/booster participation. The back end should be named Bitshares Something, but a business might also have a retail site with some name that is different and catchy (isn't this what Music is doing?). That said, DNS may have more blurring than usual, because there should be lots of overlap. I think the primary retail audience for DNS is going to be nerds. And I mean that in a good way.
This is what I have assumed all along - all DACs should have a market name and a consumer friendly front-end name.
BitShares Lotto might be known to game players as the Hard Luck Casino
BitShares Music might be known to its customers as BitTunes
BitShares Toast might be known to its customers as Names-R-Us
It's up to the developers to pick a name that will attract their customers.
But on coinmarketcap, BTER, BTC38, etc. they all show up as a branded family and work together to attract attention of investors.
When you need to connect the two, then Follow My Vote powered by BitShares is an easy way to have your cake and eat it too.
!
Even if it is not currently visible in the client it will be very soon. I think it is not worth the effort.
Anyway you could point XXX.delegate.bid to the real delegate's site which might help.
Well , each delegate can have his own site. There is a field that you can use when registering. Why should anyone use delegate.bid instead of his own site?
For example why should I use angel.delegate.bid when I currently use angel.bitdelegate.org ?
What would be nice is one place where everyone could go look for all the delegates. And you could put a link to your site from there. Because otherwise how would anyone find angel.bitdelegate.org other than digging through this forum? Until there is a one stop shop where people can compare delegates, the masses will have much less motivation to make good votes.Code: [Select]emski (unlocked) >>> blockchain_get_account angel-delegate
Name: angel-delegate
Registered: 2014-07-20T19:37:50
Last Updated: 10 days ago
ID NAME (* next in line) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
============================================================================================================================
5585 angel-delegate 7.1971134526 % 682 26 96.33 % 100 % 1,242.17116 BTSX 96422
Public Data:
"angel.bitdelegate.org"
See the public data? It is already integrated in the client.
Well , each delegate can have his own site. There is a field that you can use when registering. Why should anyone use delegate.bid instead of his own site?
For example why should I use angel.delegate.bid when I currently use angel.bitdelegate.org ?
