Pasting a huge AI generated explanation to a problem in an issue or pull-request is nothing but RUDE. Don't do it. You look stupid and the receivers of that feel insulted.
We are humans. We communicate like humans. Fine, use the tools you like, but don't insult us.
@safigo @mk I'll answer literally since your "why?" seems well-intentioned, given your other comments.
Painting a choice between "AI slop description" and "no description at all" is a false dicothomy, which is a rhetorical fallacy ill-intentioned people try to pull: portraying a bad-thing-X as "X or even-worse-Y". It's a fallacy because those are not the only options. The issue/PR author always has the 3rd option of writing a normal human message. That's why you got the "false dilemma" reply.
I did this Summary A signed integer overflow in tftp_set_timeouts caused by Curl_timeleft_ms() returning TIMEDIFF_T_MAX (9223372036854775807), which when added to 500 at tftp.c:171 overflows the ti...
@bagder now I see. You were too polite in your description. I thought it would be a PR with a description generated by LLM.
Your cases are just copy paste from a LLM after asking it to find a security issue, without understanding or even not reading an answer…
It’s sad…
@bagder @safigo Raymond Chen calls these "being on the other side of an airtight hatchway", which I really like.
Sorry you are dealing with this especially when so overworked from recent security reports. 
https://devblogs.microsoft.com/oldnewthing/20221004-00/?p=107246
daniel:// stenberg://
Anton Ohorodnyk
Michael Knudsen
Hisham
Billy O'Neal
Sharkfie 
Sibshops
F4GRX Sébastien