I think XFCE has way more themes etc. Both are extremely themable though.
I think XFCE has way more themes etc. Both are extremely themable though.
Swap is only needed for emergencies, if you have a bad oom, and if you have low RAM.
If you have like 1-4GB of RAM, ZRAM may be better than swap.
Aged like milk
No, I understand your points. I may think you need to specify what you mean by “customizable”. A lot of stuff users normally do, like theming, installing random stuff etc, works. You can layer, build your own image etc.
But this is not the point as OP was frustrated about having an OS that even though promising to be reliable still breaks.
And whining about “oh I cant tweak it” is just not at the correct place there.
But of course my answers were kinda harsh, sorry for that. But these issues are really nonissues if your priority is having a working system.
I mean, Github is literally the source of 2 operating systems I run. And most of my apps.
Yeah that factor may not be wanted. But it is a security factor, because only you have it.
You could hash it securely so the computer gods dont know your fingerprint. And you could only use it in addition to another factor.
Ah okay but is that useful in many cases? Only when you are home.
Really?? This is crazy.
Afaik headscale is the selfhosted server. You can likely login however you want.
Static IPs are not a thing in most countries. You need an overlay network or dynamic DNS like NoIP.
Headscale is a downstream of tailscale, meaning it has a fraction of the features and is maintained by Tailscale employees.
But great for less trust.
To get more versed infos, visit discussion.fedoraproject.org
We have tags there, many knowledgeable people, and can help better.
Run it through the terminal.
You could archive chats encrypted too.
Something you know, something you have, something you are.
3FA:
You could also start with just one of these
Some way to encrypt the decryption key.
This could also mean TPM + Pin. Or using a Nitrokey, externally, which stores the password to decrypt the decryption key.
That is how user account unlocking (on GrapheneOS with Pixel phones) is done.
opportunistic TPM integration would be nice.
I.e. use the security chip of the device, if one is found. Otherwise use password.
OR use a Nitrokey etc, which can act as a secure device to store these keys too.
Take that, Windows. You dont need a builtin TPM if you can use a Nitrokey 3 with a secure element, externally.
Which is still irrelevant for OPs thread. It is actually the opposite. The more you diverge from upstream, the more you need to vendor your changes.
That means if your mums PC breaks, you are responsible ;)
This should be done out of the box. The implementation depends on the desktop.
Which is why for quality assurance, at most 2 desktops should be supported and prioritized like that.
This is not relevant to the topic about issues with the stability of atomic desktops
Try KDE Plasma, you can strip out a ton of it, for example XOrg entirely, baloo, animations, etc.