61–70 of 128 posts
Who would report this? Are they hoping for a bug bounty or they know their competitors are using the technique?
I would have done the same.
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.
It was a mess before, and it will only get worse, but at least I can get some work done 4 times a day.
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.
Some were already that and even more, because of other reasons. The Cathedral model, described in "The Cathedral and the Bazaar".
Even without hacks, Copilot is still a cheap way to use Claude models: - $10/month - Copilot CLI for Claude Code type CLI, VS Code for GUI - 300 requests (prompts) on Sonnet 4.5, 100 on Opus 4.6 (3x) - One prompt only ever consumes one request, regardless of tokens used - Agents auto plan tasks and create PRs - "New Agent" in VS Code runs agent locally - "New Cloud Agent" runs agent in the cloud ( https://github.com/…
+1. I see all these posts about tokens, and I'm like "who's paying by the token?"
There’s some exceptions eg Claude Max
Even without hacks, Copilot is still a cheap way to use Claude models: - $10/month - Copilot CLI for Claude Code type CLI, VS Code for GUI - 300 requests (prompts) on Sonnet 4.5, 100 on Opus 4.6 (3x) - One prompt only ever consumes one request, regardless of tokens used - Agents auto plan tasks and create PRs - "New Agent" in VS Code runs agent locally - "New Cloud Agent" runs agent in the cloud ( https://github.com/…
So 100 Opus requests a month? That's not a lot.
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.
Nothing compared to pirated CDs with Office and Windows, 20 yrs back.
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.
On the other hand, since they own GitHub they can (in theory) monitor the downloads, check for IPs belonging to businesses, and use it as evidence in piracy cases.
Earlier quoted context omitted.
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…
> 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. Reminds me of an interaction I was forced to have with a chatbot over the phone for “customer service”. It kept apologizing, saying “I’m sorry to hear that.” in response to my issues. The thing is, it wasn’t sorry…
We need a law that forces management to be regularly exposed to their own customer service.
Earlier quoted context omitted.
Recently? They've been shipping absolute trash for 15 years, and still haven't reached the bottom apparently.
.NET is actually, unironically good . But yes, this is one of few exceptions, unfortunately.
I think C# and .Net are objectively better to use than Java or C++.
But the tooling and documentation is kind of a mess. Do you build with the "dotnet" command, or the "msbuild" command? When should you prefer "nuget restore" over "dotnet restore"? Should you put "true" in the .csproj instead? What's the difference between a reference and using Nuget to install a package? What's the difference between "Framework" and "Core"? Why, in 2026, do I still need to tell it not to prefer 32-bit binaries?
It's getting better, but there's still 20 years of documentation, how-to articles, StackOverflow Q&A, blogs, and books telling you to do old, broken, and out of date stuff, and finding good information about the specific version you're using can be difficult.
Admittedly, my perspective is skewed because I had never used C# and .Net before jumping in to a large .Net Framework project with hundreds of sub-projects developed over 15-20 years.