Hacker News Reader

Hacker News

Comment by kej | Hacker News Reader

Full thread

kej

I like the irony of hosting this site on a Google-operated TLD.

View on HN

Thought you were joking, but unfortunately you weren't... https://en.wikipedia.org/wiki/.dev

Just how many parts of the stack does Google have its fingers in?

EDIT:

Consider this:

1. a user at home, wearing a Fitbit walks over to their computer, with their Nest camera recording their movements

2. they open their Chromebook, which uses Chrome OS

3. browses to their Gmail inbox with Chrome, and clicks on a link in one of their emails, sent by a friend using a Google Pixel phone running Android.

4. via their Fiber ISP

5. using Public DNS (8.8.8.8)

6. transfers between the US and Europe via the Grace Hopper subsea cable

7. transfers with HTTP/2 (based on SPDY)

8. to the website on the .dev TLD.

Google is in every step above. Thankfully the webpage doesn't use AMP, or Google would be in that step as well. And good thing it's not a page built on Angular, or hosted in Google Cloud...

Especially one that Google weren't even going to let the rest of us use (an entire "generic" top-level domain to use as a globally-routable in-house domain...) and only capitulated after it seemed like the pressure on ICANN might cause them to Do Something About That.

Have context? Algolia search isn't working well for me, or I don't know which keywords would lead me to the story.

Here's a story from The Reg in 2015: https://www.theregister.com/2015/03/13/google_developer_gtld...

They quote from Google's application for .dev in 2013: "The proposed gTLD will provide Google with direct association to the term 'dev', which is an abbreviation of the word 'development'. The mission of this gTLD, .dev, is to provide a dedicated domain space in which Google can enact second-level domains specific to its projects in development."

Google finally opened it to registration in 2019, four years later: https://www.theregister.com/2019/02/21/google_launches_dev/

(Google also added .dev to the HSTS preload list so browsers expect names in that domain to only be reachable via HTTPS, thus breaking in-house uses of .dev.)

> (Google also added .dev to the HSTS preload list so browsers expect names in that domain to only be reachable via HTTPS, thus breaking in-house uses of .dev.)

Anyone using .dev for that was already broken per the spec. There are TLDs for those cases, they are .test, .local and .invalid.

Repo owner here. The jmoore.dev domain is for my personal website. degoogle.jmoore.dev is linked as the website in my repo (https://github.com/tycrek/degoogle) but it is not the primary site I wish people to view it from.

As noted in https://github.com/tycrek/degoogle/blob/master/MIRRORS.md for GitHub Pages: "I am using my personal domain as some firewalls block GitHub"

To be quite honest I would prefer to not use GitHub either, but in the interest of easy collaboration GitHub is the optimal platform to manage the project from.

Don't get me wrong: I totally agree with the irony of using a Google TLD. But as @franksvalli said, I do not use AMP, Angular, or Google Cloud. Any tracking done on that page is from GitHub Pages that I do not have control over, unless I make my own auto mirror for that domain.

Reply on news.ycombinator.com