

And so many other things. I’ve also used it for “cloud saves” back/forth from my desktop to my steam deck on games that don’t support them for various reasons. Dyson Sphere Program being one, because the files can get quite large.
Just chilling


And so many other things. I’ve also used it for “cloud saves” back/forth from my desktop to my steam deck on games that don’t support them for various reasons. Dyson Sphere Program being one, because the files can get quite large.


Can’t wait for this company to be public and to be subject to the whims of shareholders chasing profit.
Yuzu TwoZu: Electric Boogaloozoo.


If you’re up for pgp and git, gnu password store is a killer app. There are a few guis, including Android and iOS, and if you use gopass there’s a nice plugin for browsers as well. And it’s ultimately just two tools that are both solid and generally well known.


My 3090 is a light flickering machine. Kind of annoying tbh.


I mean, that’s exactly the same set of problems faced by closed source software. I guess one potential difference is that you can hire new devs to take over if it’s successful enough. But both crappy documentation and team burnout have killed lots and lots of internal projects at places I’ve worked.
Rage against the garage door opener.


Mixing storage and processing is now cool again. It’s just called hyper converged infrastructure.


I really don’t miss trying to find codec packs to install. Good riddance.


If this was not a zero day being actively exploited then you would be 100% correct. As it is currently being exploited and a fix is available, visibility is significantly more important than anything else or else the long tail of upgrades is going to be a lot longer.
Keep in mind a list of federated instances and their version is available at the bottom of every lemmy instance (at /instances), so this is a really easy chain to follow and try to exploit.
The discovery was largely discussed in the lemmy-dev Matrix channel, fixes published on github, and also discussed on a dozen alternate lemmy servers. This is not an issue you can really keep quiet any longer, so ideally now you move along to the shout it from the mountaintop stage.


I’m also running arch. Unfortunately I’ve been running mine long enough that it’s just my own bespoke Ansible playbooks for configs that have morphed only as required by breaking changes or features/security I want to add. I think the best way to start from scratch these days is kubeadm, and I think it should be fairly straightforward on arch or whatever distro you like.
Fundamentally my setup is just kubelet and kubeproxy on every node, the oci runtime (CRIO for me), etcd (set up manually but certs are automated now) and then some k8s manifests templated and dropped into the k8s manifest folder for the control plane on 3 nodes for HA. The more I think about it, the more I remember how complicated it is unless you want a private CA. Which I have and love the convenience and privacy it affords me (no CTL exposing domain names unless I need public certs and they’re public anyway).
I have expanded to 6 nodes (5 of which remain, RIP laptop SSD) and just run arch on all of them because it kinda just works and I like the consistency. I also got quite good at the arch install in the process.


If you’ve got >=3 machines and >=3 devices, I’d suggest at least strongly considering Rook. It should allow for future growth and will let you tolerate the loss of one node at the storage level too, assuming you have replication configured. Which (replication params) you can set per StorageClass in case you want to squeeze every last byte out for cases where you don’t need storage-level replication.
I’ve run my own k8s cluster for years now, and solid storage from rook really made it take off with respect to how many applications I can build and/or run on it.
As for backup, there’s velero. Though I haven’t gotten it to work on bare metal. My ideal would be to just use it to store backups in Backblaze B2 given the ridiculously low cost. Presumably I could get there with restic, since that’s my outside-k8s backup solution, but I still haven’t gotten that set up since it’s much more cloud-provider friendly.
I’m not saying it doesn’t suck for this person, but product market fit is a thing for open source too. If people need it they’ll use it and contribute until something better comes along. If not, your idea wasn’t the one. That doesn’t mean it’s not possible. Nearly my whole life runs on open source software, so it’s pretty clearly sustainable.
Um. Yes. And to be blunt: obviously. And in return, I give away software I create for free whether people need it or not, and try to give back in the form of contributions too. But I’ve never once given up my day job for it. Would that be nice? Maybe. But open source software is more frequently sustained by passionate people using and expanding it for their own projects and not by expecting people to pay you for your efforts when you’re likely not paying (nodejs, github, ahem) for the software you’re building it on anyway.