Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Today's #FreeSoftwareAdvent entry is my podcatcher, castget(1).

Uncategorized
1 1 0
  • Today's entry is my podcatcher, castget(1). I've used several CLI podcatchers over the years, changing mostly because hpodder (my then-favorite) became deprecated and dropped out of repos, so I had to find a replacement.

    Configuration is a simple INI-style file, it allows me to post-process files (certain ones I cut off the 7-minutes of advertising at the beginning, customize ID3/ID3v2 tags), and give them a naming-convention that works for how I listen.

    It runs nightly from cron(8) downloading to my queue directory-tree, emailing me the resulting output, and saves its state in files that can be fairly easily tracked in version-control (annoyingly it doesn't sort them, so every run mangles them, but a little processing with vim makes quick work of them, meaning the resulting diff output is just the new podcasts and a top-level timestamp change, not a complete remunging of the file). About every 3–4GB of queued-up files, I've usually reached the ones on my player/phone, delete those, and replace them with the fresh queue. It does mean that news podcasts are largely worthless because there could be a 3–4wk lag between when the episode releases and I eventually catch it in my player.

    It's simple, it works, and it plays well with the rest of my ecosystem. I like it.

  • stefano@mastodon.bsd.cafeundefined stefano@mastodon.bsd.cafe shared this topic

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    2 Views
    Today in #FreeSoftwareAdvent, it's pf(4)Having lived through several iterations of firewall management tools on Linux (and FreeBSD offers both IPFW, IPFilter, and pf in the base system), I've come appreciate the simplicity and declarative nature of pf.conf for my firewall management.The only downside is the quirky syntax of pfctl(8) but I do like being able to run my rules through it to sanity-check them from vi/ed with:w !pfctl -nvf -before installing them.
  • 0 Votes
    1 Posts
    2 Views
    Today in #FreeSoftwareAdvent I'm thankful for the BSD projects, particularly FreeBSD & OpenBSD. Nothing against NetBSD or DragonflyBSD, I just haven't found a regular use-case for them in my day-to-day.I recently wrote up¹ why/how I ended up on a mix of FreeBSD & OpenBSD after a long tenure with Debian since it drifted from the Unixy principles² I loved and grew up with.⸻¹ https://blog.thechases.com/posts/why-bsds/² https://en.wikipedia.org/wiki/Unix_philosophy
  • 0 Votes
    1 Posts
    3 Views
    Today's follow-up #FreeSoftwareAdvent entry is vi/vim.Which I use depends on the situation. Classic vi/nvi tends to be lighter weight and start faster, while vim offers extra features that I find particularly useful). I usually just type `vi` which gets me `vi` on OpenBSD, `nvi` on FreeBSD, and `vim` (or `vim-tiny`) on most flavors of Linux. If I specifically want vim features, I'll invoke it as such directly.I could go on for ages about favorite features, but a select few:• the ability to keep my hands on the home row and not use a mouse is helpful for preventing RSI symptoms• it's a language¹ of editing, involving counts, verbs/commands, and objects/motions, so I can express my editing *intent* and then use the period command to re-issue that same editing *intent*• the :global or :substitute commands can make massive-yet-precise edits across huge files• the :*do commands extend that power across multiple files, allowing me to precisely edit millions of lines across thousands of files with targeted precision• it's ubiquitous—even as some Linux distros have started removing ed(1) from the base installs , relegating it to packages, I can always type `vi` on any Unix-like/POSIX system and be editing with a powerful editor. And with builds for Windows and my phone, I can use it everywhere. No need to install anything• they work just fine over a SSH connection without a GUI, and use minimal resources so they work even on that old hardware from the 90s.⸻¹ https://gist.github.com/nifl/1178878
  • 0 Votes
    1 Posts
    5 Views
    Today's #FreeSoftwareAdvent entry: ledger(1) & hledger(1)I primarily use ledger use for my #plaintextaccounting purposes¹ but try to mostly keep my data-files in a form that hledger can process them too.Getting started involved a crash-course in accounting terms, but the use of positive/negative numbers (rather than "debits" and "credits" which always bugged me; though both have ways of specifying that output should be in credit/debit format) eased the transition.While it started a little tedious, a few helper-scripts and shell-functions simplified adding new common entries and gave me lazy access to common reports.I still struggle a little bit with closing the books (I though I'd figured it out, and documented it², but had some hiccups so I'll need to revisit my documentation in January)But it's been incredibly helpful to see and track our household net worth, spot trends, keep tabs on gift-card balances that would otherwise get forgotten, track invoices sent to clients, and it simplifies balancing the checkbook monthly.⸻¹ http://plaintextaccounting.org/² https://blog.thechases.com/posts/closing-out-the-books-in-ledger/