namelosw
Joined 8 years ago
Joined 8 years ago
These combinations are questionable and very easy to filter, probably with Luna/Haiku tier of models that are able to tell things might get fishy here, and it would likely escalate to heavier checks and trigger KYC or straight banning.
Those are only my guess and probably aren't how the system works, but I think these rules are fairly easy to come up with for developers who have any idea of anti-abuse. I've seen too many Chinese posts mourning their accounts and communicating that their setups there would be similar mechanisms, I would say.
In previous months, there was news that Claude Code uploading a special signal for the Chinese timezone is pretty evident. I probably got away from having serious insomnia, using PST on my computers, and exclusively speaking English with those models lol.
Especially for Claude because Anthropic is very good at identifying mainland Chinese and getting them banned in hours. There are many of them who are willing to pay more than the original rate for a stable experience.
It's very hard for them because they'll need a legit phone number and bank cards that are not issued in China, and a clean enough IP, etc. and those better match together to make sense. (Back in the day, ChatGPT required resident IPs, which made it worse, but they worry about growth more now). Obviously, they have to use a VPN to access the real Internet, and most of the IPs they can find are shared with bots and abusers.
It's an art to come up with a great test suite that covers just enough and minimizes overlap, not only survives but also helps with refactoring.
It's essentially punishing players for playing well, and often could be gamed by playing badly intentionally.
Theoretically and conceptually I agree. But in practice there are a lot of programming languages aren’t as expressive. People prefer codebases with duplications rather than visitor patterns everywhere. In essence, visitor pattern is a tool to solve multi-dimensional abstraction problems, just like type classes in Haskell or CLOS in Common Lisp. But it’s so verbose and non-straightforward so more often than not it’s not worth it even conceptually it’s a legit case for “single source of truth”.
The current implementation isn't command-line, but a re-implemented GUI in disguise, awkward and even more buggy. Why should I use that over a GUI? I would prefer Electron over those TUI unless I have to SSH.
A great QA can understand the features of a product quickly, turn those concepts into some sort of grid or matrix in their mind, then pull a bunch of paths and scenarios with estimated priorities and probabilities at a fast and efficient pace, all with great coverage. They can also identify features contradicting each other more quickly than product people.
I think a good QA is capable of being a great vibe coder nowadays, too. If you can write great test suites (write names only), agents nowadays are able to turn those specs into decent codebases. Comparatively, I know a lot of decent dev having not very good taste in testing, who often write overlapping tests or missing important paths.
Source: trust me bro
Furthermore, within China, alternative conspiracy theories claiming that the virus came from the US were allowed to circulate. A significant number of people in China actually believe that theory.