This has absolutely nothing to do with burner phones and the proposed changes won't do anything to change that.

~5 years ago there was a big push (in the USA) to try and solve it with STIR/SHAKEN but I've not been involved or paid attention since then, so don't know if anything came of it. It's a legitimately hard problem to solve though. Lots of engineering and backwards compatibility technical problems, but also political, logistical and commercial issues are abound. You've also got some turtle issues too; it's attestation all the way down.

ZFS also lets you specify number of copies on a single disk. This sounds a bit weird, but as drives suffer block failures far more often than total failures, it's actually surprisingly useful in some situations.

[1] My suspicion is significantly, as storage sizes are now multiple orders of magnitude larger and errors per MB can't have scaled up linearly to match.

For anyone not in the know, Resolve has an exceptionally capable and feature rich free version. A lot of the AI features (and >4k editing) are locked to the Studio licence which is a one-time payment, but works simultaneously on two computers (including different OS's) and allows upgrades across major versions.

I spent less than $300 on it a decade ago and my licence works fine on new v21 released this week. My least-regretted software purchase in 3 decades.

"Can you paint them gold? And how about custom packaging and drop-shipping as well?"

https://archive.org/details/OTRR_X_Minus_One_Singles

I don't remember which updates triggered it, but that was September 2015.

https://www.bbc.co.uk/news/articles/c0mgjklmzwvo

The calculator gives numbers for nearly everything, but I can't obviously see how much space it needs for model storage or how many writes of temp files I should expect if I'm running flat out.

If you're testing hardware or vm's that don't support it or don't have root, you can stick your linux box transparently in the middle by bridging two interfaces, and apply your traffic mangling there. Testing wifi? Use a decent WiFi AP connected to one of these bridges and mangle your traffic once it hits the wire/after it stops being RF.

At a previous job I had a linux box set up with multiple bridges (each set with a different "testing profile" on different vlans) and trunked to a physical switch. Made it very easy for people in the office to attach physical devices through known bad network links by either using pairs of physical switchports or just dumping VMs/SSIDs into the right VLAN so they could test different things (simultaneously) without needing to reconfigure the actual mangling.

Worth noting that tc applies to egress traffic, so if you want a uniformly bad line it needs applying to both sides - but it does mean you can simulate unidirectional link problems too.

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.

Last time I asked, user hackmiester pointed me to https://goughlui.com/2016/05/03/project-the-definitive-colle...

The "Texas Instruments DSP based Modems" linking to USR-Sportster-bong-bong.wav is pretty close to what I remember.

edit: hackernudes reply is perfect. The youtube auto generated subtitles are pleasing too.

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 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.