The problem is .dac or .coin are really specific, so while they are better in each specific utility they are not better in all cases. because Nikolai specified he wants a single TLD, I think we need to pick something that can be applied to any circumstance like .p2p which defines the tranmission method rather than being suggestive of the content contained therin.
Open to other suggestions but I think they need to be non-specific so .coin and .dac are out.
This seems non standard though.
.org is the organizational type. .com is the organizational type. .mil is the organizational type. .net is really the closest thing we have which resembles .p2p at the moment.
I think .dac would catch on quite quickly, or .coin because everyone making a coin or making a dac would be able to use it. I think .p2p makes a lot of sense and is fine too but I just prefer .coin or .dac because it's more community specific and it promotes the meme of the new organizational model.
If other TLD's are in demand, it will be rather easy to create another chain once the first is done. ".coin" and ".dac" might have more specific business logic than .p2p, it will give people a chance to experiment with what works while letting us focus on rallying behind "THE peer-to-peer domain"
This could work. We gotta start somewhere and .p2p isn't a bad place to start. I think .coin and .dac are just so logical and catchy that people would actually use it. I think .p2p might be used by something but it's not community specific. Like for example I cannot imagine Bitshares.p2p but I could imagine Bitshares.dac and when you have Bitshars Me then you can make use of all those .coin domains.