News for hackers. Stuff that matters.
Re:How to Compromise the Enterprise Endpoint by pfg on Wednesday June 29, 2016 @04:43AM (#12000300)
I'm having difficulties understanding this. If Google receives a request to remove content from some specific country, I would assume they are doing this based on Geo-IP rather than based on the domain users enter. It wouldn't really make sense otherwise, as the link to the blocked content would not necessarily need to use the localized domain, so this would be ineffective. It seems like an unimportant implementation detail - one that seems to do more harm than good.
Re:How to Compromise the Enterprise Endpoint by lmm on Wednesday June 29, 2016 @06:09AM (#12000596)
It means countries that want to block certain content can block all the other blogspot.* domains. i.e. blogspot.us is a site that they promise will only ever contain content that's legal in the US, so any country-level firewall in the US should leave that site unblocked, and so on.
Re:How to Compromise the Enterprise Endpoint by pfg on Wednesday June 29, 2016 @06:24AM (#12000646)
That still seems like an odd trade-off. The same logic should apply to things like YouTube and Google+, but they don't have a ccTLD redirect for those sites.
Re:How to Compromise the Enterprise Endpoint by lmm on Wednesday June 29, 2016 @08:16AM (#12001127)
Blogspot is older (and/or maybe put more thought into it early on - a blogging platform is naturally a speech medium whereas YouTube may not have thought of itself in the same terms), country-level firewalls are a lot more sophisticated these days.