Hacker News Reader

Comment by joshdance | Hacker News Reader

More aggressive reporting and patching I support.

On a side note, I have a hard time taking any blog at a .blogspot.com domain seriously. Don't know why.

Using different domains reduces attack surface area [1]. That said, I agree that the blogspot domain and site design look amateurish.

[1] https://github.com/blog/1466-yummy-cookies-across-domains

It's a policy issue:

> If we receive a removal request that violates local law, that content may no longer be available to readers on local domains where those laws apply.

https://support.google.com/blogger/answer/2402711?hl=en

Not only that, its a .blogspot.com.br domain.

When I removed the .br part it redirected me to .blogspot.co.uk

Likely, the .br is there because the original submitter (here on HN) is from Brazil. Blogspot tends to redirect to the subdomain of the reader's country for some reason.

.br isn't a subdomain, it's a TLD.

If you want to get technical. A TLD is the subdomain of the root.

It really is .br. but the last . is left of for convenience.

Agreed. I don't think there is anything stopping me from registering googleinternetsecurity.blogspot.com or officialonlinesecurity.blogspot.com if they filter out "google."

Nor googleinternetsecurity.com. A TLD doesn't make it more legit, but at least under Blogspot, Google can shut down an imposter once discovered.

How about internetsecurity.google.com? They control their own TLD, they can make subdomains.

internetsecurity.google.com could set cookies on google.com

I think you mean they control a second-level domain. The top level domain is "com" in the example of "internetsecurity.google.com".

http://en.wikipedia.org/wiki/Top-level_domain

Yes, that was what I meant :).

The Google security folks have been getting more and more selective about what goes under google.com (especially user-generated content) because stealing google.com cookies gives you the user's auth tokens.

Reply on news.ycombinator.com