This is an early prototype, a fully developed product for both sides is being worked on.

Coming soon to a shelter near you!

Definitely! Actually their stability can be much better than a cat’s (cats tend to shuffle around whenever they like)

Desktop environment AND desktop app toolkit/library, like GNOME + GTK or KDE + Qt, not just a desktop environment.

https://github.com/pop-os/libcosmic

Waiting for the day the question becomes:

Qt or Cosmic?

☺️

https://feddit.nl/comment/19388358

Sell the expensive minisforum pc, buy 3 used laptops, use https://github.com/onedr0p/cluster-template

Done! Full GitOps bare metal Talos kubernetes cluster that runs your workloads so much faster than any VM. Without hypervisor or Ansible or systemd or ssh. Just YAML manifests all the way down. Cert-manager for automatic certificate management. SOPS for local secrets management.

A few months later, you can have this:

Volsync for automated encrypted backups that automatically populate your volumes when you completely reset the entire cluster.

Rook-ceph for shared replicated storage among the nodes.

Authelia/lldap stack + Anubis botblocker to protect public-facing endpoints.

I guess I should start a blog.

Maybe Signal drains battery when it can’t use Google Play Services for notifications and falls back to keeping a connection alive to Signal servers instead?

Tell your buddy you can play Helldivers with him!

Helldivers 1 and 2 are platinum and gold rated on ProtonDB with recent reports on both confirming they work well.

https://www.protondb.com/search?q=Helldivers

Random uneducated guess: Could it be some cache/shaders stuff? Depending on the game, it could take a while until the cache is warm and everything runs smoothly.

Good question!

In the Home Operations Discord there’s some very smart people who solved this problem inside kubernetes by checking if their NAS is online (through a Prometheus exporter named node exporter) and then scaling down their workloads that use it, automatically, using KEDA (an autoscaler for kubernetes)

Depending on how your processes are orchestrated, you might be able to do something similar?

Source: https://github.com/onedr0p/home-ops/pull/9334/files

/etc/systemd/system/mnt-nfs.mount

[Unit]
Description=Mount NFS Share

[Mount]
What=server:exported_path
Where=/mnt/nfs_share
Type=nfs
Options=_netdev,auto,rw

[Install]
WantedBy=multi-user.target

You’re both right: one doesn’t exclude the other.

• Yes we need to be more careful about privacy and who we trust with our data
• Yes we need to protest and take a stand against fascism

Had to DDG that, I could only think of (tofu plan)[https://opentofu.org/docs/cli/commands/plan/]

No idea why you’re being downvoted, it looks like an interesting concept:

https://garbagecollected.org/2017/10/24/the-carmack-plan/

I don’t agree with /u/red-crayon-scribbles ’ approach to memory safety, but what you’re saying isn’t entirely true either.

It is possible to manipulate memory in ways that do not conform to Rust’s lifecycle/ownership model. In theory, this can even be done correctly.

The problem is that in practice, this leads to the following, many of which were committed by some of the most highly skilled C developers alive, including major kernel contributors:

https://xeiaso.net/blog/series/no-way-to-prevent-this/

Thanks, this was indeed the issue!

Thanks, with the help of some kind volunteers on the bastardkb discord I figured out that I have the old v1 elitec version and I managed to flash it with an old version of the bastardkb firmware.

I should probably have used upstream QMK. Might try that next.

I got the layers working, as well as the combo, but callum’s oneshot modifiers aren’t working yet. Although the bastardkb version of QMK seems lower quality than upstream, it is highly likely that I messed up my own code there.

https://github.com/fhoekstra/bastardkb-qmk/tree/main/keyboards/bastardkb/tbkmini/keymaps/fhoekstra

Thanks, I tried flashing it anyways but it seems something in this bastardkb fork / userspace setup I followed is still defaulting to rp2040 it seems. When I flash it says:

Flashing for bootloader: rp2040
Waiting for drive to deploy...

Which never happens of course. I am now asking on the bastardkb Discord since this seems to be something bastardkb specific

For those who don’t get it: https://xkcd.com/378/

QMK FAQ mentions a kernel compile argument, surely I don’t need to compile my own kernel, right?

Literally yesterday I had this idea and looked in the settings if this is possible. Announced the next day.

Nice!