←back to thread

"Widevine Dump":Leaked Code Downloads HD Video from Disney+, Amazon, and Netflix

(torrentfreak.com)
449 points bertman | 1 comments | 27 Dec 21 12:55 UTC | HN request time: 0.206s | source
Show context
vmception ◴[27 Dec 21 14:56 UTC] No.29702940[source]▶
This is one of those github repositories that you just clone and move on.

Don't fork, just clone to your local system. When it gets taken down the forks will disappear, whereas the clones will not. You can also just download a zip file.

https://github.com/widevinedump?tab=repositories

replies(3): >>29703359 #>>29703386 #>>29703653 #
jrm4 ◴[27 Dec 21 15:42 UTC] No.29703359[source]▶
"Making an imaginary-ish copy that stays on the big Microsoft-owned system is mostly unnecessary and probably not enough to keep it around, make sure you save a copy on your own computer that they can't get to."

Don't want to be (too) condescending, but, as an old-timer it's kind of wild to me that people who work with tech a lot do actually sometimes need to be reminded of this.

replies(4): >>29703445 #>>29703620 #>>29703744 #>>29703746 #
1. vmception ◴[27 Dec 21 15:51 UTC] No.29703445[source]▶
Its wild to me too, but I've seen people actually debate fork perseverance and I'm always confused what the issue is when you can just have a local copy but somehow that often never gets brought up in those conversations. Its not even about something used in a package manager, they just really had no backup when the default behavior of the git protocol is to have a backup. I'm like "wait did they actually lose something?" so since that seems to be the case, yeah, gotta remind people.