@encthenet Yep. Either by choice or vigilance fatigue, or being pressured by mgmt, etc.

The quality check is now being externalized on someone else.

I have seen examples where it did something akin to:

`let string = "this-is-a-string".replace(" ", "-")` complete with hard coded string and a replacement that'd never replace anything. Is the string the correct output? Sure? What's that replace doing there?

(Edit: This was during a code review I was obliged to perform, I do not prompt the slop machine myself)

"These things are good at generating code" is a phrase that makes me think that you do not review the output of the code generating hell machine.

For example, Muse's had a shell script who's usage example is (working from memory of @jonny 's thread) `print_home_dir.sh <default home dir>` that was literally just an `echo /hard/coded/dir`...which is just consumed by several other shell scripts in the environment, and included a big "AND NOTHING ELSE" in it. It's peak stupid.

This post is really well written. It explains what happened with KDE vs LLM, but it also goes into the issues with LLMs and the impacts far beyond OSS.

> https://pointieststick.com/2026/09/23/kde-and-ai-and-you-and-me/

So, Google support is pretty bad. I called them to verify that they received the needed information, then 24hrs later I received an email saying that I need to provide the information, and I reply to that email saying that I've provided that info, and if that isn't sufficient to tell me what info is needed, and never got a response after 24hrs.

As far as I can see, zero movement on an issue where I can't use my phone as a cell phone for 4 days now.

so much for quality Google engineering. Apparently they never thought anyone would use esims and want to switch back to a physical sim. Traveled recently, loaded a second esim into my phone, and in doing so, it looks like it disabled the physical sim slot when doing so.

At least that's my assessment since my sim card still doesn't work, and google support has to escalate the issue because their first tier support script doesn't fix things.

It is funny that it takes AI for companies to realize that they need to write docs.

So very confused by git documentation. git(1) under Reset, restore and revert says that git-reset changes the commit history.

But everywhere I've read, including git-reset(1) implies that git reset doesn't modify commit history and is the correct way to unstage files.

Can we please be consistent with documentation on what things do? I have a feeling that it should be the git reset MAY modify commit history, but yet, the docs are confusing.

Just looked through the security assessment on the rust rewrite of core utils, and this is why just rewriting everything in the last language is such a dangerous things. They literally threw out 20+ years of security fixes because they thought it was cool and would increase security.

At least a security assessment was done, but some of those failures are pretty bad, and very likely to have had serious security implications if they were deployed into any real world system. Setting mode bits incorrectly, TOCTOU, arbitrary file overwrites are just terrible.

Would I have likely introduced some of the bugs if I had done the work? Yes. Would I have done the work? No, I'm not that crazy.

I do wonder if they did white box or black box when they copied functionality. I'm suspecting black box because of some of the errors.

https://github.com/Zellic/publications/blob/master/uutils%20coreutils%20-%20Zellic%20Audit%20Report.pdf

Repeat after me. AI agents only act on the commands that it was told. The fact that it also does random stuff is known and expected and any deviation is a failure on the person/org.

An AI agent never acts on its own initiative.
> entirely on its own initiative

If you don't have proper seat belts on your AI agent, that is entirely a human problem, NOT an AI agent problem.

> https://mathstodon.xyz/users/gregeganSF/statuses/116473736484432679

Question, for people who learned concurrent programming in high level language like Python? How hard was/is it? And do you think you have a good grasp of it?

I'm curious as I learned it dealing with C, where you need it correct or you're likely to crash your code/kernel, vs getting weird behavior some of the time. But even though the underlying problems are exactly the same, I feel that in a high level language they might not be as clear/obvious.

I'm seeing some weird behavior with FastAPI and async.

I have a function:
```
async def foo(r=[]):
if r: return r[0]
r.append(someobj())
return r[0]
```

Now I have that declared on a route via the usual:
```
@router.get('/somepage')
async def get_somepage(foo : Annotated[someobj, Depends(foo)]):
xxx
```

But in the foo function, I print the id of the r list, and each time somepage is fetched, the list is different.

I did finally just move r into the module name space, and that fixed things. But it's pretty clear that FastAPI is doing something wonky with function calls.

#FastAPI #Python

@SnoopJ @david_chisnall it is very clearly a con artist rhetorical trick and it is baffling that the same group of people keep falling for it preemptively

Sounds like SRAA maybe be trying to bury their own "harmless flirting" problem.

> https://climatejustice.social/users/chu/statuses/116352339515975348

Ouch, just saw code checking if a bool is true with boolvar > 0.

So much of this sounds like the regular police, just amped up 10x.

> https://mstdn.social/users/_L1vY_/statuses/115934175737331125

Question, does C have a way to convert an enum value to a string? And if not, why not?

Even a simple tale this enum define and make an array of strings from it would be helpful.

I get too spoiled with python that makes things like that easy.

#CLang

Well, I had heard/assumed homebrew was better/more actively maintained, but I just found out that brew doesn't have nvi2, yet MacPorts does.

Just realized that this gives Mozilla permission to use your passwords.

> When you upload or input information through Firefox, you hereby grant us a nonexclusive, royalty-free, worldwide license to use that information to help you navigate, experience, and interact with online content as you indicate with your use of Firefox.

This is a really poorly worded grant. Mozilla does NOT need this right at all.

> https://mstdn.social/users/jschauma/statuses/114072572772110102

> these standards are in place to ensure our company, which transports guests from around the world, remains respectful to those with cultural sensitivities to tattoos.

Paraphrased: We're bigots and we need to make other bigots feel comfortable in their own bigotry.

This is the start of the slippery slope preventing people from being themselves, be it this or LGBTQIA+ or other.

> https://mastodon.social/users/nedhamson1/statuses/113710107738609469