<![CDATA[When I get a report which is obviously LLM output, I do not read it.]]>When I get a report which is obviously LLM output, I do not read it.

Instead, I ask the sender to summarize the novella in their own words, because I do not have the time, unless they explain to me why it‘s worthwhile.

My advice: do the same. Deflect, politely, LLM dumps. Let‘s make this a conversational norm.

]]>https://board.circlewithadot.net/topic/8aadc172-20cd-4395-a341-4616b0d9c69f/when-i-get-a-report-which-is-obviously-llm-output-i-do-not-read-it.RSS for NodeFri, 05 Jun 2026 09:00:24 GMTSun, 31 May 2026 07:33:04 GMT60<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Mon, 01 Jun 2026 08:32:55 GMT]]>@cafeinux @icing ha, good idea. Next time!

]]>https://board.circlewithadot.net/post/https://mastodon.social/users/timsk/statuses/116673922665025380https://board.circlewithadot.net/post/https://mastodon.social/users/timsk/statuses/116673922665025380Mon, 01 Jun 2026 08:32:55 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Mon, 01 Jun 2026 02:57:06 GMT]]>@timsk
You were too kind. I'd have said that "I could have cancelled the fees because X and Y, but due to the fact that you made me read 8 pages of AI slop, please consider these fees as the tax to pay for my time."
@icing

]]>https://board.circlewithadot.net/post/https://infosec.exchange/users/cafeinux/statuses/116672602239990429https://board.circlewithadot.net/post/https://infosec.exchange/users/cafeinux/statuses/116672602239990429Mon, 01 Jun 2026 02:57:06 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 17:04:24 GMT]]>@dbof @icing Where I work llm code is your code and you are responsible for what it does. Blaming ai will not work.

]]>https://board.circlewithadot.net/post/https://olifant.social/users/burly/statuses/01KSZFWWB6X1C1F0RD9XW4EVFNhttps://board.circlewithadot.net/post/https://olifant.social/users/burly/statuses/01KSZFWWB6X1C1F0RD9XW4EVFNSun, 31 May 2026 17:04:24 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 16:23:11 GMT]]>@dbof @kgf @icing
Any of: Kill chains, Root cause analysis, Swiss cheese model, defence in depth, site safety procedures/policy mechanisms, staff training, education / certification, regulation about how it can be advertised, restrictions on places where those tools can be used (no not work near flammable gasses), making it a security/safety/compliance issue, administrative approvals/restrictions, ACLs etc

There are already metaphorical matches to tasks in non-IT industries for how to treat things that act violently / non-intuitively / unpredictably - I'm sure those procedures are a decent place to start.

Generally, they all orbit around whittling down the chances of a mistake being made, and whittling down the chances that something goes wrong when a mistake is made.

]]>https://board.circlewithadot.net/post/https://hachyderm.io/users/EndlessMason/statuses/116670109525965455https://board.circlewithadot.net/post/https://hachyderm.io/users/EndlessMason/statuses/116670109525965455Sun, 31 May 2026 16:23:11 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 16:04:33 GMT]]>@icing

"Thank you for your LLM generated report, I have passed it on to an LLM to read, the portion of your salary which would have paid you to write this report will be passed to the LLM owners instead"

]]>https://board.circlewithadot.net/post/https://mstdn.social/users/staringatclouds/statuses/116670036310241452https://board.circlewithadot.net/post/https://mstdn.social/users/staringatclouds/statuses/116670036310241452Sun, 31 May 2026 16:04:33 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 15:36:16 GMT]]>@kgf @EndlessMason @icing yeah of course, so that is the change. But non-it people do not know these flaws. They don't know (or ignore) how LLMs work. They also don't know how Photoshop works.

How do we evaluate this then?

]]>https://board.circlewithadot.net/post/https://infosec.exchange/users/dbof/statuses/116669925038048969https://board.circlewithadot.net/post/https://infosec.exchange/users/dbof/statuses/116669925038048969Sun, 31 May 2026 15:36:16 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 15:35:48 GMT]]>@dbof @icing
Hint: the Human selected a tool that made it either difficult or impossible for them to do a good job... and then they did a bad job.

Improving operator, tool, and environment can all contribute to better results...

I also think we're well past "computer does what operator says" especially on corp controlled autoupdate endpoints speaking to a sea of random corp clouds

]]>https://board.circlewithadot.net/post/https://hachyderm.io/users/EndlessMason/statuses/116669923225583544https://board.circlewithadot.net/post/https://hachyderm.io/users/EndlessMason/statuses/116669923225583544Sun, 31 May 2026 15:35:48 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 15:32:12 GMT]]>@dbof @EndlessMason @icing Except in the case of LLMs it is nearly the opposite: the computer never does exactly the thing you "tell" it to do, so it is never "right", only plausible-looking. Using an LLM at all is _begging_ for bugs.

]]>https://board.circlewithadot.net/post/https://hachyderm.io/users/kgf/statuses/116669909066155144https://board.circlewithadot.net/post/https://hachyderm.io/users/kgf/statuses/116669909066155144Sun, 31 May 2026 15:32:12 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 15:20:01 GMT]]>@EndlessMason @icing often we blame the users, sometimes the tools!

"Oh, you got hacked? You're to blame!"
"the spreadsheet calculated the wrong value"

In IT we always assume the computer does exactly the thing you tell it to do so it is never "wrong", you just put the wrong input out used or wrong. Yes, programs have bugs, but that is introduced by humans.

So should we blame humans for computer / algorithm / llm output? It's not so clear cut in my opinion.

]]>https://board.circlewithadot.net/post/https://infosec.exchange/users/dbof/statuses/116669861189702424https://board.circlewithadot.net/post/https://infosec.exchange/users/dbof/statuses/116669861189702424Sun, 31 May 2026 15:20:01 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 13:07:23 GMT]]>@dbof @icing
How do we react when people make mistakes with other tools?

]]>https://board.circlewithadot.net/post/https://hachyderm.io/users/EndlessMason/statuses/116669339661756424https://board.circlewithadot.net/post/https://hachyderm.io/users/EndlessMason/statuses/116669339661756424Sun, 31 May 2026 13:07:23 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 12:49:24 GMT]]>@icing I just told a student in an online only class to edit the wall of words or else. I'm an adjunct, I'm not paid enough to wade through shit.

]]>https://board.circlewithadot.net/post/https://indieweb.social/users/akamran/statuses/116669268910544982https://board.circlewithadot.net/post/https://indieweb.social/users/akamran/statuses/116669268910544982Sun, 31 May 2026 12:49:24 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 12:39:11 GMT]]>@dbof It depends on the situation. If your boss drop LLM output into your inbox and think that is the way to go, you are probably very limited.

If a random person drop such a thing into your project, you can refuse to process it without further work by the submitter.

I experience LLM output as part of being a maintainer. And a FOSS project should not feel obligated to accommodate such behavior, IMO.

I do not care what tools someone uses. I care how we communicate and collaborate.

]]>https://board.circlewithadot.net/post/https://chaos.social/users/icing/statuses/116669228757816668https://board.circlewithadot.net/post/https://chaos.social/users/icing/statuses/116669228757816668Sun, 31 May 2026 12:39:11 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 12:28:37 GMT]]>@icing well I just wrote a rant about this. How can I react to mistakes made with or using AI? Can we always blame the person, or should we blame the AI companies for that?

What can I reasonably enforce as a "conversational norm", now that AI written mails and documents are becoming the norm? I do not want to rant and argue every time I get AI Slop sent to me..

]]>https://board.circlewithadot.net/post/https://infosec.exchange/users/dbof/statuses/116669187189959862https://board.circlewithadot.net/post/https://infosec.exchange/users/dbof/statuses/116669187189959862Sun, 31 May 2026 12:28:37 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 12:25:47 GMT]]>@icing @catsalad I love this idea.

]]>https://board.circlewithadot.net/post/https://mastodon.social/users/WTL/statuses/116669176061493114https://board.circlewithadot.net/post/https://mastodon.social/users/WTL/statuses/116669176061493114Sun, 31 May 2026 12:25:47 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 10:46:47 GMT]]>@icing ok now it's way more clear, I think I understand and agree 🙂 Thanks !

]]>https://board.circlewithadot.net/post/https://hostux.social/users/PorCus/statuses/116668786773207352https://board.circlewithadot.net/post/https://hostux.social/users/PorCus/statuses/116668786773207352Sun, 31 May 2026 10:46:47 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 10:24:44 GMT]]>@PorCus No. The prompt could be "Find a security vulnerability in ".

I'd want to know *what exactly* the submitted LLM output found and why it is a vulnerability (and not some bug).

In the reporters words. To make sure they read it. If they did not read/understand it, it is not a communication.

]]>https://board.circlewithadot.net/post/https://chaos.social/users/icing/statuses/116668700045626149https://board.circlewithadot.net/post/https://chaos.social/users/icing/statuses/116668700045626149Sun, 31 May 2026 10:24:44 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 10:20:34 GMT]]>@icing so in other words ' please send me the prompt ' ? would that be acceptable ?

]]>https://board.circlewithadot.net/post/https://hostux.social/users/PorCus/statuses/116668683681144409https://board.circlewithadot.net/post/https://hostux.social/users/PorCus/statuses/116668683681144409Sun, 31 May 2026 10:20:34 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 09:32:45 GMT]]>@icing Yeah I do this too. Arguing with an LLM is pointless, and if the other person is unable to make their points themselves then they're not an actual participant in the discussion.

]]>https://board.circlewithadot.net/post/https://swecyb.com/users/troed/statuses/116668495679155438https://board.circlewithadot.net/post/https://swecyb.com/users/troed/statuses/116668495679155438Sun, 31 May 2026 09:32:45 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 09:18:42 GMT]]>@icing
I replied: "I don't engage with AI slop, as I find it demeaning to both the sender and the recipient. After a brief investigation though, it appears that you signed up for a class but never attended, and since the class was not full, I'm happy to cancel any fees that were due. (You could have just asked for that in a two line email, and the result would have been the same.)"

]]>https://board.circlewithadot.net/post/https://mastodon.social/users/timsk/statuses/116668440403014939https://board.circlewithadot.net/post/https://mastodon.social/users/timsk/statuses/116668440403014939Sun, 31 May 2026 09:18:42 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 09:18:36 GMT]]>@icing in response to my automated message to a customer saying "you appear to owe some money, please settle up or get in touch if there's a problem", I got 8 pages of ChatGPT slop about how the debt doesn't exist, about legal precedents, threats of legal action for harassment, it went on and on.

]]>https://board.circlewithadot.net/post/https://mastodon.social/users/timsk/statuses/116668440023156761https://board.circlewithadot.net/post/https://mastodon.social/users/timsk/statuses/116668440023156761Sun, 31 May 2026 09:18:36 GMT<![CDATA[Reply to When I get a report which is obviously LLM output, I do not read it. on Sun, 31 May 2026 08:53:15 GMT]]>@icing
But won’t they just respond with an LLM summary? I suppose that does cut down your time wasted. 🤷‍♂️

]]>https://board.circlewithadot.net/post/https://mastodon.social/users/KimSJ/statuses/116668340331642576https://board.circlewithadot.net/post/https://mastodon.social/users/KimSJ/statuses/116668340331642576Sun, 31 May 2026 08:53:15 GMT