31–40 of 128 posts
the "AI" bot closing the issue here is particularly funny
Billing for what?
> VS Code Version: 1.109.0-insider (Universal) - f3d99de
Presumably there is such thing as the freemium pay-able "Copilot Chat Extension" for VS Code product. Interesting, I guess.
Every time I see something about trying to control an LLM by sending instructions to the LLM, I wonder: have we really learned nothing of the pitfalls of in-band signaling since the days of phreaking?
Every time I see something about trying to control an LLM by sending instructions to the LLM, I wonder: have we really learned nothing of the pitfalls of in-band signaling since the days of phreaking?
Earlier quoted context omitted.
Let's just say they are pretending to be helpful, how about that? > "Peer review" no unless your "peers" are bots who regurgitate LLM slop.
You think they lied about reproducing the issue? It’s useful to know if a bug can be reproduced.
Good job, Microsoft.
The laat comment is a person pretending to be a maintainer of Microsoft. I have a gut feeling that these kind of people will only increase, and we'll have vibe engineers scouring popular repositories to ""contribute"" (note that the suggested fix is vague). I completely understand why some projects are in whitelist-contributors-only mode. It's becoming a mess.
No where in the comment do they assert they are work for Microsoft. This is a peer-review.
Let me slop an affirmative comment on this HIGH TRAFFIC issue so I get ENGAGEMENT on it and EYEBALLS on my vibed GitHub PROFILE and get STARS on my repos.
Every time I see something about trying to control an LLM by sending instructions to the LLM, I wonder: have we really learned nothing of the pitfalls of in-band signaling since the days of phreaking?
See also: string interpolation and SQL injection, (unhygienic) C macros