

still Morrowind in XR. having fun just wandering around again.
also Vintage Story. chill minecraft flip but more. wandering around public rooms seeing what is up.


still Morrowind in XR. having fun just wandering around again.
also Vintage Story. chill minecraft flip but more. wandering around public rooms seeing what is up.


maybe open technically. but my impression of BlueSky is that it is full of neoliberal status quo apologists. would be happy to be wrong.


Penny’s Big Breakway
creative colorful indie platformer


Lenovo ThinkCentre M715q, Lenovo ThinkCentre M93p
separate cheap newer N100 cpu node for jellyfin, other encoding
Intel NUC NUC8i5BEHS for k3s control plane, little more expensive but reliable.
i usually replace Thinkcentre fans w noctua for power draw, performance, and noise. and remove wifi module, not needed, draws power, closed blob firmware, is a risk. pops out easy, no config changes needed in Debian.


amazing, well done! i run Debian on cheap used Thinkcentre PCs, run as k3s worker nodes just fine.


https://github.com/fosrl/pangolin
use this instead of tailscale or other corporate options. tailscale is going for IPO, their service cannot survive investor greed.


1000xResist with XR glasses. talk about immersive.
just get a cheap n100 box, don’t overspend


it would be amazing if geerlingguy was the one to make youtube go mask off


ansible has a learning curve but will save you a lot of time in long run over bash.
write playbooks rhat target groups of similar hosts instead of a playbook for each distinct host, target specific hosts with -l flag of ansible-playbook.
look into molecule for testing sooner than later. helps you be more confident your plays will work as expected vs running trial and error on a host and getting it into a bad state. i run on bare metal so more important for my workflow not to wipe a folder with a typo, etc.
https://forgejo.org selfhosted has been good for me, FOSS fork of Gitea.
I run a k3s cluster for selfhosted apps and keep all the configuration and docs in a git repo. That way I have history of changes and can rollback if needed. In that repo I have a docs folder with markdown documents about common operations and runbooks.
There are other ways to do this, but I like keeping docs next to the code and config so I can update them all at the same time. Deployed several wikis in the past but always forget to update them when I change things.
Paradise Killer