Hacker News

+1. I see all these posts about tokens, and I'm like "who's paying by the token?"

So 100 Opus requests a month? That's not a lot.

I've had single prompt to Opus consume as many as 13 premium messages. The Copilot harness is so gimped so they can abstract tokens from messages. Every person that started with Copilot that I know that tried CC were amazed at the power difference. Stepping out of a golf cart and into <your favorite fast car>.

“Not my job” award winner.

We use a “Managed Azure DevOps Pool”. This allows you to use Azure VM types of your choosing for build agents, but they can also still use the exact same images as the regular managed build agents which works well for us since we have no desire to manage the OS of our agent (doing updates, etc), but we get to choose beefier hardware specs.

An annoying limitation though is that Microsoft’s images only work on “Gen 1” VMs, which limits available VM types.

Someone posted on one of Microsoft’s forums or GitHub repositories to please update the images to also work on Gen 2 VMs, I can’t remember for sure right now which forum, was probably the “Azure Managed DecOps Pools” forum.

Reply was “we can’t do anything about this, go post in forum for other team, issue closed”.

As far as I’m concerned, they’re all Microsoft Azure, why should people have to make another post, at the very least move the issue to the correct place, or even better, internally take it up with the other team since it’s severely crippling your own “product”.

Useless and lazy employees.

On the other hand ... I recently had to deal with official Microsoft Support for an Azure service degradation / silent failure.

Their email responses were broadly all like this -- fully drafted by GPT. The only thing i liked about that whole exchange was that GPT was readily willing to concede that all the details and observations I included point to a service degradation and failure on Microsoft side. A purely human mind would not have so readily conceded the point without some hedging or dilly-dallying or keeping some options open to avoid accepting blame.

I wholly agree, the response screams “copied from ChatGPT” to me. “Contributions” like these comments and drive by PRs are a curse on open source and software development in general.

As someone who takes pride in being thorough and detail oriented, I cannot stand when people provide the bare minimum of effort in response. Earlier this week I created a bug report for an internal software project on another team. It was a bizarre behavior, so out of curiosity and a desire to be truly helpful, I spent a couple hours whittling the issue down to a small, reproducible test case. I even had someone on my team run through the reproduction steps to confirm it was reproducible on at least one other environment.

The next day, the PM of the other team responded with a _screenshot of an AI conversation_ saying the issue was on my end for misusing a standard CLI tool. I was offended on so many levels. For one, I wasn’t using the CLI tool in the way it describes, and even if I was it wouldn’t affect the bug. But the bigger problem is that this person thinks a screenshot of an AI conversation is an acceptable response. Is this what talking to semi technical roles is going to be like from now on? I get to argue with an LLM by proxy of another human? Fuck that.

Some were already that and even more, because of other reasons. The Cathedral model, described in "The Cathedral and the Bazaar".

No where in the comment do they assert they are work for Microsoft.

This is a peer-review.

Exactly I have seen these know it all comments on my own repos and also tldraw's issues when adding issues. They add nothing to the conversation, they just paste the conversation into some coding tool and spit out the info.

> I completely understand why some projects are in whitelist-contributors-only mode. It's becoming a mess.

That repo alone has 1.1k open pull requests, madness.

Everyone is a maintainer of Microsoft. Everyone is testing their buggy products, as they leak information like a wire only umbrella. It is sad that more people who use co-pilot know that they are training it at a cost of millions of gallons of fresh drinking water.

It was a mess before, and it will only get worse, but at least I can get some work done 4 times a day.

Some part of me says, let their vibing have a cost, since clearly "overall product quality going to shit" hasn't had a visible effect on their trajectory

They tried to report it to MSRC, likely to get a bounty, and when they were stiffed there and advised to make it public they did.

I would have done the same.

They don't care, they would rather let you use pirated MS software than move to Linux. There is a repo on GH with powershell scripts for activating windows/office and they let it sit there. Just checked, repo has 165K stars.

This could be the same, they know devs mostly prefer to use cursor and/or claude than copilot.

Vibes all the way down. "Please check out this other slop issue with 5-600 other tickets pointed to it" -- I was going to ask, how is anyone supposed to make sense of such a mess, but I guess the answer is "no human is supposed to"

You must be new here.

Microsoft notoriously tolerated pirated Windows and Office installations for about a decade and a half, to solidify their usage as de facto standard and expected. Tolerating unofficial free usage of their latest products is standard procedure for MS.

By recently, you mean since 2007

Their software seems like it. Their sales team is brutal.

Recently? They've been shipping absolute trash for 15 years, and still haven't reached the bottom apparently.

Sure but the exploit here isn’t prompt injection, it is an edge case in their billing that isn’t attributing agent calls correctly.

It reminds me of when I used to write lisp, where code is data. You can abuse reflection (and macros) to great effect, but you never feel safe.

See also: string interpolation and SQL injection, (unhygienic) C macros

Allowing phreaking was an intentional decision, because otherwise they could have carried half as many channels on each link.

It'll be a sad day for Little Bobby Tables if in-band signaling ever goes out of fashion.

The access to premium models. This much should have been evident from reading the ticket.

> Copilot Chat Extension Version: 0.37.2026013101

> 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.

Oh that was pithy, mean, and just the right amount of taking-it-personally. Well done!