While updating an old hacky audit-follow script to do more long-term monitoring recently, found that I wanted to add a filtering mini-language/ DSL there, and after trying a couple options with having blacklist/whitelist and such, quickly arrived at using a seemingly unnamed but somewhat popular list type for this …
Since GIMP (aka GNU Image Manupulation Program) is still a complicated raster graphics editor, kinda like Photoshop , it has same problem of having a ton of tools and options which can be easy to forget. And especially for some same-y but rare tasks, like going back to update/export specific …
Bot traffic on the internet was always comparatively high, with search engine scrapers and whatever odd research tools doing their thing, but that changed massively in recent few years with LLM-training-content-scaping bots. Those don't care about robots.txt and are designed to be unblockable, running on regular users' machines, faking …
Tools like rnm and regex-rename , or one-liner shell loop like: for p in *.mkv; do n=${p##*/}; n=<string-manipulations>...; echo mv "$p" "$n"; done ...is how I usually rename stuff, as a typical shell-for-file-management terminal-user. It's non-interactive and not "visual", as in you kinda have to imagine results, then think …
When tinkering with something outside PC/laptop screen, I often need a reminder pad for a wiring schematic or recipe, or even some hotkeys, maps and other quickref-data when playing games on main display, and I'm using e-ink pad for that, combining any kind of text/icons/diagrams/images/etc …
Using standard rm(1) tool in something like a file-backup script, with any "untrusted" list of paths OR an untrusted dir is wildly unsafe, but it's kinda frustrating to me that it doesn't have to be. On modern linux, "rm" can fairly easily have some --restrict-to-dir option, which guarantees that …
When retrying some failed check or operation, common ways to algorithmically wait for next attempt seem to be: Make N retries with a static interval in-between, e.g. "retry every 10s". Works well when it's not a problem to retry too often, or need to know when stuff starts working …
As a long-time conky user, always liked "system status at a glance" visibility it provides, so you're pretty much always aware of what's normal resource usage pattern for various apps and system as a whole, and easily notice anything odd there. (though mostly kept conky config same since last post …
My pattern for using these shell wrappers / terminal multiplexers for many years have been something like this: Run a single terminal window, usually old XTerm , sometimes Terminology . Always run tmux inside that window, with a C-x (ctrl-x) prefix-key. Open a couple local tmux windows (used as "terminal tabs") there. Usually …
Dunno what random weirdo found me this time around, but have noticed 'net connection on home-server getting clogged by 100mbps of incoming traffic yesterday, which seemed to be just junk sent to every open protocol which accepts it from some 5-10K IPs around the globe, with bulk being pipelined requests …