5 ms·
Turns out Google also hates 500, 174, 833, 285 and 302 (from generating files from -1000 to 1000).
by CJefferson 5y ago
Turns out Google also hates 500, 174, 833, 285 and 302 (from generating files from -1000 to 1000).
- tyingq 5y agoThat's interesting. 500 and 302 popped into my head as common HTTP status codes. The others don't seem notable to me.
- CJefferson 5y agoAnother bunch of numbers got flagged (186, 451, 336, 173, 266). I deleted the experiment, just in case I got my account deleted for too many naughty numbers.
- Mathnerd314 5y agoThat probably looks even more suspicious.
- apocalyptic0n3 5y agoThis is relatively new then. As part of some testing last summer for how to handle a migration from one Drive to another, I generated a folder that had I think 10k files in it. They were all named 1.txt, 75.txt, 8492.txt and their contents matched the filename (i.e. 1, 75, 8492). They never got flagged for me. That was for a Google Workspace account, though, and they were deleted a few days later once I was done with the tests.
- tyingq 5y agoI did notice it flagged "1", "1\n", but not "1\r\n". Then, it didn't flag "0", but did flag "0\n". So line endings seem to matter as well, but not in some consistent way.
- SecurityLagoon 5y agoThey are probably on some kind of hash list accidently. Its probably not about the content as such.