1,110 karma · joined July 23, 2021
But I will say that it makes sense to avoid commenting on anything that could be interpreted as politically divisive (which Shays and 9/11 are not, really) regardless of factuality. It certainly doesn't seem to serve the intended purpose, since it's suggesting I ask it how to do things and not to ask it about history.
It did refuse to comment on whether or not the Vietnam war was viewed favorably by the public though. So I don't think it's the case that there is some specific exception coded in for Jan 6th.
Are you alright?
(This should be a sign that you need to turn off the TV and delete Facebook).
We're talking about changing default behaviors here in ways that can be surprising to users. It's reasonable to try and accommodate existing setups, future setups, and - yes - careless users.
This is, to me, a completely reasonable and believable use case that could break if you implement this fix without "overengineering" it.
A setting to disable what? Be specific. See? Not so simple...
Does that apply to WSL? I would assume everyone develops on WSL these days if they have to use Windows, at least...
And I say this as someone that loves the Unix philosophy dearly.
Google is in a unique situation to protect their users, and they also want to avoid serving search results that are malicious (yes, I know about their ads problem) - so they are proactive about scanning for sites that are malicious so they can avoid sending users to them.
The link you posted literally only lists the scanner related to security/safe browsing. Why would it? What kind of bot would that be if an attacker could just put up a robots.txt that causes it to ignore the site?! And many do...for obvious reasons.
It's misleading because this implies you're getting heavy scraper traffic from Google bots that don't respect robots.txt for reasons of greed rather than because it's necessary so they can proactively avoid surfacing malicious websites.
Two things can be true at once.