You know, in hindsight, you’d have to be an idiot to turn down being Trump’s lawyer. Absolutely tons of money, and you’ll have no moral worries when you decide to intentionally throw the case.

I would find this all extremely concerning if China didn’t regulate US platforms so heavily. For example, Tiktok has safety limitations for children in China while they have nothing at all for children in the US. It’s being used as a social/mental health weapon.

Just remember that daddy allows you access to the propaganda that encourages defending Tiktok.

Finally, your speech has not been limited. You can take it to any of the competitors. There would be free speech concerns for Tiktok, but it’s a Chinese company, not protected by the US constitution, and checks notes China proactively limits speech.

RAM could be a cheaper culprit. Try re-seating it.

Do not use Manjaro. It is a known trap. What you can do is install pamac, which is what Manjaro uses for GUI package management. It’s been a hot minute since I’ve used Arch, so here’s a tutorial:

https://itsfoss.com/install-pamac-arch-linux/

Alternatively you could look at Garuda, which is a solid Arch distro. You’ll either love or hate the theme, but that’s easy to change. It also comes with an interactive kernel by default (most distros use a regular kernel build, which works better for servers).

Whatever you do, please please please not Ubuntu. It’s the lowest common denominator. Emphasis on “lowest”. It was good in the past, but Canonical have really lost the plot.

Missed opportunity to call it Muhummanoid

Inadvertent oracle attack.

At some point when people ask about the Holocaust, we’re going to have to start asking “which one?”

For your use case, consider it to be a packaging format (like AppImage, Flatpak, Deb, RPM, etc.) that includes all the dependencies (including services, not just libraries) for the app in question.

Should I change this?

If it’s not broken don’t fix it.

Use Podman (my preferred - the SystemD approach is awesome), containerd, or Incus. Docker is a graveyard of half-finished pet projects that have no reason for existing. Podman has a Docker-compatible socket, so 100% of Docker tooling will work with it.

I have read on more than one occasion that Wine is becoming the “Linux Gaming ABI.” It’s no longer just about Windows. With the huge variety presented by distros, Wine is simply a nice stable target that never moves.

Try forcing it to use Proton (game properties in Steam).

It does. I have it enabled and tested. “Client Device Isolation.” It’s enabled per SSID.

Ooh I like the idea of “no Internet.” I do trust all of those devices (open source), but they could still be pwned.

All this, and while you’re at it, Donate!

Their voter base is “phasing out:” https://www.statista.com/statistics/319068/party-identification-in-the-united-states-by-generation/ (you’d think that they would value universal healthcare more)

I’m not sure. I’m worried that we’re already in the feedback loop.

MacOS is a BSD, so go with Linux if you want variety.

The rules are different for a second term primary. 85%+ is typical from what I’ve read. Especially when your voter base is bigoted and your opponent is female.

I heard it in a podcast, but here’s a written source on that: https://fedoramagazine.org/pipewire-1-0-an-interview-with-pipewire-creator-wim-taymans/

The message is still to use the PulseAudio and JACK APIs. They are proven and they work and they are fully supported.

I know some projects now use the pw-stream API directly. There are some advantages for using this API such as being lower latency than the PulseAudio API and having more features than the JACK API. The problem is that I came to realize that the stream API (and filter API) are not the ultimate APIs. I want to move to a combination of the stream and filter API for the future.

Switching over to the discrete GPU work in the efi/bios might help. Optimus (the driver that chooses between discrete and integrated) is known to be a steaming pile.

PipeWire wins in the feature-set game, which is why it is being preferred over PulseAudio.

According to the inventor of PipeWire, this is the wrong perspective to take. PipeWire is preferred over PulseAudio as a server, clients (apps) should continue to use the PulseAudio/JACK APIs because the PipeWire API is not designed for general use (it’s designed for things like pipewire-pulse and pipewire-jack).