Last commit is two years ago, but still a good overview.

https://www.404media.co/elite-the-palantir-app-ice-uses-to-f...

https://archive.ph/wa32f

At least the older model. Don't know about their latest model with gaming and everything.

I'd say this only applies to huge scale (or monorepos, as mentioned in the article). Another workaround might be gitless gitops via OCI.

Comments URL: https://news.ycombinator.com/item?id=46180944

Points: 45

# Comments: 17

Let me heat up the discussion using this quote

> The Linux kernel has atrocious security. It has an anti-security architecture, implementation and culture. The Linux kernel is not a good base for building any new operating system with a focus on privacy and security

https://grapheneos.social/@GrapheneOS/114665594121762341

While the logic behind it sounds reasonable, REST does the exact opposite with the same goal: simplicity, easy to learn, i.e. reduce mental load. I know there are other reasons for REST/SOAP/Graphql, etc. Still makes mental load a somewhat subjective matter to me.

Comments URL: https://news.ycombinator.com/item?id=43538725

Points: 3

# Comments: 0

> The term [rooting] generally also includes the functionality for making runtime code patches (eg. with Zygisk) and making runtime filesystem modifications (eg. Magisk modules).

> Out of the many root-enabled apps I've studied or reverse engineered, the vast majority fail to handle arbitrary inputs properly (especially filenames). For example, some root-supporting file managers turn a seemingly benign action like listing a directory into local privilege escalation. This is trivially exploitable, especially with browsers auto-downloading files with server-provided filenames to /sdcard/Download/.

To avoid repeated root access UI prompts, some apps spawn a long-running shell session, write commands to stdin, and rely on parsing stdout and searching for the shell prompt to determine when commands complete. This approach is prone to desync, which can lead to commands being skipped or other inputs being interpreted as commands.

All in all, I simply do not trust most root-enabled apps to not leave a gaping security hole, so I avoid them entirely. There are apps that do handle root access in what I would consider a more proper way, by spawning a daemon as root and then talking to the daemon over a well defined binary protocol. Unfortunately, this approach is the extreme minority.

Hopefully GrapheneOS deliver on their promise to provide a better backup solutions than seedvault.

Yes, video streaming can be done easily nowadays. But finding a multi-room audio solution that works across different brands and also on offline devices was my main reason for getting into chromcast.

Maybe if I subscribed again, there still would be something. But I won't.

The support person on the phone also told me that everything gets deleted once the subscription ends, even when it's by mistake. Which seems to have been the case with me.

Difficult to avoid though for some cases like streaming. Fortunately I had a backup of my playlists. Still annoying. I wonder if those kinds of things happen with spotify as well. Because once your subscription ends you're only relegated to a free account, not deleted.