Depends on distro, snapshotting and if it’s a immutable distro.

Though Windows users should be worrying more, they don’t have backups and have silently activated bitlocker but ignorance of that is bliss.

Mac user don’t have to worry in my experience.

Can recommend, works offline and online with PWA support and stores everything in Markdown files for easy migration if you want to change your frontend.

Did you follow the guide?

https://docs.searxng.org/admin/installation-docker.html#installation-container

The next iteration will be a cheese wedge, 1mm thin on one side and 1cm thick on the other.

To fix your deteriorating attention span we’ve decided to administer a controlled electrictric shock every time you click a video.

I read their justifications but I must’ve missed the part where it justifies anything.

Nah i don’t. I can hope though and the backdoor is a threat not just for consumers but also companies.

I hope more follow, would be funny if “all chat apps have to include a back door” leads to “there are no official chat apps”

It is expected, the users inside the container are “real” users. They just get offset inside the container and some mapping is applied:

Root inside the container is mapped outside to the user running the container, everything that has the owner “root” inside the container can be read from outside the container as your user.

Everything that is saved as non-root inside the container gets mapped to the first subuid in /etc/subuids for your user + the uid inside the container.

You can change this mapping such that, for example, user 1000 inside the container gets mapped to your user outside the container.

An example:

You have a postgres database inside a container with a volume for the database files. The postgres process inside the container doesn’t run as root but instead runs as uid 100 as such it also saves its files with that user.
If you look at the volume outside the container you will get a permission denied error because it is owned by user 100100 (subuids starts at 100000 and usid inside container is 100).

To fix: Either run your inner processes as root, this can often be done using environment variables and has almost no security impact or add --userns keep-id:uid=100,gid=100 to the cmdline to make uid 100 inside the container map to your user instead of root (this creates a new image automatically and takes a while on the first run)

I though that was the point of surveys?

deleted by creator

Bro did not get a degree, he got a whole rotation.

Theoretically, google could keep that workaround in the code, yes.

I’m sorry to say but problem solving and computer skills are left at the door.

Maybe the losing $150 part is what is wrong.

Yeah they are now very fine, almost liquid even.

Maybe

actually end up changing anything for the better.

They start at 50€/Month but get cheaper over time!