This probably isn't the point either, but I get an almost perverse level of calm knowing that for my most favourite albums, I own a physical representation of the waveform trapped in a medium.
I very rarely listen to them in that form, but I honestly like the idea that in a post-Carrington event, zombie apocalypse or mad-max style future where electricity or electronics become scarce, I can (if desperate enough) listen to them with a nail and a cone.
I've been using Win+R to paste it in the windows run box.
Amazingly still works on Win 11 and still seems to keep it local (bypassing the windows search), so I'm pleased to report consistent results for 30 ish years.
Of course, now I've mentioned it out loud, it'll be the next thing to go...
I don't know if it's just me being old and grumpy, but everything windows 8 and later (server 2003) seems like half-baked, unfinished enshittification. Trying to do something even vaguely "advanced" to a network adapter puts me back in windows 95 land along with the run box. The "manage" pane with device & disk manager and logs is from a totally bygone era yet it seems to still be the only way of getting that information. The worst bit is, I'm not complaining. All the bits that look and feel like they've been forgotten since Windows 2000 are the easiest, least infuriating bits of the system I interact with.
I don't suppose you could point to any resources on where I could get started. I have a M2 with 64gb of unified memory and it'd be nice to make it work rather than burning Github credits.
You can then get Claude to create the MCP server to talk to either. Then a CLAUDE.md that tells it to read the models you have downloaded, determine their use and when to offload. Claude will make all that for you as well.
Mainly gpt-oss-20b as the thinking mode is really good. I occasionally use granite4 as it is a very fast model. But any 4GB model should easily be used.
It works exceptionally well for Slack as we've seen over the years. Someone in your $group uses signs up for the free tier, gets people using it and then you've got to pay through the nose to access any history.
At least slack is clear upfront that this is going to happen, mattermost just did a rug pull and removed history from users who previously had access to it.
> Syncing networked clients to play audio at exactly the same time is a solved problem.
I was going to point out that with the variance in FM demodulation chips, using a pile of FM receivers probably wouldn't get you perfectly synced audio these days at all, even more so if it's going through usb/software/audio stacks.
Then I re-read the Ops comment and this actually seems to be a network of _transmitters_. I'm not sure what problem they're trying to solve, but I can't believe multiple PiFMs is ever the answer.
Commercial DAB radio does use single frequency networks (with tight timings and clever calculated offsets), and I am somewhat curious how analogue FM responds with regard to offset destructive interference, but this isn't that.
Please don't do this. For context, a car FM transmitter is limited to 250nW (in many jurisdictions). A Pi GPIO pin with the right bit of wire is potentially capable of 10mW or more. 40,000 times more powerful and a lot more noisy. One could be causing problems for people surprisingly far away.
Having been brought up on pictures of Stonehenge, I felt a little twang of confused letdown the first time I visited Thornborough. This passes quickly though, and if you're vaguely near North Yorkshire it's well worth a visit. I've had the pleasure of camping at the base of it a few times with fire and mead which makes it all the more fun.
It's a good question, and I wondered the same. I don't know, but I'd postulate:
As it stands at the minute, the clocks are a mere 5 microseconds out and will slowly get better over time. This isn't even in the error measurement range and so they know it's not going to have a major effect on anything.
When the event started and they lost power and access to the site, they also lost their management access to the clocks as well. At this point they don't know how wrong the clocks are, or how more wrong they're going to get.
If someone restores power to the campus, the clocks are going to be online (all the switches and routers connecting them to the internet suddenly boot up), before they've had a chance to get admin control back. If something happened when they were offline and the clocks drifted significantly, then when they came online half the world might decide to believe them and suddenly step change to follow them. This could cause absolute havoc.
Potentially safer to scram something than have it come back online in an unknown state, especially if (lots of) other things are are going to react to it.
In the last NIST post, someone linked to The Time Rift of 2100: How We lost the Future --- and Gained the Past. It's a short story that highlights some of the dangers of fractured time in a world that uses high precision timing to let things talk to each other: https://tech.slashdot.org/comments.pl?sid=7132077&cid=493082...
> The boss doesn't see that you can't properly paste a piece of code in the chat
Of all my many gripes with Teams, it usually handles code surprisingly well. Single `inline` and triple backtick blocks usually render as you'd expect.
OneNote on the other hand doesn't support a code-block at all, and is worse (if you can believe it) than storing cli commands in Word docs.
When I paste code into the native MacOS Teams chat, my peers using Window Teams see a literal black box. I wish it worked! I really do. Or we all had MacBooks or Linux desktops.
I very rarely listen to them in that form, but I honestly like the idea that in a post-Carrington event, zombie apocalypse or mad-max style future where electricity or electronics become scarce, I can (if desperate enough) listen to them with a nail and a cone.
reply