Still waiting for them to release the .dev domains
Everyone that has been using that for local development agrees.
Though the writing on the wall has been there for awhile - https://iyware.com/dont-use-dev-for-development/
Introducing .app, a more secure home for apps on the web
111–120 of 378 posts
Re: Introducing .app, a more secure home for apps on the web
#112Took me a while to figure out that Google Domains isn't participating in the Early Access Program. Apparently the "additional fee" for early access is extraordinarily high from some registrars. For example -> https://imgur.com/a/E9WRqTI
have you checked other registars? it's about 20eur on gandi. https://shop.gandi.net/en/domain/suggest?search=whatthefucki...
It's $15 after early access ends on yay.com
Re: Introducing .app, a more secure home for apps on the web
#113Supporting https is only an infinitesimal part of what makes downloading apps on the internet like playing Russian Roulette. It still doesn't prevent unsuspecting users from downloading malware, adware, ransomware, and apps that siphon user data. It also doesn't prevent users of sites depending on third party ad networks from being a victim of the same vulnerabilities they are now.
Later google will launch .ampp for apps that are certified to only have Google and their thousands of partners sharing your PII 'securely'.
Re: Introducing .app, a more secure home for apps on the web
#114Earlier quoted context omitted.
"embrace/extend/extinguish" is Microsoft's invention [1]. What are examples of Google's use of EEE? [1] https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
It was Microsoft's strategy roughly twenty years ago. It's Google's strategy today.
Can you provide an example? Something more specific than merely competing with existing businesses. The intent is key in the original definition of EEE.
Re: Introducing .app, a more secure home for apps on the web
#115Does this mean all request's will go via Google servers ? Like cloudflare ? Or how else would they enforce httpS ?
Re: Introducing .app, a more secure home for apps on the web
#116Earlier quoted context omitted.
So I have a Namecheap account and trying looking at an .app domain just now, but it says "We don't support this TLD". Because of this I am now on GoDaddys page pre-registering there.
Preregistrations don't really mean anything. We only do GA launches, which is on May 8.
Please get google to add you to https://www.registry.google/about/register.html
Lots of registrars are in there that aren't part of the Early Access Program.
Re: Introducing .app, a more secure home for apps on the web
#117Are already sex.app and dating.app registered?
sex.app returns this "available: false, reason: in use".
dating.app returns this "available: true, tier: premium"
Re: Introducing .app, a more secure home for apps on the web
#118Earlier quoted context omitted.
> But are web apps "apps"? Both Google and Microsoft are both strongly in the "Yes" category here and are heavily pushing PWAs as a future of many types of apps. If a lot of PWAs also want to use .app as their TLD, that serves Google's purposes just fine, I'd imagine. > Are Google going to be actively monitoring these to make sure the content is related to the .app TLD? Where's the creativity in that? The internet de…
Would Chagos get .io if it wasn't British Indian Ocean Territory?
Chagos is the preferred name for the atoll that the British named to be "their" Indian Ocean Territory in the colonial empire era.
Chagos should get direct control of .io, but it is a weird political fight.
One awareness campaign: http://www.thedarksideof.io/
Re: Introducing .app, a more secure home for apps on the web
#119Earlier quoted context omitted.
Godaddy enables you to preregister at the moment. This is only a preorder and doesn't guarantee the domain.
You can register a domain name at this moment during the Early Access Period through any registrar which supports it (which includes GoDaddy and many others listed at https://www.registry.google/about/register.html ). It's not a pre-registration; the domain is created and assigned to you immediately.
GoDaddy is confusing. They only have "Pre-Registration" and "Priority Pre-Registration", the latter showing the days of the EAP, but it only says you can "increase your chances of getting this domain", not that you get it right now.
Re: Introducing .app, a more secure home for apps on the web
#120Earlier quoted context omitted.
It was Microsoft's strategy roughly twenty years ago. It's Google's strategy today.
Can you provide an example? Something more specific than merely competing with existing businesses. The intent is key in the original definition of EEE.
Google Reader would be the often mentioned first example: Google entered the RSS reader market, became the best, added a bunch of features and really became "the" de facto place to read feeds. ...Then closed up shop and killed much of the ecosystem outright, directing people towards proprietary places to get their news like social networks or Google News.
Hangouts did very much the same with XMPP, a move which a Googler once suggested to me was viewed internally as a betrayal of the company's values.
I think we may be approaching EEE territory with email: Gmail's already centralized a large portion of the email industry, to the point that Google has about two-thirds of all emails on one side or the other, and now they're moving into introducing a proprietary email format (AMP 4 Email), which isn't being developed in a standards-focused way.
I'm sure the same argument could be made for their push into RCS over texting, browsers (now pushing Chrome-only websites and features in a lot of places), Android (embracing third party OEMs before moving into locking down much of newer Android functionality and launching a first party iPhone competitor), etc.
If there was a movie quote that best exemplified Google's business strategy, it would be "I have altered the deal. Pray I do not alter it any further."