gila

Okay you got me with this one. Excepting one category of Apple products, you would need to go back about half a century to find an example of a major hardware manufacturer that is worse at “allowing” open source operating systems.

https://store.steampowered.com/app/385380/Planet_Centauri/

They did kinda abuse early access to crowdfund development for a very long time. 100k+ copies sold is not a bad result overall. The bug is pretty unfortunate, but they didn’t exactly set themselves up for future financial success. Seems more like an unfortunate factor in the “flop” rather than the ultimate cause of it.

The game does look interesting though and if they can regain enough momentum off a daily deal and/or future discounts to fix some of the issues mentioned in the post-1.0 reviews, I’ll definitely consider getting it on sale.

You’re right, the messages would not be decrypted by the server but by the client making the report. Key rotation also shouldn’t be an issue because it uses a ratcheting chain key. But if the non-malicious client is already set up to send decrypted messages to the server, this seems antithetical to the idea that WhatsApp can’t read your conversations. There are clear caveats without even introducing the idea of a malicious client potentially exfiltrating decrypted messages elsewhere. Signal on the other hand receives the reported senders phone number and an encrypted message ID, presumably acting on spam reports by relying on multiple reports of the same message from the same sender, rather than by reading the message

https://faq.whatsapp.com/414631957536067/

Either the report function doesn’t work like they say, or messages are stored decrypted, or they can decrypt messages at will based on a simple request from another user

Edit: fixed

Niagara launcher has “pop-ups” on swipe which can act as an app folder, or display app shortcuts or widgets. Not exactly the same behaviour but imo tidier & more elegant approach to basically the same use case.

Oh they figured it out alright, that’s how the current players were handed the keys to the industry and why they take the more insidious DRM approach to controlling the content they own. They understand it’s less likely to cause customer to revolt than the fundamental problems with the movie/tv show distribution business model that came before. And tbh they’re right - yeah I pirate, but mostly because that’s what I’ve done for 30+ years at this point. People have been saying the most recent anti-consumer decision by Netflix will finally be their downfall for like a decade - their stock is now at all time highs.

You aren’t wrong that people will prioritise convenience/features highest but make no mistake, these companies are fully aware of the impact of their shitty practices. It’s all calculated.

A custom skin with widgets on the home screen pulling from Trakt, TMDB, IMDB etc lists - here I have the “New” category set to “Trending Recent Shows” from Trakt to highlight actually new stuff, whereas “Trending” category is set to “Trending This Week” from TMDB to cover returning shows. This approach inevitably leads to duplicates but at least covers everything important without the perpetual The Office, Breaking Bad etc results. When a title is highlighted, network badge is shown where available. The categories that point to individual episodes autoplay upon selection, the ones that point to series go to the ‘folder’ type browser

Search page overriding default kodi search, categorised by movie / tv show, also includes trakt lists.

Heaps of navigation and backend customisation, too much to show or mention but some notable things being the play next dialog including display prompt being based on end of subtitles track (with time-based backup), customised context menu including option to play trailer (displayed via long press on remote, requires youtube API key for HD trailer playback), codec prioritisation/blacklist, overriding local watched/unwatched status with trakt, partial playback resume including auto resume option

FWIW these examples are on a minimally configured proof of concept instance, when I set this up for family I need to test and tune it a bunch to ensure codec compatibility with the device/display, auto resume if that’s the behaviour they want etc. Base Kodi also allows to prefer non-hearing impaired subtitle tracks, audio tracks in a specific language or original language etc. The end result being they get what they want spoonfed to their home screen the vast majority of the time, and otherwise can find it easily with the search without hassling me lol. In the worst case scenario I need to show them how to rescrape/source select from the context menu, but that’s only happened once where an older title’s only cached release had russian-only audio. The rest of their time they can just choose an episode/movie without having to understand any specifics about whether the top result is the best stream or not. It’s enough that I’m still finding more UX improvements to add, years later.

I’d love to have this set up for usenet but don’t have any issues using torrent cache on torbox essential so just can’t really justify the cost difference

The Kodi add-on I’m using uses torrentio in the backend, but has way more customisation than the stremio app + trakt integration, autoplay using preset quality filters etc

Stremio app is more seamless experience when there’s no hits for the title already in debrid cache but that’s pretty rare these days even on torbox

The problem with a wrapper as you put it, specifically one running on Linux, is DRM. The only way I know of to achieve the desired Widevine encryption level is running the service in a tab in Chrome. Not any other browser, not even Chromium.

Of course you could just bypass all that nonsense by pirating your media, and have a nice easy interface consolidating titles from all streamers - even retaining a network badge so they can see where a given popular show is airing - like what I’ve set up in Kodi for myself as well as boomer relatives.

Other than that I’d recommend Flirc for input via remote (or LIRC if you have a supported remote already and don’t mind some extra configuration)