Thank you, that link was very helpful.

Very interesting! I’ve installed it and attempted to look at the mystery signal, but I cannot make inspectrum show anything other than red. I think it’s sampled at 225144, but that’s speculation based on the filename. Any thoughts?

Source file: https://github.com/vk6flab/signals/tree/main/recorded

Edit: Update, once I played with the file format, testing c8, c16 and c32, I finally got something worth looking at. It appears to be c16 and there look to be 4 bits per symbol.

Edit 2: If I use URH, 2500 samples per symbol, I can decode bits as FSK and get the following string:

7cdc5d32a92284d1f5a53f01b512f2c4663860ec2b273abfdb3c6b90f77a0816f9b8ba65524509a3eb4a7e036a25e588cc70c1d8564e757fb6746b90f77a002df37174caa48a1347d694fc06d44bcb1198e183b0ac9ceaff6cf1ae43dde8205be6e2e9954914268fad29f80da897962331c307615939d5fed9e35c87bbd040b7cdc5d32a92284d1f5a53f01b512f2c4663860ec2b273abfdb3c6b90f77a0816f9b8ba65524509a3eb4a7e036a25e588cc7

Edit 3: Outputting only bits I get the following that seems to repeat (with some decoding errors) every 255 bits:

011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111000011000001110110000101011001001110011101010111111110110110011110001101011100100001111011101111010000010000001011
011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111000011000001110110000101011001001110011101010111111110110110011101000110101110010000111101110111101000000000001011
011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111000011000001110110000101011001001110011101010111111110110110011110001101011100100001111011101111010000010000001011
011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111000011000001110110000101011001001110011101010111111110110110011110001101011100100001111011101111010000010000001011
011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111000011000001110110000101011001001110011101010111111110110110011110001101011100100001111011101111010000010000001011
011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111

I don’t keep a browser history at all, but my most recent visit was to:

• Vehicle registration plates of Western Australia

Or my favourite passive aggressive attempt by Admiral’s anti-ad-blocking “technology”:

“Continue without supporting”

My only experience with this is that if the engine is over 50cc it’s no longer a moped and requires a motorcycle licence.

Have you considered an electric bike or scooter?

As for winter, I’ve cycled for a decade through Dutch winters and the only investment I required was a proper raincoat and pants to keep dry. More often than not I didn’t need any winter coat underneath it if I was wearing a jumper, but that was me as a teenager cycling. Not sure if that applies on an motorised bike.

It is an easy upgrade.

Boot from a Linux installer and the upgrade is seamless. I upgraded from Windows NT to Debian 25 years ago. Best decision ever.

This article doesn’t at all explain what actually happens. There’s a hand wavey description including PowerShell scripts and the clipboard, but it doesn’t indicate how the code gets executed.

The article talks about a complex and sophisticated attack, but I don’t see any evidence of that assertion.

Also, given that it’s talking about PowerShell, I’m going to guess that this affects Windows only.

Finally, there’s no source links, no CVE allocation, no indication what the URL looks like.

I’m going with deep scepticism about this report unless more information comes to hand.

Can’t wait to see the Australian government completely ignore this rather than apply it to the fossil fuel lobby that’s currently running the show.

Ashland VA has a recurring problem where non-Tesla drivers turn onto the tracks, there’s dozens of cases.

Virtual Railfan YouTube channel will give you most of them.

Makes you wonder if Tesla used YouTube as a training tool.

There’s an Australian Canadian co-production that goes into some of the atrocities the British got into:

https://en.m.wikipedia.org/wiki/Stuff_the_British_Stole

I would be extremely careful, since it failed for a reason and you were very lucky not to set the house on fire, which looks like it came pretty close to.

The lack of transparency within the various bodies within our community is disturbing. It’s not that the information is there, waiting to be found, instead it seems clear to me that it’s been withheld for reasons nobody has ever even attempted to articulate let alone justify, and frankly I think it’s harmful to the well-being of the entire pursuit of amateur radio.

There’s a whole range of cli tools to extract and query structured data like that, but you might consider loading it into something like sqlite3 and treating it as a database because those formats are really not intended for queries, they’re designed for sharing data.

For some workloads it’s true that you can do the heavy lifting on a more powerful remote machine and transport the results back to an endpoint device like a phone. Websites are a good relatable example of that, as are services like YouTube.

It’s not universally applicable for many activities that computers are involved with, data analysis, record keeping, simulations and a myriad of other processes.

Blurring of the lines between these different orders of magnitude is made possible by faster and faster networks, but that’s physically not able to beat processing done inside a single device.

The more powerful we make computers, the more complex problems we use them for. I suspect that this is unlikely to change as computers evolve.

One of the fundamental differences between phones, laptops, desktops, and beyond is size. While that sounds obvious, it also means that the amount of processing within the device is constrained by that size.

The constraints relate to how much energy can be used by each device and more importantly, how much cooling is available for the system.

It means that there’s a physical limit on how much work each device can do without being unusable.

While miniaturization is a factor, it’s not linear and you can only get so small before you fail.

So, depending on what you want to do in any given time, the device you use will dictate what’s physically possible.

This is a lesson that the religious fundamentalists currently running the USA have weaponised.

A search engine?

QSL … thank you.

Just to make sure, you’re not an ARRL member?

Are you an active LoTW user?

Very interesting! I just recorded a sample using your WebSDR, much appreciated.

Edit: Hmm … that’s odd. I just managed to check the file, two days later, and it’s essentially empty. It doesn’t appear to have saved the .mp3 file at all.