"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…
Google Drive flags file only containing “1” for copyright infringement
171–180 of 464 posts
Re: Google Drive flags file only containing “1” for copyright infringement
#172Re: Google Drive flags file only containing “1” for copyright infringement
#173File 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
#174Earlier quoted context omitted.
It hurts me to even think about this. We're headed towards such a bleak future. The only solution I can think of is to kill copyright in order to save computing freedom. Otherwise our computers will eventually no longer be ours.
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.
Any tort in law also has secondary liability attached to it, and it's generally accepted caselaw that online service providers get secondary liability if someone uses them to infringe. Congress decided that said providers should be able to disclaim that liability if they participate in a notice-and-takedown process; and the EU has gone further and replaced that with a very context-sensitive "best practices" approach that almost certainly will be interpreted as "video sites must have an equivalent to YouTube Content ID".
From an old media perspective, this is crazy. If CBS licenses a TV show that infringes upon a third-party copyright, they cannot disclaim liability by saying it's the licensee's problem. If they could, then you could construct a bunch of LLCs to separate the infringement from the liability. And this is effectively what online services have done: YouTube, for example, gets to automatically[1] recommend you infringing content, and those who have been infringed only have the legal recourse of sending takedown notices.
Getting rid of the takedown system would mean that copyright owners would have to go back to suing individual users, which is both expensive and, IMO, wrong. YouTube gets to own online video and infringe copyright with impunity, because they passed the buck onto individuals that largely cannot afford to pay damages on infringement. If you're a legitimate[2] user of copyright, you can't economically get the infringement to stop or go underground. Furthermore, if you are a copyright troll, this does nothing to stop you; you will still be able to sue individuals and coerce them into settling baseless claims.
The underlying problem is that online platforms want to half-ass copyright. You can decide whether this is because they understand the draw that infringing content provides to them, or if proper enforcement interferes with the FAANG business model of "own the platform and take 30%". Either way, it's a compliance cost. We don't want people just suing individuals, and we don't want people suing online services to the point where any amount of third-party content is too legally perilous to touch. The answer was supposed to be notice-and-takedown, which is designed basically as a way for online service providers to push papers around between copyright owners and users without having to resort to an expensive lawsuit.
However, nobody likes this. Online service providers that try to do things "by the book" wind up with all sorts of legal pitfalls for both themselves and their users. So even the current notice-and-takedown regime in the US has been subverted by private agreement. For example, DMCA 512 requires copyright owners to actively monitor infringements of your work; but YouTube Content ID instead provides a turn-key solution to find infringing work on that platform. It also lets you just monetize the infringements instead of taking them down, which is also a sort of backdoor license for Google. I suspect some sort of similar arrangement is involved with Google Drive, where you can't share files that trip whatever content ID system is involved here.
So even "killing vigilante enforcement" would not be good enough, because Google has already found it lucrative to privilege copyright owners over regular users. You need to specifically regulate these takedown alternatives rather than just getting rid of takedowns.
[0] Technically speaking, a DMCA takedown notice from someone who does not own the copyright to the work in question is legally deficient and can be safely ignored by Google. However, most online service providers do not do a good job of checking.
[1] As per Mavrix v. LiveJournal, the process has to be automatic. Human curation takes you out of your DMCA 512 safe harbor. This is effectively a "willful blindness" requirement, IMO, which is also bad.
[2] As in, you're interested in preventing sharing of newly-published works for a reasonable time frame, rather than keeping an ironclad grip on Steamboat Willie or Super Mario Bros forever.
Re: Google Drive flags file only containing “1” for copyright infringement
#175"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…
Re: Google Drive flags file only containing “1” for copyright infringement
#176Re: Google Drive flags file only containing “1” for copyright infringement
#17715 years ago the first word that came to mind when thinking of Google was “magic”. 10 years ago “useful”. These days it’s just “dread”.
I think dread is a bit over dramatic. I still find utility in Google Maps and GMail. Some products in the Google domain are heading that way but I don't dread Google I treat them as a business with respect to my coupling to them on a case by case basis. I used to be a Google first, now I am one to look at all options and decide if its worth coupling something else in my life to Google. In many cases its not worth it…
Re: Google Drive flags file only containing “1” for copyright infringement
#178Re: Google Drive flags file only containing “1” for copyright infringement
#179Earlier quoted context omitted.
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.
As someone who dealt with identity theft, SSN should only be collected if contact with the SSA is needed. I.E. payment of social security benefits.
Any and ALL other "ID", nope. Use some other number.
Re: Google Drive flags file only containing “1” for copyright infringement
#180I 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…
This is another case for only pushing encrypted files to storage hosts, unless it's against Google Drive's TOS or something. Has anyone tried it? Did Google complain?
openssl enc -e -aes-128-cbc -in ${1} -out ${1}.cr -iter +123456 -k