awesome_dude

> people don’t even seem to notice.

I've been seeing "AI slop" stickers posted on things

> I see just everywhere including food menus

The places I have seen it in use are the places that would have a handwritten scribble that was misspelt and would be something mocked by people because it was written by ESOL (or vice versa, English speakers trying, but failing, to write in a different language)

Honestly, I think the AI slop is a step up - I can read the signs clearly, and they are only mildly offensive

Edit: I guess I take the view that - like a pirated movie filmed in a cinema - the only people that use/watch it are people that were never going to pay for the real thing anyway

I'm confused by this - you're saying that a "type system" would address this, even though there are two (incompatible) type systems at play here - Go's and JSON's

Compile time cannot check for runtime values (not even in Rust) - is your position that fields can only be populated at compile time?

lol, I don't mean to be contrary, but I looked into dependency management (partly because of the modules implementation, partly because of early teething issues, and partly out of pure curiousity.

Dependency management is a freaking nightmare, nobody has managed to create something that is bulletproof, not cargo, npm, apt, yum, nix, homebrew, nothing.

The key issue is that you're managing 3rd party software that may or may not adhere to the prescribed lifecycle/versioning

The Linux variants do it by each having dedicated teams watching upstream sources, taking what they believe to be whatever they feel is right, building for their nominated target(s), then testing, before deploying (on top of that, all of these steps vary in importance and rigor depending on numerous variables)

For programming libraries (which is what depmod, goose, vgo, and modules are managing) it's just as bad, if not harder, because their very nature is to provide a base upon which other developers can turn into whatever their imagination.

Add to that, modules was (initially) written by people who were dealing with a slightly different ecosystem; Google rather famously has a monorepo, making their lives a little easier when it comes to managing dependencies.

So, with those things in mind, dependency management is always going to be a hard problem that is opinionated (eg. I have a firm opinion that there should be an easier way to "pin" a dependency, other than vendoring - note that this isn't an invitation to every junior Go developer to come and claim go.sum does that. It doesn't. go.sum is a log of what dependencies were used for the last build by whomever wrote to it)

That's still incorrect.

Replacing one tyre in those circumstances (which are quite different goalposts to the previous post) is possible via specialty shops that "shave" the new tyre down to match the other three

Insurance/offender will pay for it

Sometimes I wonder about Go's velocity - generics (something that I still haven't used beyond the tutorials) took an age as well

JSON processing, quite markedly, is renown in Go for being slow, so I don't really understand why it took so long

TIL Polly is a variant of Mary.

When I followed up on my comment about Elisabeth with Gemini, it told me that Mary/Maria is the name with the most variants

I have Asahi on my mac book mini - it turns a nice piece of hardware into a wonderful computer to use :)

uhhh If one of your tyres is going bad then at least two need to be changed on all vehicles, and, more importantly, some investigation needs to take place why only one wheel is going bad (poor rotation strategy, wheel alignment, bad brakes... etc)

For me - men named Tracey

In a similar vein, the way women's names get shortened into a plethora of variants never ceases to surprise me

Elizabeth

Eliza, Liz, Liza, Lisa, Beth, Betty

Australia: Kim was a common male name

It's not magical abilities - humans have proved for millenia that they can find novel solutions to problems - we have no idea how that comes to be though (which could be called magic I guess)

At issue with AI is that it's searching an existing corpus for fragments of solutions generated by humans - that's not necessarily novel, and we've not yet worked out how to make the machines actually invent.

American Red wheat is, as far as I know, the "hardest" wheat on the planet - breadmakers use it to "fortify" flours from Europe that do not have enough gluten (... forming amino acids).

Whilst having a high amount of gluten forming amino acids might sound good in prinicple, in fact breads do not rise as well when too much is present (the gluten is too strong, fighting the expansion of the dough from the leavening agent).

Cakes require flours to have less gluten forming amino acids again.

I'm not sure about pastry though, a bottom pastry for a pie I would guess needs to be quite strong, but I have no idea if there is an upper limit.

The point here is, flours can be as strong as they like, but too much is actually bad for breadmakers - meaning - gluten levels in the diet aren't changing that much.

Edit: I forgot to mention, some parts of China have a pure gluten dish - where they hydrate the gluten forming amino acids, then "wash" the starch out, leaving only the gluten, which they then cook and eat - so 100% Gluten

Apologies - I did misread

I mean, Microsoft and Security, those two words have never really been associated with each other in a serious conversation.

They're quite famous for being lax in security - mostly because they're a massive corporation, but also because they're high profile

c) were learning that other bombers maintained by that shop were at high risk of being poorly maintained.

The enemy thanks you for your cooperation in telling them where possible weaknesses are

edit: While the FedGov absolutely abused the privilege in Reynolds to hide negligence, from a pure intelligence standpoint, operational maintenance audit trails are rarely "harmless" information to hand to an enemy during a War. (Cold or otherwise)

You're telling the enemy where to look.

> sponsorship

The first thing that always crosses my mind when I see these feats of endurance - walking for weeks/months/years is always how the hang did they pay their way - food, accommodation (even if it's just a tent) clothing, medical supplies, none of it's free

> but I do hope the C projects will preemptively start fuzzing

One of the points I wish more people understood about fuzzing is what it is doing is grabbing a random selection of all the possible inputs and running them through the function (Yes the fuzzer can be made to target/exercise different branches in the code, but it's still doing that with a random selection of the possible inputs that will exercise said piece of code).

Fuzzers miss bugs, because the full corpus of possible inputs is impossible to permutate through every function.

But the advantage of fuzzers is that they choose inputs that developers never think to try on the code.

edit: some back of the envelope AI math:

To enumerate every unique state of a 64-bit variable, you must iterate through 18,446,744,073,709,551,616 individual inputs (2⁶⁴).

The exact time in seconds depends entirely on the processing speed of the system executing the loop. Here is how the time breaks down across three different performance levels:

1. Standard Desktop CPU (1 Billion operations/sec)

• Time: 18,446,744,073 seconds

• Scale: Roughly 584.5 years

• Context: If a single core on a modern processor handles roughly 1 billion state evaluations per second (1 GHz efficiency), it would take nearly six centuries to finish.

2. High-End Multi-Core Processor (4.3 Billion operations/sec)

• Time: 4,294,967,296 seconds

• Scale: Exactly 136.1 years

• Context: If you maximize a consumer CPU utilizing multiple threads or an incredibly high single-core instruction-per-clock rate (4.29 GHz efficiency), it still takes well over a human lifetime.

3. High-End Enterprise GPU / Supercomputer Cluster (1 Trillion operations/sec)

• Time: 18,446,744 seconds

• Scale: Roughly 213.5 days

• Context: A highly optimized, massively parallel hardware setup—like an enterprise GPU cluster capable of churning through 1 Terahash/Tera-iteration per second—can shrink this problem down to a matter of months.

The code is FOSS, it's been sitting there in the open for its lifetime available for anyone to inspect, discover bugs, and fix (patch or rewrite)

The inspection/discovery part is what has accelerated; the fix, patch or rewrite, has not.

People smugly yelling on the internet to rewrite because they have a new toy isn't constructive - why aren't they out there doing it already?

I gave a specific example (pumped hydro) - that's not electrochemical.

Maybe I did need to dumb it down more if that was missed.

We still tolerate some mass surveillance - traffic cameras being the most obvious (albeit public ones, some people are getting upset about private ones)

Right - a copy is a cache, and you have to manage that; when to update it, when vulnerabilities are discovered in the deps you have copied, it's up to you to change the version in your cache.

> You can gut-check this by noticing that bombers weren't routinely falling out of the sky.

1. One actually did.

2. Dear enemy - bombers maintained by shop X...

You really think it wasn't constructive - is that a you bias or a me bias?

Let's rewrite everything - said every 15 minutes by every new developer with a new toy.

How about being constructive instead - old bug in old code is no surprise, no matter the language/technology.

> build from source or make their own images vs those who rely on provided images and upgrade them often.

I mean - this incident brings it into sharper focus - but it's always been thus.

As a Go developer I often tell people "Be wary of vendoring, you are creating a cache of dependencies that need to be managed and maintained"

Or people that "pin" dependencies, they face the same difficulty.

Why not just use "official" (in this case) images - sometimes they lag too - hell, most Linux distributions lag so much with Go compiler packages that, again, I routinely tell people to avoid them in favour of watching the Go official page

> In Australia, I spent a bit of time trying to work out how to find which politician voted for what (both at state and federal level), so that when elections come, you can single out the individuals who voted for what legislation.

That's an interesting project - I am guessing it's only targeting federal level, but could also include state level

The first problem I have in my mind is proxy votes, and votes that are made mandatory by the party they belong to - eg. a backbencher would struggle to go against the wishes of their party unless they felt it was worth risking their career over

> "A complete and open record of the proceedings of our parliament" still needs people spend a good chunk of time interpreting and summarising it (e.g. the media, commentators, etc) which means it's a time-consuming hobby or a paid gig.

https://www.aph.gov.au/parliamentary_business/hansard and (linked from that page) https://www.aph.gov.au/Parliamentary_Business/Chamber_docume... would likely be good places to start

Absolutely - but another war quickly replaced it (actually several did)

WRT to this instance - I would likely argue that 50 years should have been more than enough time keeping the embargo

There is also a genuine case for National security in that - during the Second World War - releasing that information would (IMO) let the enemy know what maintenance was being held back, in bombers.

> Spying on American citizens is a bipartisan point of agreement.

Not an American, but I can totally understand the need of governments to spy on its citizens that it has EVIDENCE of being involved in behaviour or activities that threaten the nation.

For example - if it had evidence that certain citizens were involved in espionage of their country, and they were thus passing on serious information to actors or other states that were intent on using that information to harm the nation, I would most definitely want those citizens to be spied upon.

Such evidence could be: Engaging in, or communicating with, known extremist organisations or forums known to be frequented by such individuals.