Google Blew a Ten-Year Lead

Re:Google Blew a Ten-Year Lead by joshuamorton on Wednesday June 24, 2020 @01:00PM (#23630643)

So your contention is that because they check hashes of documents stored on drive for unlawful material, we'll say, that this proves that Google is lying about how it uses data from docs and drive?

Or are you saying they don't actually share any data learned from docs and drive

[ Parent | on HN ]

Re:Google Blew a Ten-Year Lead by throwaheyy on Wednesday June 24, 2020 @01:36PM (#23631167)

Checking a hash of a document unavoidably necessitates reading the entirety of that document.

[ Parent | on HN ]

Re:Google Blew a Ten-Year Lead by skinnymuch on Wednesday June 24, 2020 @01:35PM (#23631138)

What does checking hashes of documents mean? Isn’t stuff either encrypted or not?

This might not be a good look for me to be confused by this as a web dev/programmer, but I does that mean they are securely or otherwise hashing everything they store on all users? Drive, Gmail and other Google services have tons of data. After THats they are also still only checking hashes?

[ Parent | on HN ]

Re:Google Blew a Ten-Year Lead by virtue3 on Wednesday June 24, 2020 @01:21PM (#23630947)

how would they check the HASH of a document for unlawful material?

I think the complaint was they scan your entire doc, for all it's content.

[ Parent | on HN ]

Re:Google Blew a Ten-Year Lead by joshuamorton on Wednesday June 24, 2020 @01:41PM (#23631225)

> HASH of a document for unlawful material

This is ~super common with things like copyright violations and child porn. You store a database of hashes of copyrighted or pornographic data. And specifically you can use visual-similarity hashing to detect even somewhat perturbed documents.

(https://en.wikipedia.org/wiki/PhotoDNA)

[ Parent | on HN ]