jpeg xl! wow! that's cool!
WhyJiffie
separately, part by part. if they had a laptop they would have needed to buy at least 6 complete laptops by that time, or more realistically, give up on upgrades.
don't enable unsigned extensions. It's there for good reason.
upload your addon to addons.mozilla.org. there's an option to not publish, but only upload for signing. then you'll get back a signed xpi you can install properly.
that's why I believe that in a normal world, renting should only be needed for temporary hardware. a temporary home, a temporary vehicle, a temporary server, temporary storage..
but with homeservers you could have your own once you can afford it, and you could request help from contractors for the urgent type of maintenance. replacing failing disks in the array, minimal monitoring so that they can keep an eye on when that happens, maybe critical updates..
who cares about trump here. he's just the catalyst that started the process we long needed. american big tech has for much longer been parasitic and anticonsumer, and that's not on trump. every administration before that was fine with it too.
yes you violated, and that's out of question.
they upload your medical information to advertisers and data brokers, and connect it to your name and email address, that's what needs an account.
that's peertube too
an open source app for wearables, its on fdroid. works without contacting manufacturer servers, but for some devices you might still need the official app for first time setup
I guess it's just google sans, they use this placeholder elsewhere too
oh, LXC containers! I see. I never used them because I find LXC setup more complicated, once tried to use a turnkey samba container but couldn't even figure out where to add the container image to LXC, or how to start if not that way.
but also, I like that this way my random containerized services use a different kernel, not the main proxmox kernel, for isolation.
Additionally, having them as CTs mean that I can run straight on the container itself instead of having to edit a Docker file which by design is meant to be ephemeral.
I don't understand this point. on docker, it's rare that you need to touch the Dockerfile (which contains the container image build instructions). did you mean the docker compose file? or a script file that contains a docker run command?
also, you can run commands or open a shell in any container with docker, except if the container image does not contain any shell binary (but even then, copying a busybox or something to a volume of the container would help), but that's rare too.
you do it like this: docker exec -it containername command. bit lengthy, but bash aliases help
Also for the over committing thing, be aware that your issue you've stated there will happen with a Docker setup as well. Docker doesn't care about the amount of RAM the system is allotted. And when you over-allocate the system, RAM-wise, it will start killing containers potentially leaving them in the same state.
in docker I don't allocate memory, and it's not common to do so. it shares the system memory with all containers. docker has a rudimentary resource limit thingy, but what's better is you can assign containers to a cgroup, and define resource limits or reservations that way. I manage cgroups with systemd ".slice" units, and it's easier than it sounds
perhaps we should try some kind of conversion therapy on them
how did you try? did you try registering a mozilla account?
It's probably temporary, it doesn't have problems usually
they do it so that malware cant install unvetted addons to your browser. and if someone signs a malware addon this way, and some people report it, mozilla can disable it for everyone.
what you need is a footgun. you have it in about:config.