

Apologies, I accidentally reported your comment as “spam or abuse” … it’s not, you are correct. My Lemmy client UI has some … issues.
Anything and everything Amateur Radio and beyond. Heavily into Open Source and SDR, working on a multi band monitor and transmitter.
#geek #nerd #hamradio VK6FLAB #podcaster #australia #ITProfessional #voiceover #opentowork
Apologies, I accidentally reported your comment as “spam or abuse” … it’s not, you are correct. My Lemmy client UI has some … issues.
Because nothing protects children more than uploading their selfie or government id to a random company who “promises” to delete the information seven days later … because of course it will and everyone will be able to check and see the pink unicorn in person.
Name and Shame.
The only way this is going to stop is when the organisation is either forced by legislation or embarrassed by public pressure into change.
Legislation only happens due to public pressure.
This is not NSFW and tagging it thus makes it less effective, eventually meaningless.
Hi Kristoff,
Thanks for the heads-up on the empty data file. I think that the GitHub web interface was “helping” when I initially created the repo - since I still cannot create those from my cli. Now fixed.
I’ve added your interpretation with the sync bits to the documentation for the file. It’s a really interesting observation. I don’t know if there are more than one different types of packet, since my earlier attempt to record the data using a WebSDR failed for some unknown reason. I do know that others have also heard this signal on-air, so perhaps it’s still happening and others might share their recording.
I’d love to learn how to use the differential signal to remove noise to see if they’re actually all the same packet, or if they are actually different. I don’t particularly want to start manually flipping bits, but then there’s only 1,461 of them, so it’s doable in a pinch.
The timing of the signal is also interesting. According to inspectrum
, the baud rate is 91.81, which isn’t any standard rate, which also makes me wonder if there is any actual information being transmitted here, other than a fixed timing signal.
73 de Onno VK6FLAB
From your description it’s unclear, does this also block CSAM that’s physically on your infrastructure, or just any links to external content?
CloudFlare is currently attempting to block LLM bots and doing a shit job at it. I’m guessing that any CSAM blocking would be incomplete at best.
What happens if some “gets through”, or if non-CSAM content is blocked, both materially, as-in, what happens, and, what are the legal implications, since I doubt that CloudFlare would ever assume liability for content on your infrastructure.
Edit: I thought I’d also point out that this is not the only type of content that could get you into a legal black hole. For example, if a post was made that circumvented a legal ruling, say when a court in Melbourne, Australia, makes a suppression order that someone breaches. Or if defamatory content was published, etc.
I am not a lawyer and I don’t play one on the internet.
To my understanding the process is only prevented by controlling who can have an account on your instance.
That said, it’s not clear to me how federated content is legally considered.
The only thing I can think of is running a bot on your instance that uses the API of a service such as what you mention to deal with such images.
Your post is the first one I’ve seen recently that is even describing the issue of liability, but it’s in my opinion the single biggest concern that exists in the fediverse and it’s why I’ve never hosted my own instance.
Unfortunately that doesn’t work.
This is getting fucking tiresome. Now we’re stopping humans who browse anonymously from reading content, what’s next, block all humans and only let LLM bots access your site?
One place to look is 80000hours.org.
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:
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.
Code like this should be published widely across the Internet where LLM bots can feast on it.