Earlier quoted context omitted.
I mean why would Chagos, free of ever having the British, end up with IO as a country code?
Well, there aren't any obvious alternatives, for one thing: .ch is Switzerland, .ca is Canada, etc. I don't know, it's a problem for politicians and standards bodies. Even if not "British", Chagos is still inside the "Indian Ocean", so the reason for the country code remains.
Introducing .app, a more secure home for apps on the web
341–350 of 378 posts
Re: Introducing .app, a more secure home for apps on the web
#342I went through a few of the registrars and got error messages that the TLD wasn’t supported.
Godaddy of course has a solidly gouging pre-registration price.
Set an alarm to park park park.
Edit: Godaddy isn’t straight up gouging. Seems like dictionary words are much more expensive than made up words or non-dictionary brand names.
Name.com somehow has a “buy it now” option in the 10k+ range. Curious how that works.
Re: Introducing .app, a more secure home for apps on the web
#343Earlier quoted context omitted.
I've used DuckDuckGo for months. Only the very most esoteric of terms brings me back to Google, and I can count those times in the past months on one hand.
Yes, but good luck convincing the (potential) users of your app :)
If you are creating a organization that is less focused on making money as a core element like a business is, then you should feel fine using .org or any other domain.
Re: Introducing .app, a more secure home for apps on the web
#344Earlier quoted context omitted.
Both of those are articles are about registrars refusing to do business with one specific hate group. They're not about registries.
Yes, but that still represents a very serious problem. The EFF has written extensively on it since this occurred in August. Here's a starting point: https://www.eff.org/deeplinks/2017/10/eff-icanns-registrars-... . ICANN has worked very well so far, but if they don't put up a strong response to registrar-based censorship on already-registered domains and make this contractually impossible, the internet is going to be…
Re: Introducing .app, a more secure home for apps on the web
#345Yeah, the play store of websites. Where we need to get permissions and approvals and can get banned. No thanks, Google is trying to bring their walled garden idea for websites. Don't trust Google on this. They just turned off their service rather than support signal, what if signal was signal.app would they block em? Don't trust Google on this. It's a decent idea but no.
Actually I was searching for Terms of Service and Acceptable usage policy for .app domains and could find NOTHING specific. Not even on official site https://get.app/ I could only find Google Terms of Services, so they also apply to .app ??? So what if I host e.g. adult related material on .app will they ban me? The usage policy is totally in the dark for this domain. UPDATE: Found something here https://v4.gandi.net…
Re: Introducing .app, a more secure home for apps on the web
#346Just for fun, I tried these domain names via the url get.app: apple.app facebook.app instagram.app twitter.app ycombinator.app * snapchat.app * producthunt.app * whatsapp.app amazon.app microsoft.app google.app hotmail.app * dropbox.app intercom.app * pivotal.app * tesla.app dell.app ibm.app * * AVAILABLE
i call dibs on 'whats.app'
Re: Introducing .app, a more secure home for apps on the web
#347Registration opens May 8th. I went through a few of the registrars and got error messages that the TLD wasn’t supported. Godaddy of course has a solidly gouging pre-registration price. Set an alarm to park park park. Edit: Godaddy isn’t straight up gouging. Seems like dictionary words are much more expensive than made up words or non-dictionary brand names. Name.com somehow has a “buy it now” option in the 10k+ range…
Happy hunting.
Re: Introducing .app, a more secure home for apps on the web
#348Earlier quoted context omitted.
Hey Ted, since you're here, may I please suggest that the future implementation of 2FA not require a separate app? Even though Namecheap is using Authy OneTouch, it still requires a dedicate app, which is unnecessary. Thanks.
We partnered with Authy/Twilio on this integration to try something new. Totally get that we need additional options.
Re: Introducing .app, a more secure home for apps on the web
#349Earlier quoted context omitted.
> Now imagine that that ad had instead said "Go to curb.app to get our app", and that said site had prominent links to mobile app stores. Now imagine it's a year or two from now and you have the exact same problems that you had with curb.com. What's the strategy for when .app gets mined out? Are we just going to keep creating new tlds over and over for eternity? Bear in mind that the only way .app won't get mined out…
> Are we just going to keep creating new tlds over and over for eternity? Yes. The "easily memorable global namespace" is a limited natural resource, there is no definitive fix and there can't be - unless you accept the totalitarian single gatekeeper scheme Cyde describes. In an open system, you always need to deal with the Sybil attack and the only solution is proof of work, resources - money. This means domain squa…
Zooko's triangle is a triangle - decentralization is not the only thing we could sacrifice. We could even start to layer multiple naming schemes on top of each other to mitigate some of those sacrifices.
What OP (makecheck) was getting at was that the .app tld doesn't really solve any problems except to block one very specific injection attack, and it's problematic for Google to market it as significantly more secure than any other namespace. I agree with that.
The problem isn't that new tlds are unsustainable in the long term (although they are), it's that they don't even solve anything in the short term. Right now, at this moment, I can't credibly tell my parents that they should trust a .app domain more than a .com domain. Within a month of its release, people will be using it to phish older websites - because malicious actors will always be faster than regular users and developers.
If you're trying to block Sybil attacks, I wouldn't be that surprised if introducing new namespaces ironically ends up making the problem even worse.
Re: Introducing .app, a more secure home for apps on the web
#350Earlier quoted context omitted.
> Are we just going to keep creating new tlds over and over for eternity? Yes. The "easily memorable global namespace" is a limited natural resource, there is no definitive fix and there can't be - unless you accept the totalitarian single gatekeeper scheme Cyde describes. In an open system, you always need to deal with the Sybil attack and the only solution is proof of work, resources - money. This means domain squa…
Wouldn't it be easier to just raise domain registration /renewal prices, making squatting a poor return on investment?
There are a lot of benefits to allowing hobbyists and students to cheaply (or even freely) register domains.