IcedRaktajino

Got divorced at age 42, started doing community theater, and moved to Hollywood at age 53 to become an actress. She had 121 acting credits by the time of her death in 2012.

Just shows it's never too late to follow your dreams.

Follow up to this post: https://startrek.website/post/37629244

I put together the RTL-SDR + Meshtastic EAS-SANE Alerter system a few weeks ago and have had it running on my bench. So far, I'd only gotten the weekly test alerts to my private channel, but yesterday it was absolutely blowing up (see post screenshot - those are real alerts from yesterday). I've redacted the identifying bits, but the locations that are blacked out are relevant to the reception area.

The real emergency alerts currently go to my private channel along with the test ones, but I was thinking about changing that to send the real alerts to the default public channel. There's not a lot of mesh activity in my area, so I can't really poll the crowd for opinions on that, so I figure I'd ask here to get some general feedback/consensus. One thing I noticed yesterday was that the tornado warning came through this about 45 seconds before all 3 cell phones in my house started blaring with the same alert.

Bonus -- Here's the PiZero running the show. Forgive the messy workbench (I tried to crop most of the chaos out of view).

It's got the USB hub hat with two RTL-SDRs connected (one for NOAA reception and the other tuned to a local variety station). The signal from NOAA is decoded and tee'd to the Meshtastic EAS alerter as well as to nc which is then picked up from my Snapcast server to distribute on the network to anyone who wants to listen to it. The second SDR, currently tuned to the variety station, is simply piped to the Snapcast server. I may do something else with that later, who knows? Both are fed through a splitter from an amplified FM/VHF/UHF antenna.

Screenshot/lyrics from an old CollegeHumor parody of Ke$ha's "Tik Tok" called "Sing Talk" that lambasts the autotune trend back in 2010.

I've been noticing lately that emails from coworkers are all starting to sound like they were written by the same "person", and this old parody song popped into my head.

Nothing fancy. Just a basic 25 ft tape measure because my 10 year old Harbor Freight one finally broke.

No touch screens, no telemetry, no cellular modems, no wifi, no apps, no subscriptions, no infotainment.

Knock knock.

Who's there?

I eat mop.

I eat mop who?

Eww, that's gross.

Github: https://github.com/oozebot/preFlight

Interested in taking some wild new 3D printing features for a test drive? preFlight is free and open source slicer that brings a host of processing improvements as well as fascinating new features and interesting twists on old ones. There are almost too many to list, so here are a few that caught our eye. Cross-sectional view of Interlocking Perimeters, which increases Z-strength. Unlike brick layers, layer height stays constant.

Want to mix and match different support types on the same object? No problem. How about use Nip & Tuck seams to better hide where layers start and stop? You can emboss images directly onto print surfaces with a real-time preview and use smart bridging for counter-bored holes. We particularly like the ability to preview a sliced object from the side instead of just by layer. That’s not all, either.

Those features alone are pretty intriguing, but there’s one in particular that is particularly relevant to creating stronger parts. Interlocking Perimeters increases layer bonding to increase object strength. Unlike brick layers, which staggers layers vertically, interlocking perimeters plays with spacing and compression to increase bonding in the Z axis while keeping layer heights constant. This is possible thanks in part to the greater control offered by Athena, the new perimeter generator.

There are plenty more features — like a full Python runtime embedded directly into the slicing pipeline, and a host of export pathways — so check out the GitHub repository for added detail and let us know in the comments if you give it a try.

Laugh track if you're unfamiliar with the term.

Beyond ridiculous.

A new Linux zero-day exploit, named Dirty Frag, allows local attackers to gain root privileges on most major Linux distributions with a single command.

Security researcher Hyunwoo Kim, who disclosed it earlier today and published a proof-of-concept (PoC) exploit, says this local privilege escalation was introduced roughly nine years ago in the Linux kernel's algif_aead cryptographic algorithm interface.

Dirty Frag works by chaining two separate kernel flaws, the xfrm-ESP Page-Cache Write vulnerability and the RxRPC Page-Cache Write vulnerability, to modify protected system files in memory without authorization and achieve privilege escalation.

Also, while Dirty Frag belongs to the same class as the Dirty Pipe and Copy Fail Linux vulnerabilities, it exploits the fragment field of a different kernel data structure.

"As with the previous Copy Fail vulnerability, Dirty Frag likewise allows immediate root privilege escalation on all major distributions, and it chains two separate vulnerabilities," Kim said.

"Dirty Frag is a case that extends the bug class to which Dirty Pipe and Copy Fail belong. Because it is a deterministic logic bug that does not depend on a timing window, no race condition is required, the kernel does not panic when the exploit fails, and the success rate is very high."

This kernel privilege escalation affects a wide range of Linux distros, including Ubuntu, Red Hat Enterprise Linux, CentOS Stream, AlmaLinux, openSUSE Tumbleweed, and Fedora, which have not yet received patches.

​Kim released complete Dirty Frag documentation and a PoC exploit with distribution maintainers' agreement after an embargo on full public disclosure was broken on May 7, 2026, when an unrelated third party independently published the exploit.

"Because the embargo has currently been broken, no patch or CVE exists. After consultation with the maintainers on linux-distros@vs.openwall.org and at their request, this Dirty Frag document is being published," Kim said.

To secure systems against attacks, Linux users can use the following command to remove the vulnerable esp4, esp6, and rxrpc kernel modules (however, it's important to note that this will break IPsec VPNs and AFS distributed network file systems):

sh -c "printf 'install esp4 /bin/false\ninstall esp6 /bin/false\ninstall rxrpc /bin/false\n' > /etc/modprobe.d/dirtyfrag.conf; rmmod esp4 esp6 rxrpc 2>/dev/null; true"