News for hackers. Stuff that matters.
Re:Google Docs Is Randomly Flagging Files for Violating Its ... by s3r3nity on Tuesday October 31, 2017 @01:23PM (#15594868)
I don't know if it's fair to say that they are "randomly" flagging items - I'm guessing they're using a similar set of tools that they use to algorithmically determine if, say, Youtube videos violate their TOS.

Probably a recent update / bug increased the number of false positives more than expected.

Not that I'm sympathizing with Google - just seeing if there's a less click-baity reason for what's going on.

Re:Google Docs Is Randomly Flagging Files for Violating Its ... by mikeash on Tuesday October 31, 2017 @01:33PM (#15594948)
I think “randomly” is being used here in the sense of “without a good reason.” Regardless of how the content gets classified, they shouldn’t be policing private files.
Re:Google Docs Is Randomly Flagging Files for Violating Its ... by duality on Tuesday October 31, 2017 @03:07PM (#15595715)
The anecdata from Twitter were stories about shared docs getting flagged as a ToS violation. Did anyone see the false ToS violation on a totally private, unshared file?
Re:Google Docs Is Randomly Flagging Files for Violating Its ... by mikeash on Tuesday October 31, 2017 @03:47PM (#15595964)
Where do you get that from? I randomly checked a few of the tweets and didn't see anything about shared. Nothing about private, either, but that seems like a reasonable default assumption.
Re:Google Docs Is Randomly Flagging Files for Violating Its ... by billsmithaustin on Tuesday October 31, 2017 @02:24PM (#15595359)
Yup. It's a big leap from "Google has a bug" to "you don't control any of your content on the Internet."
Re:Google Docs Is Randomly Flagging Files for Violating Its ... by confounded on Tuesday October 31, 2017 @01:28PM (#15594914)
Well, even a PRNG is deterministic at some level. I think it’s a fine descriptor given the context.