Earlier quoted context omitted.
> SSNs should be treated ... 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.
I definitely agree, but in america it's impossible to be legally employed without your employer having your SS# on record.
Google Drive flags file only containing “1” for copyright infringement
191–200 of 464 posts
Re: Google Drive flags file only containing “1” for copyright infringement
#192Always 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.).
3 copies of the data,
2 of which are on different, local mediums (i.e. hard drive and a thumb drive)
1 of which is offsite (cloud storage, safe deposit box, salt mine, etc)
Re: Google Drive flags file only containing “1” for copyright infringement
#193Earlier quoted context omitted.
> 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.
Which is a problem of its own, since they're effectively usernames. Secure usernames that have no corresponding password is already an oxymoron; that's what credit card numbers used to be, hence the introduction of the CVV, 3DSecure and so on; but at least a credit card can be blocked with relative ease. But SSNs are secure unchangeable usernames, which makes even less sense. Do any countries other than the US have s…
https://faq.ssa.gov/en-us/Topic/article/KA-02220
It's a huge pain, obviously. Especially when you get to all the systems which blindly assume it isn't possible. But you can do it.
They ought to just open it up and let anyone who requests to change it once a year no questions asked.
Re: Google Drive flags file only containing “1” for copyright infringement
#194Earlier quoted context omitted.
> SSNs should be treated ... 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.
You say things that are true, and yet they are inconsistent with existing practice. Is there a word for this?
Re: Google Drive flags file only containing “1” for copyright infringement
#195Earlier 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.
Re: Google Drive flags file only containing “1” for copyright infringement
#196I'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…
Re: Google Drive flags file only containing “1” for copyright infringement
#197Earlier 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.
Re: Google Drive flags file only containing “1” for copyright infringement
#198File 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
Can you file a counter-notice _in absence of_ a DMCA notice? The problem at hand is not DMCA.
Re: Google Drive flags file only containing “1” for copyright infringement
#199Earlier quoted context omitted.
Update: It has now flagged the file with "0\n" in it. So it's official, Both 0 and 1 are copyrighted :) https://imgur.com/a/xMgh6Xn
Does that mean someone copyrighted binary? :p I guess that mean that this comment and everything digital is copyrighted.
Whether or not large tech companies will punish people for infringing upon your copyright is yet to be determined.
Re: Google Drive flags file only containing “1” for copyright infringement
#200I'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…
It looks like those files are marked as public. Does it trigger for you on files not being shared?