I don’t know, if your goal is security Pixels have the best hardware and GrapheneOS the best software. It makes a lot of sense.
I don’t know, if your goal is security Pixels have the best hardware and GrapheneOS the best software. It makes a lot of sense.
You can destroy it all the same with cp
or cat
.
The quote is not about installing security patches but implementing them. Terrible paper.
I don’t think this is of interest, this is an article in a student journal, written by one person which seems to be a student too. The quote is weak and cherry-picked.
A quote from the same paper:
Security measures in Linux are slim to none as it is a free OS to download.
I don’t see what you can do at the protocol level to improve availability, you still need people storing the file and acting as peers. Some trackers try to improve that by incentivizing long term seeding.
Like the 13.1 torrent being only a patch to the 13 one and listing it as a dependency? Downloading the 13.1 torrent would transparently download the 13 if it wasn’t already, then download the 13.1 patch and apply it. But I don’t think any of this needs to be at the protocole level, that’s client functionality.
Yeah, that’s my issue, NixOS is so stable I never had to reinstall.
Being decentralized prevents DNS or IP blocks but not blocks through DPI.
Signal has an option to masquerade it’s traffic as regular HTTPS, I don’t know if Matrix can do such a thing.
Fuzzy finding really shine for this use case, no need for a mouse.