Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Drive flags file only containing “1” for copyright infringement

twitter.com

Post reply on HN
Print view View original

151–160 of 464 posts

Re: Google Drive flags file only containing “1” for copyright infringement

#151

Post by driverdan »

spicybright wrote: post #143
ChicagoBoy11 wrote: post #13

I experienced something similar building an internal tool on GSuite. I had a large file with sequences of 9 digit numbers specific to our use-case, all tied to names of people (employees). Whelp, at one point the tool I was working on stopped working, and it was flagged as apparently containing social security numbers (which I suppose matched the character length). Whelp, on the admin panel, you can get a report of t…

That's ridiculous. Storing social security numbers is necessary for lots of businesses. Imagine your filing cabinet not letting you file employment forms with a SS# on them. It's the sticky note password problem all over again...

> That's ridiculous. Storing social security numbers is necessary for lots of businesses.

They should absolutely not be stored in a GSuite document. SSNs should be treated more securely than credit card numbers.

Re: Google Drive flags file only containing “1” for copyright infringement

#152

Post by folbec »

tyingq wrote: post #15

I'm curious if it was related to the file name. I created a few 1-byte files with just "1" in them, with different names, including "output04.txt". No problems so far. Also uploaded variations with "\n" and "\r\n" after the "1". And enabled sharing to anyone with the link. No issues so far. Google drive does support metadata like a description and comments. I wonder if someone posted some copyrighted text in a commen…

My bet is someone did a DMCA claim on a file containing 1, either by mistake or as a joke.

Then Automated Stupidity took over.

Re: Google Drive flags file only containing “1” for copyright infringement

#153

Post by AnthonyMouse »

matheusmoreira wrote: post #74
josephcsible wrote: post #56

Earlier quoted context omitted.

Do we need to kill copyright? Couldn't we just kill vigilante enforcement of it? Maybe we should make it the law that if you see a copyright violation, your only legal options are (1) nicely ask the infringer to stop voluntarily, or (2) sue.

Copyright is fundamentally a monopoly on data. The very name implies that you can restrict who can copy data, how many copies can be made. Copying data is among the most basic, fundamental computer operations. Therefore all computers are inherently capable of violating copyright, they merely need to be instructed to do so. It's the 21st century and copyright is absolute nonsense. Computers make it seem absurd by triv…

> So in order for copyright to exist in the 21st century, it must be impossible for us to instruct computers to do anything.

This is not true. It could be enforced by courts and not by computers.

Courts are slower and more expensive, so they'll only be used for the most egregious violations. But that's fine. Those are the high value ones. You wrote some code or made a movie, Netflix wants to use it, Netflix has to pay you for it. Because Netflix is big and you can sue them.

> We cannot be allowed any control because we can easily subvert their business model.

The assumption here is that everybody wants to subvert their business model. For the RIAA that might be true, but we don't need the RIAA. They can lose. Specifically because they're crooks and nobody respects them.

But already right now I can find basically the entire Netflix catalog on BitTorrent sites, and still I pay them.

And look at Substack. You have people making content, the readers respect the writers, so they pay. In many cases even when the articles are available without paying or after only a short delay. Because the readers know they won't be created if the creator has to go dig ditches instead for money.

We should get rid of DMCA 1201 (prohibiting circumvention of DRM). We don't need to get rid of the law that prevents Google News from hosting the full articles on their own servers while stripping out the subscription links.

Re: Google Drive flags file only containing “1” for copyright infringement

#154

Post by Animats »

File a DMCA counter-notice, of course.[1]

You may have to do this the hard way, via Google's address for service of process.[2] Use registered mail or FedEx.

There's also the option of taking Google to arbitration. Legal advice from one of those "free quick consult" services may be helpful.

[1] https://www.nolo.com/legal-encyclopedia/responding-dmca-take...

[2] https://support.google.com/faqs/answer/6151275

Re: Google Drive flags file only containing “1” for copyright infringement

#155

Post by withinboredom »

jrockway wrote: post #7
version_five wrote: post #2

"A review cannot be requested for this restriction" ML enforcing rules is bad enough, but not allowing false positives to be corrected is ridiculous. This is why I would never consider g-suite for any business application. Otoh, I think there is a legitimate business to be made helping small businesses and individuals secure themselves against arbitrary behavior from big tech. This kind of thing can have serious cons…

How long until cloud providers are forced to scan block devices, so you can't even self-host a file erroneously flagged by the ML? (Actually, how long until this is integrated with the "security engine" in CPUs, so you can't even hide with encryption? Everyone is talking about on-device voice-recognition and CSAM recognition, but no doubt the copyright lobby is going to push hard for this as well.)

I have an email from myself to myself sent in 2007 in GMail. I can't open the attachment because "it is malicious." It doesn't, just a schematic, but there's no way to tell GMail to let me download it anyway.

Re: Google Drive flags file only containing “1” for copyright infringement

#157

Post by miohtama »

IshKebab wrote: post #107
kevin_thibedeau wrote: post #69

Earlier quoted context omitted.

If the full DMCA process was implemented, takedowns could be immediately reverted and then the trolls would have to use the court system as intended. Abusive behavior from bad actors could then be addressed.

This isn't a DMCA takedown.

This is actually a fair point. Thus, this should limit Google’s escape intoany safe harbour. Though still leaves the problem who is going to go after Google for them locking users out from their own files.

Re: Google Drive flags file only containing “1” for copyright infringement

#158

Post by quickthrower2 »

Qub3d wrote: post #136

Always operate under the assumption that iCloud (Apple), Microsoft and Google will delete any/all of your data, with no notice, and for no reason. Because they explicitly reserve the right to do so in their TOSes. Not your computer, not your data etc. ( https://www.quentb.com/posts/diy-cloud-backup/ )

Cloud drives are a cache. (Actually treat all storage as a cache, i.e. the data will be lost, it's just a matter of when.).

Re: Google Drive flags file only containing “1” for copyright infringement

#159

Post by nocturnial »

Just call google support... oh... wait... right...

I wonder how many ads we need to watch before google implements something even remotely similar to user support? How many billions are enough before we get support?

I know I'm overreacting but I'm getting tired of these articles. We all know that google is messed up (to put it lightly). Some people here don't think that's the case and that's fine. Other people, including me, don't find it surprising at all.

Post something about google killing cute kittens.

I wouldn't be surprised but I would be interested in that story.

Re: Google Drive flags file only containing “1” for copyright infringement

#160

Post by quickthrower2 »

blunte wrote: post #61

Ironically, it may end up being one of these "tiny" scenarios which finally does Google in. When trying to illustrate a problem or bug, one of the typically time consuming challenges is reducing the scenario to the minimal case which illustrates the problem. So thank you, @emilyldolson! Aside from an empty file, you cannot reduce this any further. It brings to light in simple terms that non-techies can understand how…

It's a real motivator to leave Google and the MAG cloud in general. It has at least reminded me again to do regular Google takeouts.
Post reply on HN