Same here, joined up when GPM was in beta. Still on the $7.99/month. I really only use it for YTM, so if they ever up my price, I'll cancel and use Tidal or Deezer.

If you're looking for a good resource on jailbreaking and installing KOReader on your Kindle, I highly recommend the guides at https://kindlemodding.org/

It took me way too long to realize it has infinite scroll and keeps repeating, bravo!

> Netflix seems to basically do everything in their power to own the experience of using Netflix as much as possible, short of making a device and OS themselves.

I'm suddenly feeling that the next step for Netflix is making a dedicated streaming hardware device solely for Netflix. Subsidized by ads of course. Like the reverse of Roku.

You mean like PopcornTime? I think it's still around in various capacities and different forks

This is my sole reason for sticking with smart TVs or a streaming device. How is anyone getting proper 1080p+ streams from Netflix using a Linux device? 4K is not necessary, but 1080p at least it's what I need. Not even considering proper HDR support

> How is anyone getting proper 1080p+ streams from Netflix using a Linux device?

Piracy

Here's his post: https://mastodon.social/@Gargron/115569820207257167

One suggestion (feel free to ignore) is to hide the vote counts until after a choice is selected, just to prevent some sort of bias. But again it's your site, thanks for the fun!

done!

Context for this submission:

Apple releases the iPhone Pocket: https://www.apple.com/newsroom/2025/11/introducing-iphone-po...

HN discussion: https://news.ycombinator.com/item?id=45885813

Thanks! I've put a link to OP in the toptext of the other thread.

Ah thought I saw a Helium browser mentioned recently on HN[0] and thought this was the same thing. So this is not the same as this Helium browser [1]?

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

[1]: https://helium.computer/

The repository introduces it as indeed based on Helium [0].

The cool part about Helium is that it's based on patches, rather than forking the full source code. I don't know how sustainable this is in the long term, but it's an interesting approach for sure.

[0]: https://helium.computer/

Not sure what's cool about that. A fork is a patch set, with a ton more ergonomics on top. Passing around sets of patches was what we did before VCSs were common/easy-to-set-up, and it was always brittle and annoying.

Here is a homework for you to see why they do it:

  1. Checkout Chromium's codebase.  
  2. Make a commit and see how long it takes.  
  3. Try to push it to any git hosting service.  

You will discover what's actually brittle and annoying.

And yes, being 10s vs 10000s devs in the same repo isn't fun.

Standard practice for Chromium forks. Chromium's repo is huge, slow, and impossible to diff for your changes with 10000s of other commits. Also, painful to host it anywhere.