301–310 of 464 posts
Earlier quoted context omitted.
I wonder if this is an incredible hash collision. hash("1") == hash(disney_movie.mp4)
Assuming is's a cryptographic hash function, that sort of collision just never happens.
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…
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?
Earlier quoted context omitted.
Technically any creative work you author is copyrighted, so your comment was copyrighted anyway. Whether or not large tech companies will punish people for infringing upon your copyright is yet to be determined.
I don't know about US lawy but in German law there is a requirement on some originality. ("Schöpfungshöhe") The barrier is low, but a 1 certainly doesn't receive the protection.
Earlier quoted context omitted.
"Computer says No!"
No? Why is this computer talking about Norwegian?
Earlier quoted context omitted.
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…
Italy: https://ilmiocf.it lets you generate your equivalent of an ssn (fiscal code). And, yes...if you know someone's very basic details you have the number. For US viewers, enter 'stati uniti' as 'comune di nascita'. Use deepl.com for the bit at the bottom.
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…
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
Earlier quoted context omitted.
Assuming is's a cryptographic hash function, that sort of collision just never happens.
Well, it has to happen at some point. Exceedingly unlikely, but never say never.
Of course, it’s always possible that the particular hash function used could be hilariously broken…
All software has bugs; I'm not mad at all that this silly test case was flagged incorrectly. The truly infuriating part is "A review cannot be requested for this restriction." Translation: "We have no idea if you actually own this content or not, but it would be _way too expensive_ for us to find out for sure! So you're out of luck, but don't worry — it's all worth it so we can make sure children can't stream Marvel…
We've gone from copyright as a mechanism for sharing works and licensing others to a situation where there are the in-group, the big media corporations who are allowed to license and remix content, and a sub-class who essentially are not.
Earlier 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
That’s it, kids, the internet is now illegal — until we switch to a quaternary system using only 2’s and 3’s
Earlier 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
Relevant Onion article here: https://www.theonion.com/microsoft-patents-ones-zeroes-18195...
https://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2...