Live data from Hacker News

The Quest for Netflix on Asahi Linux

da.vidbuchanan.co.uk

101–110 of 293 posts

Re: The Quest for Netflix on Asahi Linux

#101
post #82
post #72

Earlier quoted context omitted.

You know we had that, they called it HDCP. It continues to frustrate users of beamers and what not today, despite the root key being leaked for many years now. Even before the key leak, it never did anything to stop shows appearing as torrents on day one. It will never work, if pirates have to replace the TV panel with an FPGA, they will happily do so.

> It will never work, if pirates have to replace the TV panel with an FPGA, they will happily do so. Evidence does appear to point to you being right, but I really wonder just who is going to these lengths to pirate things for other people? A significant investment of time and money, from highly a highly skilled individual, for... bragging rights? Is there some financial motive I'm unaware of?

An enterprising and skilled hacker or group of hackers finds rich financial backers to invest in the equipment and time necessary to build a solution. There’s probably a whole underground scene or multiple connected scenes working on this stuff, composed of both hackers and their supporters.

Re: The Quest for Netflix on Asahi Linux

#102
post #79

Earlier quoted context omitted.

Netflix doesn’t do it because they want to. They do it because it’s part of the licensing agreements they sign to get content.

If it was the whole story, they'd put their own content (the rare ones for which they have 100% of the rights) with no DRM and the maximum resolution. But they don't do that. In some cases you might get 720p (Netflix content) instead of 540p (third party) with widevine L3.

Why would they do this if they've already gone to the trouble to solve the problem for content they don't own? Just to show off by taking on unnecessary risk? The fact that they didn't build this infra specifically to protect their own content doesn't mean they wouldn't enjoy the benefit of the extra protection anyway.

Re: The Quest for Netflix on Asahi Linux

#103

> The only officially supported way to use Widevine on Linux is using Chrome on an x86_64 CPU. To be precise it is "The only officially supported way to use Widevine on Linux is using Chrome on an x86_64 CPU using glibc." In other words, even though I have x86_64 cpu, since I'm on alpine, I'm fucked anyway.

If you are using alpine as a desktop distro, don’t you have bigger problems than Netflix not playing?

(also how are you even using alpine for desktop. I tried to look it up once and gave up soon)

Re: The Quest for Netflix on Asahi Linux

#104

For some reason, my Jellyfin and Navidrome instances doesn't use Widevine (garbageware) in any way. Radarr, Lidarr, Sonarr, and the other Arrs work beautifully to control what media I want, get it, and store it appropriately. And the files I download from Usenet and Torrents work on any platform powerful enough to play them. I was treated like a criminal when legitimately buying media years ago. Already learned https…

> Navidrome

Thank you. The two things I don't like having in Jellyfin are music and youtube videos (the latter are a real PITA if what you've ripped doesn't have a TVDB entry, which, fortunately, some Youtube series do—yeah, there's a 3rd party plugin to help out, but it's so unhelpful I stopped using it completely, broke other stuff, very fiddly, not worth it)

This gives me what looks to be a much-better solution for at least one of those. Looks like I'll be adding another docker container to my server this evening.

Re: The Quest for Netflix on Asahi Linux

#105
post #82
post #72

Earlier quoted context omitted.

You know we had that, they called it HDCP. It continues to frustrate users of beamers and what not today, despite the root key being leaked for many years now. Even before the key leak, it never did anything to stop shows appearing as torrents on day one. It will never work, if pirates have to replace the TV panel with an FPGA, they will happily do so.

> It will never work, if pirates have to replace the TV panel with an FPGA, they will happily do so. Evidence does appear to point to you being right, but I really wonder just who is going to these lengths to pirate things for other people? A significant investment of time and money, from highly a highly skilled individual, for... bragging rights? Is there some financial motive I'm unaware of?

Often it’s people motivated to watch something otherwise unavailable to them. Then the technique is easy to use for other content, so why not?

Re: The Quest for Netflix on Asahi Linux

#106
post #86

Earlier quoted context omitted.

The terminology should be either "License", "Buy a License", or "Purchase Indefinite License ", but it's distinctively "not renting" since it's a one-time cost to obtain that indefinite license. Renting anything implies and requires some form of ongoing cost.

What "indefinite license"? They can, and do, take content off at any time...

"Indefinite" in this context means that there is no set expiration date. It doesn't mean "perpetual" or "irrevocable".

Re: The Quest for Netflix on Asahi Linux

#107
post #66

> Truth be told, I don't care very much about Netflix - the UX offered by BitTorrent is superior.

getting what you want fast. It is literally that easy & netflix messes it up with being nondeterministic and screaming at me trailers I've never asked for. My autistic self is o.u.t.

FYI you can turn off the auto-playing ability of trailers in your settings on the website. They will then take affect in any Netflix app you use, too. It's stupid you can't set it from the app, but I turned off autoplaying trailers the day it came out and have liked using Netflix a lot more since then.

Re: The Quest for Netflix on Asahi Linux

#108
post #97

Earlier quoted context omitted.

It does indeed! Even the alpha GPU drivers work. Not working: speakers, power management isn't ideal and I don't believe Thunderbolt works, although I haven't tried. I'm not sure what a casual driver on the go is..

Thanks! I wasn't sure if was even going to bother qualify the statement further. Mostly use it for light browsing or just light coding, nothing substantial. Reading the docs of a newly released framework etc. Some video-calls here and there, but I have other devices if I can use this purpose.

You can see support is coming along nicely, with many things supported in the kernel directly or in one of the two yet-to-be-upstreamed packages. There's no hardware video encoding/decoding and no webcam support yet, so I don't think doing video-calls would be very good at this point. https://github.com/AsahiLinux/docs/wiki/Feature-Support#m2-s...

Re: The Quest for Netflix on Asahi Linux

#109
Anyone who knows some technical detail about Widevine, please could you explain what is the difference between L1 and L3 (other than resolution/quality)?

How does each interoperate with EME?

And what sort of process would one need to do, to be able to view an L1 stream on a bespoke Linux distribution, rather than the L3 stream that this person received? How difficult is it to do, and what are the specific challenges?

Re: The Quest for Netflix on Asahi Linux

#110
post #62

Earlier quoted context omitted.

> since the HDCP protecting the inevitable HDMI video output has been thoroughly cracked My impression is the stuff coming from the various streaming services is not captured and reencoded, but direct bit-for-bit copy of the original H.264 (or H.265) encoding (sans DRM). (Yeah, others will do reencodes later but quite a bit of the source material encoding comes directly from the streaming sites.)

You're right that there is plenty of directly stream-ripped content out there, presumably using cracks of various levels of Widevine. The makers of these tools and the groups using them tend to keep quiet about the details of the precise exploits they're using, for obvious reasons. Ultimately, there's no shortage of DRM-free 4K content, whether from streaming services or Blu-Ray, since there's always a weak point in…

Yeah. With blurays, you can always extract the device key out of some Bluray player. It's an extremely poor user experience for bluray consumers to have their devices stop working for new movies, so my impression is these keys aren't blacklisted all that quickly. For the streaming sites, I have no idea. But, yeah, the cleartext bits need to get in front of the user eventually.
Post reply on HN