dihutenosa

https://icecast.org/faq/

In Icecast you usually have a “station” (mountpoint) sourced by a source client like IceS and streamed by Icecast to a large amount of listeners. This implies that all listeners of that mountpoint get the same stream, so an individual listener can’t pause the stream or add different tracks without affecting all other users.

You might want to check out pass - the standard Unix password manager

Surely a custom vibe-coded mess of a web frontend for ImageMagick (it allows uploading a whole lot of scanned images, then presents a comfy web UI which allows choosing particular transformations - posterize to bilevel, trim, straighten, deskew, scale-to-page-size-and-add-edges). It runs in an ancient discarded-and-salvaged laptop.

I also use the same laptop as:

• Livekit SFU (transporting media for Element (Matrix) calls)
• XMPP server (Prosody)
• STUN/TURN server (transporting media for Snikket (XMPP) calls) (coturn)
• email server (Postfix)
• hosting a QR scanner webpage, so I could scan QRs in PCs with minimal fuss (nginx + 1 static file)
• and of course, since it’s already there, home router (it’s in the basement, so too far to do WiFi. The WiFi access point runs in dumb bridge mode)

I also run a periodic HLS video broadcast (my home internet connection should survive something like 40 simultaneous watchers, I should figure out how to distribute it efficiently to other hosts). It’s too heavy for the ancient laptop, but (as it turns out, I measured yesterday), a NAS with a 4-core Intel N100 CPU just barely manages. I might switch to it, it’s probably more power efficient than the current desktop workstation.

Right you are. Still much cheaper than a laptop, let alone a server.

When logged in locally, I use btop to see an overview of what’s happening.

Other than that, I have relevant Prometheus exporters in every machine (node exporter in all machines, specific exporters by the workload), hooked up over Wireguard to my monitoring solution offsite.

The phone I actually carry around has a ntfy client talking to ntfy server on the aforementioned monitoring solution, so I get buzzes when something goes down.

Btw, does anybody happen to know where I could get a pre-cooked comprehensive alert system for my nodes? Surely many people have already written all these rules:

• if disk space > 80% consumed, send a low-priority alert
• if disk space > 95% consumed, send an urgent alert
• … everything else, there’s so much to check…

step 1, figure out which sound system you’re using:

• oss
• alsa
• esd
• pulseaudio
• pipewire

I’m probably forgetting a couple.
… joking. Have you tried poking in the settings of pavuctrl already? There’s a button to set the default.

ntfy, self-hosted offsite on an old phone, it takes around 300mA, ie.less than a watt.
ntfy app on my phone.
Wireguard between them.

I found your Pimaps to be fabulous.

Haters gonna hate, there’s no help for it.

AI is a tool. Slop happens, but it doesn’t necessarily need to happen. I imagine there were many misguided, unnecessary, and just plain wrong trenches dug just after invention of the backhoe.

Go on and do even greater stuff.

It went something like “The old one did, this one does not. Why not? Is it broken? Computers are supposed to update software, y’know.” - everything about this reasoning is correct, except that there’s the wonderful unattended-upgrades thingamajig in Debian derivatives that takes care of it.

People don’t tolerate change.

After Windows 10 stopped getting updates, Auntie Dear finally consented to Linux Mint. Guess what, after installing unattended-upgrades, she complained that the computer stopped pestering for updates.

In the end, I explained that being Linux, it’s perfect and thus doesn’t need fixes.

Absolutely amazing!