C, because yes.
powermaker450
I missed something didn't I?
other distributions should start having an option for this in the GUI installer, but it might be tricky for the average user
Arch Wiki has a guide on FDE using the TPM and it's transparent in my everyday usage
some minor issues I see are:
- Secure Boot needing to be disabled then re-enabled during install for it to work as intended
- needing to write down a long backup passphrase, but this also happens on Windows and MacOS iirc
pickles
only to the extent of what you can do on stock android. implementing changes that enable customization is unfortunately not on Graphene's radar, it's security focused changes
then don't.
it's not something your being forced to do. it's the lifting of an unnecessary restriction that in turn gives you more power on your device.
Unless I've missed something big, passkeys are pretty easy for me if the website supports them imo.
Using KeePassXC, I click register on the website, register the passkey with KeePass, then it just works when I need to authenticate or login. My database is then synced across all my devices.
Passkey support is yet to come to KeePassDX on Android though, so I'll be awaiting that feature
and this is why uBlock origin is the be all end all of extensions.
never been diagnosed.
agnizing over tasks happens often, and at the same time I'm not actually bringing any pleasure to myself by avoiding it.
ah yes, writing a letter. just like the millions of people that UHC ~~murdered~~ wrote letters to.
UHC and many other health insurance companies in the US will and do let people die in order to keep profits. Brian Thompson was complicit in this process. His murder is fully justified.
I don't want a future where murder and violence is the only way to bring issues to light, but when governments, regulations, and other protections fail us, people get desperate. They are left with no other choice.
this, except it's just an upsetting reminder that the task I'm putting off is not even that hard, yet I'm still not doing it.
probably not true in most other langauges. although I'm not well versed in the way numbers are represented in code and what makes a number "NaN", something tells me the technical implications of that would be quite bad in a production environment.
the definitive way to check for NaN in JS would probably be something like