So you rolled back your root filesystem's system state to a snapshot but did you roll back the kernel you're booting into aswell?
If you didn't, that'd explain the symptoms seen here; you might be booting into a newer kernel than the system state has modules for. Without the appropriate kernel modules, Linux cannot mount filesystems or accept keyboard input. (This depends on which modules are required by the HW and whether they're built into the kernel or copied to the initrd though.)
For debugging, simply boot a live ISO and chroot into the system. The Arch Wiki has a page for that. You should be able to look at the journal inside the chroot and it'll tell you exactly what's wrong.
Note that ProtonMail and Fastmail have quite different feature sets.
ProtonMail does not store your Email in plain text for instance; they cannot read them or be ordered to read them. This comes with some drawbacks such as that standard protocols such as IMAP do not work without a bridge because they necessitates that the server can read all the emails.
I also find it weird that you can't create unlimited addresses on your custom domains.
For the shared domains, limits in this regard are absolutely understandable as the supply is limited but addresses should have next to no cost for PM when they're under my own domain.
It really depends on what it is you're trying to share between machines.
I don't use syncthing but something that fulfils a similar function (git-annex). My Documents repo is set up in such a way that all instances of the repo try to have a copy of everything because documents are very important data and don't take much space. Other (larger) repos only try to have two or three independant copies; depending on how large and important their data is.
I would not "share" it synchronously as @gratux@lemmy.blahaj.zone recommended because in that case the data is only stored on one device and almost always accessed remotely. If the internet connection is gone, you'd no longer have access to the data and if the VPS dies, your data would be gone on all other machines too.
If you want to use Nextcloud anyways, that would be an option.
If all you want to do is have a shared synchronised state between multiple machines though, Syncthing would be a much lighter weight purpose-built alternative.
Depends on how many other users are using the same proxy. If you host piped for yourself using your home internet connection, Google will absolutely know who is watching the video.
The statements "vaping isn't good for you" and "vaping is a lot better than smoking" do not conflict with another; they can both be true.
Whether vaping is an improvement or not depends on what you were doing before. If you were smoking before and are substituting cigarettes for vaping, you hurt yourself a lot less and it's an improvement.
If you weren't smoking before (the case for most teens for example) and would start to vape, you'd be hurting yourself significantly more than before.
You should be advocating to never touch a vape (or cigarette) to non-smokers and to try vaping to get out of smoking addiction to smokers.
Numbers at the start of a line followed by a dot signifies a numbered list item. If you just want the numbers without it being considered a list item, you need to escape the dot like this:
This is a list item
With line break
1 This is not
With line break
1. This is a list item
With line break
1\. This is not
With line break
If you've done an OEM unlock, you effectively already have root access to the device. You could boot a custom recovery right now and modify any system file.
"Rooting" just means using this privilege you already have in order to install a tool into the OS such that you can make use of this privilege while the regular OS is booted.
Go install Magisk and do the safetynet dance. It's a whole thing but should give you a "clean" device from the perspective of unprivileged apps. It's stupid that you have to do this but here we are.
I've yet to find a use-case for "making my system lighter" by exchanging a daemon that takes <0.1% of my total system memory for a bunch of poorly maintained bash scripts.
Proper, integrated packaging is obviously preferred (though as a NixOS user I disagree that that implies an FHS) but this is about "stand-alone" packages. You're missing the point.
I don't get why we didn't just do it macOS style; bundle everything into one directory with a standardised structure and wire up file managers etc. to run the correct executable inside it.
Atemu @ Atemu @lemmy.ml Posts 63Comments 1,439Joined 5 yr. ago 
So you rolled back your root filesystem's system state to a snapshot but did you roll back the kernel you're booting into aswell?
If you didn't, that'd explain the symptoms seen here; you might be booting into a newer kernel than the system state has modules for. Without the appropriate kernel modules, Linux cannot mount filesystems or accept keyboard input. (This depends on which modules are required by the HW and whether they're built into the kernel or copied to the initrd though.)
For debugging, simply boot a live ISO and chroot into the system. The Arch Wiki has a page for that. You should be able to look at the journal inside the chroot and it'll tell you exactly what's wrong.