@MW1CFN would be interesting to measure the background noise at each location, too.

@czarbucks @amyedge @ai6yr @lckrohjr @AE4WX @Jennifer @BakerRL75 @firefly @W6KME how are you using ax.25 ?

@MW1CFN very nice! Sounds like an efficient setup for reaching all skip angles in all directions.

WSPR and Red Bull for breakfast in Eastern WA.

Collected various bits of 80s surplus over a couple of years and now I can “see” signals from DC to sub-millimeter (300 GHz+), in theory at least. This is a 25 GHz signal.

@masek 👀

@croyle RIP MFJ :-(

"Looks like there aren't many options for WJ-340 VLF receiver. Consider this used farm tractor or a pair of flannel pajamas."

DIY window feed through for running RF cables from inside to outside. You can buy these but I had the parts.

@david_chisnall @whitequark hence the rise of permission structures

Good read about cancellations in Async Rust https://sunshowers.io/posts/cancelling-async-rust/

This blogpost covers a lot of the problems in this space very well. I like how it emphasizes definitions and semantics, shows examples of bugs they came across to, and list some practical recommendations.

The "double-edge sword" of cancellation in Rust is spot on: on one hand, it's cool how "easy" and simple it is to cancel future in Rust -- you *drop* it. Especially given how non-trivial it can be in synchronous environments.

However, this also means it's far too easy to *silently* drop a future. This is scary on its own, and combined with the fact that cancellation of parent futures propagates down to child futures (because of the single ownership model) makes it much more concerning.

This post also links another (much older, Feb 2024) blogpost that covers this space well, elaborating on async clean-up problems and mentions linear types as a solution https://without.boats/blog/asynchronous-clean-up/

Last week #AllSystemsGo #ASG 2025 happened in Berlin, and it was a blast as usual, thanks to all the amazing speakers!

Talks are already available on YT: https://www.youtube.com/playlist?list=PLWYdJViL9EiqX25Rmu49FTDDnzT30wvqL

At the beginning of this month we wrapped up OSHWA’s first ever Open Healthware Conference. For two days we got to hear from incredible creators within the Open Healthware community, see demos of devices meant to better the medical world, and meet new folks from the community.

It was incredible! We can’t say thank you enough but we can try! From NSF, to speakers, to in person and online attendees - thank you, thank you, thank you!!

https://oshwa.org/announcements/open-healthware-conference-wrap-up/

@oshpark @kicad Now verified to work with the HMC doubler as expected. Thanks for making this possible! I plugged the laminate specs from your site into a couple of calculators and they were in close agreement, as are the test results. 4-layer is the next step. I'll publish the design & will be presenting the overall project at Microwave Update (MUD) in a couple of weeks.

@kicad @oshpark and the drop-off around 18 GHz could also be significantly due to the connectors, which are rated to 18 GHz. To get better results, I'd need to go to 4-layer FR4 (where the top layer is very thin), or microwave laminates (expensive).

@kicad @oshpark amazingly, the 0.8mm FR4 material works very far out of its expected range, and is useful up to ~16 GHz with acceptable loss & SWR for my hacking purposes.

@n8dmt it should work really well, the input range is 4.5 to 8 GHz officially, but it likely does more. This is indeed to extend my Kuhne 13.4 GHz synth up to about 18 GHz.

All Systems Go! is almost here! Next Tuesday, Sept 30th, will kick off 2 days of talks and mingling around foundational user-space Linux technologies.
📆 Schedule is here ➡️ https://cfp.all-systems-go.io/all-systems-go-2025/schedule/
🎟️ Tickets are still available ➡️ https://ti.to/all-systems-go/all-systems-go-2025

@amarsaar their site seems broken: "Error code: SSL_ERROR_RX_RECORD_TOO_LONG"

Anyone going to be at SOSP in a couple of weeks? I will be giving a keynote at the KISV workshop on Monday morning about how CHERI changes how you think about OS design, and then we'll be presenting our paper on the CHERIoT RTOS first thing on Tuesday morning (and at the poster session).

#SOSP #KISV #CHERI #CHERIoT