Memory is fine. I ran a couple disk checks as well and it’s also fine. I was also using two SSDs during the process with no difference in the problems experiences.

The rules are purposefully vague and interpreted to fit the particular political motives of the day.

The sites I’m thinking of never had their IPs completely blocked, the DNS entries for the domains were just removed. If you were to switch to a non-EU or self-hosted DNS server you’d get to the site.

But the domains in question are generally ones the US/EU/NATO propaganda machine has told people are bad, so there’s no outrage when they’re blocked. In many cases there are often cheers.

I linked the specific wiki page section in an edit to the main post. It’s in the troubleshooting part at the end.

I didn’t try the i8k module but looking at a couple things it looks like the issue was more apparent around Linux kernel 4.15 from a few years ago. I also don’t have any specific complaints with temperature control. The fans only ramp up in the 70-80C range which seems to be quite reasonable.

The RAM is fine (Memtest ran 4 times without faults), and cooling seems to work well enough. Storage is ok and I used two different SSDs through this whole process and saw the same problems on both.

I tried the previous known-good kernel options on the Manjaro install and it seems to be OK now. According to the Arch Wiki the Intel 8th Gen mobile CPUs and especially iGPUs are known to be a little problematic on Linux so the kernel options to disable some power saving options are basically non-optional. It’s weird though that it works now and didn’t on the Tumbleweed reinstall.

The EU regularly forces DNS server operators to remove entries or redirect certain domains. It’s super easy to circumvent but most users don’t know that.

Of course I should have done that too. Running one now, I’ll let it go for a few hours and see what happens.

A home is for living in. A person has one body, therefore one home per person/family unit is an appropriate number. Corporations have no bodies, therefore they do not need homes.

Not only is rent robbery, but private property in itself has its origins in theft.

I user a terminal so that that everyone around me thinks I’m “hacking” when I’m just running updates or configuring something.

It’s clearly a move to gain control of what people’s computers will be allowed to run and what information they’ll be allowed to see.

There were already attempts to implement this at the start of the consumer internet days by Microsoft and others, which failed then because many early internet users were paying attention and knew what was being attempted. This time I’m not sure that we’ll be able to stop it without structural changes to society.

As I understand it, it wasn’t arbitrary. Microsoft has wanted to require TPMs for two decades at this point. Once there’s high enough adoption they can roll out their version of trusted computing.

Yeah, I got called an idiot for pointing out that connection here a few weeks ago.

My partner when I do updates from the terminal: hakcer

Even if it’s as simple as choosing which Root CA’s we want to trust, how many people will know to do that and be able to do that? A couple percent at most.

Of course we need full ownership of our devices, and trusted computing has always referred to the trust of for-profit corporations, but this in itself doesn’t help the vast majority of people who either don’t know that they’re compromised, think they have nothing to hide, are unable to do anything about it, or a mix of all three.

Privacy and security are already a privilege. Proposals like eIDAS only make it even more unaccessible.

Watch the opposite happen.

Nah, they’re dropping chat control for something bigger: breaking SSL.

https://last-chance-for-eidas.org/

You can use the container names to address containers. Whether this is a randomly generated name (docker run… with no --name flag), the compose working dir and service name, or the compose container_name var.

I also rarely use the container command. docker is sufficient, or docker compose ... while in the working dir of a given compose stack.

Mint on my desktop, decided to try out Tumbleweed on a cheap laptop. KDE wasn’t for me / wasn’t reliable enough, but I’m happy with Gnome. I haven’t needed to use Flatpacks though.

Might try MicroOS on the servers, I like the idea of an immutable distro so less can go wrong during updates, and I run all services as containers anyway.

As far as I can tell this just fixes some relatively minor issues the contributor was experiencing deploying the hacky self-host stack on his Kubernetes home lab or private server. It doesn’t bring anything new to the table, and I’m not sure that a full on Kubernetes or similar distributed swarm deployment is really what the average self-hoster needs or even wants.

It could just be that Omnivore tries to do too much for it to be feasible to self host. It was also conceptualized with certain third-party backend services in mind which makes it tricky to adapt.

Maybe I’m asking for too much, but I would be looking for a two service stack, one for the app and one database service. The current and forseeable future state of Omnivore is four backend services excluding the database, and like I already pointed out you’re not even getting the full feature set.

Just the simple fact that Tor was started with a bunch of US intelligence money is cause for concern.