Well, if the service price were in any way tied to the cost of transmitting bytes, then even the 24hr scenarios would likely see a reduction in cost to customers. Instead we have overage fees and data caps to help with "network congestion", which tells us all how little they think of their customers.
How did they even know you did this? I cannot imagine what cause they could have for the ban. They actively want folks building tooling around and integrating with Claude Code.
I have no idea. The alternative is that my account just happened to be on the wrong side of their probably slop-coded abuse detection algorithm. Not really any better.
I would be surprised if the primary reason for banning third party clients isn't because they are collecting training data via telemetry and analytics in CC. I know CC needlessly connects to google infrastructure, I assume for analytics.
As I get older I more and more view convenience as the enemy of good. Luckily (or unluckily for some) a lot of the tradeoffs we are asked to make in the name of convenience are increasingly absurd. I have an easier and easier time going without these Faustian bargains.
IMHO The question is: who is in control? The user, or the profit-seeking company/control-seeking government?
There is nothing we can do to prevent companies from seeking profit. What we can do is to prefer tools that we control, if that choice is not available, then tools that we can abandon when we want, over tools that remove our control AND abandoning them would be prohibitively difficult.
On what OS have you noticed this? Very in character for microsoft to artificially slow non-windows downloads. Then again, my apt upgrades on Debian have been dog slow lately...
There is an entire generation of devs that TFS ruined for version control. I've had to essentially rehabilitate folks and heal old TFS wounds to get them properly using git (so many copies of repos on their filesystem...).
First product is called SecureCoop, that either opens the coop door or monitors another coop opener, then sends phone notifications if there are issues. Door didn't open on time, door is stuck, etc.
Next product will be battery security cameras trained on predator models (raccoon, fox, snake). Then the next one will be an electric fence monitor. All solar powered.
Basically going for back yard security for small hobby farms.
Biggest hurdle has been that I only knew 5% of what I needed to know to do this. Haha. Many mistakes. But now am close to visiting the FCC lab for SDoC verification, and then I can legally sell.
The difference between physical and software controls is pretty straightforward. (Closed source) software controls are just asking politely. Physical controls are making it so.
May be but corporate greed for data surveillance occasionally surpasses the needs of state actors so much that they'll voluntarily invent features on the same level.
Google/Apple can in the future announce a "safety" feature that periodically announce Airtag'ish Bluetooth beacons even when in Airplane or powered off mode.
Comes down to the model of trust as much as any threat model. I don't need to perceive or even conceive of a specific threat to want to safeguard my privacy, even aggressively if I so desire.
I have a separate removable SSD I can boot from to work with Claude in a dedicated environment. It is nice being able to offload environment set up and what not to the agent. That environment has wifi credentials for an isolated LAN. I am much more permissive of Claude on that system. I even automatically allow it WebSearch, but not WebFetch (much larger injection surface). It still cannot do anything requiring sudo.
reply