Hacker News Reader

Comment by sdfhbdf | Hacker News Reader

Do you have to hand over your whole privacy to google and agree to them collecting data from your grandchildren when installing?

On a serious note I thought Widevine was closed sourced and only licensed in some way, how has it made its way to Raspberry Pi OS without any consents and such? Is it libre? Or is this the new direction of the raspberry foundation to cooperate with big corps? Like when they included the Microsoft apt repository so that people can install vscode in 1 command instead of 4. [0]

[0]: https://news.ycombinator.com/item?id=26035441

View on HN

There‘s all kinds of uses for a Raspberry Pi. Not everyone is in it for ideological reasons, and I‘d argue just watching Netflix on it is a valid use case too.

I'd think privacy concerns over data collection aren't ideological, more ethical.

No data is being collected by the possibility of installing a DRM plug-in, which I understood the grandparent comment to be in objection to.

Preinstalling the plug-in would be an entirely different matter for me, and I'd see the ethical concerns there.

Is it?

I mean, it's still not very good at it - you will only get lower resolutions, and at this point a Raspberry Pi and storage/power/cases are not cheaper than buying a Fire Stick or a Chromecast which works better for that use case.

Not as a primary use case, of course. But if somebody wants to buy exactly one cheap single-board computer, why should they be prevented from being able to watch "non-free" content on it (as long as the DRM required to play it is strictly optional and does not come preinstalled)?

Chromecast still requires another device to send the video to it. Using a media serving device like a pi can mean you avoid tying up another device and the whole solution winds up being just like any other media system attached to your TV. Remote control, and interface.

I don't think that's how Chromecast always works (though it can work that way).

Most of the time, your device(s) tell the Chromecast what to play, and the Chromecast plays that on its own. There is integration which tries to sync the UI on the "controlling" device to the playback of the Chromecast but this fails often enough for me that it's clear that (in my case) my phone isn't streaming to the Chromecast directly unless I'm screen mirroring.

> a Fire Stick or a Chromecast

Corporate scrip is essentially fine too if all you care about is buying cheese (and you can exchange it for cheese...), but that doesn't mean that it's good or that regular money isn't objectively better.

But in this case a Pi is literally worse than either of those things at doing the video playback use case for the same investment. It's not a case of the Pi being as good but doing other things, you compromise the use case.

When the cheese is higher quality and cheaper with scrip, then regular money isn't "objectively better". It's a tradeoff and suggesting someone use scrip to buy cheese is quite reasonable.

It's not installed by default, users need to install it (sudo apt install libwidevinecdm0). Previously it wasn't available at all though, at least not in an official way.

These are some unofficial ways of getting Widevine on a Pi (no longer needed now): https://gist.github.com/ruario/19a28d98d29d34ec9b184c42e5f8b... https://blog.vpetkov.net/2020/03/30/raspberry-pi-netflix-one...

Raspberry Pi has basically forever shipped closed components, that's not some "new trend"...

Reply on news.ycombinator.com