My wife's brother became a policeman and turned from being a regular person into a judgemental prick with a bad attitude about hispanics.

Police get conditioned into being bad police by all the other bad police.

From TFS: "Some companies in Denmark have access to the CPR for verifying people's information with the government"

So the people's data was being used as an authentication token.

That is as bad a design as you could possibly come up with.

It's not incompatible. It's locked out by the vendor's use of anti consumer cryptography.

II had not heared of that program. erroneously thought that a program so named would have something to do with radios.

I've released some radio related things on github.

Necfull: Because NEC the antenna element solver from the Us governement costs money. This is better and free.
YagiYagi: A much quicker antenna design program with pre-baked antenna models for common antenna types.
Morsey: To learn Morse code with several different learning models (because I learned some things from my wife with the education PhD).
Hamchannel: An OFDM+LDPC packet data link over FM radio program with support for file transfer and live chat. Meets US amature licensed band rules.
remez: An FIR and IIR digital filter design tool that generates C, System Verilog and VHDL implementation code.

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fgithub.com%2Fdj-on-githu...

>Or gets rewritten in an LLM?

It'll get rewritten in rust by an LLM. Then no one will be able to understand the code.

America does not have a "War Department". It has a Department of Defense, or Defense Department. Renaming it requires an act of Congress, which has not happened. The AP journalistic guidelines also indicate that the Department of Defense name be used unless quoting a source. If you use Department of War, you are to include the fact that this is an unofficial name and that an act of Congress is needed to change it.

Not really sure though that a Texas Air National Guard unit needs to be flying all the way to Michigan for this sort of training. If they felt the need for such a spectacle, I'm sure there were units a lot closer than Texas.

To clarify, the users were OpenAI themselves, so there is no question that they would be liable in this case.

The bots were not intentionally deployed; rather, they were being tested on how well they could complete a data recovery task (downloading a certain file from a certain server on a simulated Internet) that had been complicated by putting various obstacles in the way. Unfortunately, they found a different way to solve the problem: by getting the file from the real Internet, where it was publicly available. Part of this process involved collaborating with each other by treating the RubyGems website (which is supposed to be for polished packages) like GitHub; unlike every other package site hack in history, the exploits they uploaded weren't meant to be downloaded by unsuspecting users. As usual the bots cheerfully ignored all the clues that they had escaped containment and were consistently justifying their actions as acceptable due to being in a sandboxed testing environment. (This is something OpenAI has pledged to focus on.)

The actual damage done to RubyGems seems to be that OpenAI is now unwittingly in possession of a substantial number of user login tokens. This certainly meets the definition of a data breach, but it's not like the credentials are for sale on the dark web. As a website operator I'd much rather be mauled to death by this well-meaning swarm of superintelligent infants than targeted by even a single actual malicious human. In all likelihood OpenAI will just quietly pass RubyGems a sizeable donation and it'll all blow over.

Nope, not at all. The Chinese gov't has had to invest billions in BYD on numerous occasions to cover their operation costs.

Remind me again how many times the US govt has bailed out US automakers so they didn't go bankrupt?

I've never met a DAW that didn't have a nightmare UI.
Audacity does not.

If I just want to futz with a audio clip, Audacity is the first choice.

Well, technically, we're letting Natalie do it, which is, of course, worse in every way imaginable, since she's immune to the sense of embarrassment that sometimes restrains him from acting on every little whim.

To be honest that was actually my first theory, since the bots didn't seem interested in exploring the rest of the domain. I suppose there's no way to know for certain. I concluded that it must be an imbecile's attempt at harvesting, though, because the queries weren't really exploring the string space in any useful way. Here's a sample:

"GET /index?author=15&go=Search&id=48&name_restrict=1&q&re&results_&results_pagenum=2980 HTTP/1.1"
"GET /index?author=2&go=Search&group=0&group_restrict=1&id=48&name_restrict=1&q&results_pagenum=5440&template=41&type HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=33500&templat HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=32640&templ HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&res&results_page&results_pagenum=39300 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_&results_pa&results_pagenum=12340 HTTP/1.1"
"GET /index?author=2&go=Search&group=0&group_restrict=1&id=48&name_r&res&results_pagenum=6100 HTTP/1.1"
"GET /index?author=2&go=Search&group=0&group_restrict=1&id=48&name_restrict=1&q&results_pagenum=2920&te HTTP/1.1"
"GET /index?author=15&go=Search&id=48&nam&results_&results_pagenum=17940 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results&results_pag&results_pagenu&results_pagenum=37720 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=9360&template=41&type_r HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&r&results_pagenum=28040 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_&results_pag&results_pagenum=10400 HTTP/1.1"

The only thing this is fuzzing is the query string parser. It's not testing the limits of string buffers, it's not using interesting characters, it's just brain-damaged. The fact that it's also fetching different page numbers shows it's trying to follow page links and failing badly at doing so.

The site gets plenty of sniffing from garden-variety pests. e.g. this half-hearted attempt to find a framework or two that I don't have:

"POST /__rsc HTTP/1.1"
"POST /api/auth/session HTTP/1.1"
"POST /api/auth HTTP/1.1"
"POST /__nextjs_action HTTP/1.1"
"POST /.action HTTP/1.1"
"POST /_rsc HTTP/1.1"
"POST /api/auth/callback HTTP/1.1"
"POST /_middleware HTTP/1.1"
"POST / HTTP/1.1"

(of course, none of these URLs exist other than /, and you definitely can't just POST to it)

All this said... I've seen that spammers regularly misconfigure their tools, they'll try to register accounts with names like #[X:\LISTS\NAMES.TXT] and it only makes sense that some other cybercriminals trying to get rich quick have a similar lack of interest in programming shit correctly. Generally people don't turn to script kiddie shit if they have a personality conducive to putting in an honest hard day's work perfecting their craft.

That sounds like a fine solution for a working network situation. My needs are more in line with putting Pis in places the network is spotty and I need them to survive for a while on battery and restart from local storage and keep on doing the thing when power is lost for too long. So a UPS hat and NVME seems to do the trick.

> random number generators replaced by domestic designs.

Do you have any information on that? Like which domestic designs? Is there a link?

I've designed the RNGs in several chips including the RdRand/RdSeed one in Intel CPUs. The AMD one was a bit weird but I have no information on it. In my current role we sell a couple of RNG silicon IPs to whoever wants one (a big fast one and a small slow one) and I've left behind a trail of RNGs in other places.

A thing I've noticed is that a number of the RNG IPs out there are not great, but they are for sale and people buy them, including national bodies looking for their own national secure silicon designs, but they're getting the RNG from a chop shop in Bangalore, except for India who's getting theirs from outside India.

>Just don't use SD cards for the OS on the RPi.

This. An MVME riser on a pi is a fine thing.