Both GNU and GrapheneOS have staunch requirements and will accept no compromises.
This is a situation where their requirements don’t align, so they’ll never reach an agreement.
GrapheneOS, for example, is also strictly against making the Fairphone line of phones a little more secure because it doesn’t meet all of their security requirements
In this case GNU won’t certify GrapheneOS as fully open because it includes binaries that aren’t open
The FSF is more along your line of improving the situation where they can
If an attacker gets access to your system, they will be able to ensure you can’t get rid of their access
It will persist across operating system installs
However, this requires them to get access first
Well, a.out doesn’t make much sense these days.
Gotta move to .elf
It looks like an alternative to LocalSend rather than Syncthing
Presumably. The company was made by an ex-Apple designer
I mean, just look at how many patches in Android are marked DO NOT MERGE, DO NOT MERGE ANYWHERE, etc, but are in mainline
Why is there a radio box for RealProducer if you may select FFmpeg or MEncoder? 🤔
I tried to find a manual page for special permissions (s-perm) as well…
Ah, but is this a double blocker or a triple blocker?
git was created because a proprietary VCS was being a dick