MICROSOFT CAN ERASE YOUR ENTIRE COMPUTER!
A man is going viral after exposing what millions of Windows users are just now realizing about Bill Gates’ Microsoft.
"I think they should have to go to jail for this."
Windows updates quietly turn on OneDrive without a plain English warning.
Your files don’t get “backed up.”
They get moved.
Your computer becomes a temporary access point.
Microsoft’s servers become the primary copy.
Then the trap snaps shut.
People report:
• Family photos gone
• Work files wiped
• Years of data erased
• Clean desktops with no warning
• A little icon asking: “Where are my files?”
Many thought it was ransomware.
It wasn’t.
Turning OneDrive off can delete everything locally.
Deleting files to “free up space” deletes them everywhere.
The only way out? A buried menu… or a YouTube tutorial.
Nowhere does it clearly say:
“We are transferring your entire computer to our servers.”
Millions clicked “Update” without knowing this was included.
If a company can silently take control of your files and delete them with one wrong click - how is this not malware?
The “age verification app” the EU wants to impose on the world got hacked in 2 minutes.
Step 1: Present a “privacy-respecting” but hackable solution.
Step 2: Get hacked (you are here).
Step 3: Remove privacy to "fix" it.
Result: a surveillance tool sold as “privacy-respecting”.
So the truth is finally coming out
Yesterday, Anthropic said users were hitting limits because of their own usage patterns. Today, Boris is telling us they're cutting OpenClaw and third-party tools from subscriptions and prioritizing capacity for their own products
That's a very different story. And a much closer one to what users suspected all along
It also explains what people are actually seeing
- Harsher limits
- Worse quality
- Workflows breaking overnight
That is why @lydiahallie's explanation ('we investigated, you have a skill issue') landed so poorly and didn't reflect users' actual experience
The one-time credit and refund option are a real first step. But that only fixes the bill
The deeper damage came from changing the rules AFTER people had already built around them
People can accept tighter limits
People can accept "subs don't cover this workload"
People can even accept higher prices
What they cannot accept is being gaslit first and informed later
If Anthropic wants to rebuild trust, the fix is not complicated:
- Publish actual token budgets per tier, the same way they already do for the API
- Show what each message costs against the budget
- Let users verify for themselves whether the deal changed
- Tell people ahead of time when the deal is going to change
People can plan around hard limits
They cannot plan around a company that changes the deal first, gaslights users, and explains it only after the backlash
PSA: If you've been running out of Claude session quotas on Max tier, you're not alone. Read this.
Some insane Redditor reverse engineered the Claude binaries with MITM to find 2 bugs that could have caused cache-invalidation. Tokens that aren't cached are 10x-20x more expensive and are killing your quota.
If you're using your API keys with Claude this is even worse. This is also likely why this isn't uniform, while over 500 folks replied to me and said "me too", many (including me) didn't see this issue.
There are 2 issues that are compounded here (per Redditor, I haven't independently confirmed this) :
1s bug he found is a string replacement bug in bun that invalidates cache. Apparently this has to do with the custom @bunjavascript binary that ships with standalone Claude CLI.
The workaround there is to use Claude with `npx @anthropic-ai/claude-code`
2nd bug is worse, he claims that --resume always breaks cache. And there doesn't seem to be a workaround there, except pinning to a very old version (that will miss on tons of features)
This bug is also documented on Github and confirmed by other folks.
I won't entertain the conspiracy theories there that Anthropic "chooses" to ignore these bugs because it gets them more $$$, they are actively benefiting from everyone hitting as much cached tokens as possible, so this is absolutely a great find and it does align with my thoughts earlier.
The very sudden spike in reporting for this, the non-uniform nature (some folks are completely fine, some folks are hitting quotas after saying "hey") definitely points to a bug.
cc @trq212@bcherny@_catwu for visibility in case this helps all of us.