notifications for static site builds
This morning I set up notifications for changes to my static site builds leveraging git name status and ntfy.
No themes match.
All posts with the tag "ping"
This morning I set up notifications for changes to my static site builds leveraging git name status and ntfy.
The dev server is cooking today, I’ve dropped markata builds from 2m40s (hot cache) in prod to 15s (hot cache) in dev. Currently building 2745 posts and 274 feeds.
Not every print needs supports. So many models default to having it on, whether needed or not. Well designed parts, designed for 3d printing almost never need supports (depending on constraints).
Include steps to reproduce your bug when you file a bug report or issue. You may quickly forget how you got there, and no one can fix a bug that is not reproducible.
All I want for Christmas is filament
I don’t need gifts or fancy things
I just wanna model, tinker, and print,
...
git worktrees are goated, and must be leaned on moving forward.
What flavor of autism did you guys get, I got the kind where I run kubernetes in my basement.
My home row layout. It’s not quite home row mods.
https://dropper.waylonwalker.com/file/fd74f80e-ff5e-4548-8419-bd407144bb6c.excalidraw
GPU’s are awesome. I just added gpu support to my bambu-studio distrobox and its flying! On my wayland based system the native package has never worked, (arch or bazzite), but running in a distrobox does. Outside of distrobox the 3d rendering canvas is black, no output. It used to work fine without gpu support, was snappy enough, complex models were a bit sluggish, but fine. Lately something happened and simple models bring it to its knees. It got unusable!
The print I happen to be working on is some custom designed gumdrops for a theater set. The ui is working and not lagging 30s between clicks causing clicks to happen on the wrong ui element.
Calendar data could not load. Try again.