#api Refactored the weekly database dump script since it was getting slower and slower and was very old. Re-running the new one now to test. I'm anticipating 4 hour run instead of 28 hours.

https://desertant.com/blog/introducing-desert-ant-labs/

"Voz: transcribe 10 minutes of audio in two seconds on an iPhone – 4.7x faster than Whisper – with a start and end time on every word."

My Umbrel docker containers did not survive the OS upgrade from Ubuntu 20 to 24 on my podcast rig. This is why I never upgrade anything. I still have some Ubuntu 12 and 18 servers running.

#api I would like to pretend (by silence) that I didn't break feed ingestion this morning for about 20 minutes by forgetting to update the env files on the aggregator servers. But, I'm sure @nprofile1q... will produce some sort of graph showing a dip this morning and asking what's up. So, I'm proactively admitting it.

#podping Gossip peer churn seems better now. Switched from FIFO to last seen.

Google's AI results led me down a few hours of wasted time telling me to run MySQL commands that do not exist in the v8.x branch I explicitly told it I was using. What a train wreck this whole thing is.

#api Currently back-filling the new 'podcasts' table in the database with the proper PI feed ID's. Api might run slow for the new little while.

#podping Gossip watcher, writer and monitor v0.15.0 is available on GH and docker hub. Switches from FIFO to LRU for peer node caching to handle high churn host IDs in the swarm. Also has an ID generation seed if you want to pass it in.

"17% of the most popular Rust packages contain code that virtually nobody knows what it does (I can't imagine about the long tail which receives less attention)."

https://kerkour.com/fixing-rust-supply-chain-security

I did not know "ALTER TABLE <tablename> DATA DIRECTORY = '/path/to/dir'" existed in MySQL. What an amazing solution to my exact problem.

@nprofile1q... I'll add an MCP interface after the db schema change is finished.

@nprofile1q... Do your podping gossipwatcher nodes rotate their keys? I'm seeing 120 suorcd nodes being gossip'd in the swarm right now. I need to put in some facility for aging these out quicker rather than letting them FIFO because quick churn could fill the connection suggestion messages with bad peer ID's.