Let's hope the component shortages will drive performance improvements in Apps as it will be unfeasible to expect higher specs to fix performance bottlenecks. Constraints can drive good behavior.
I remember a few years back when Jon Blow (Braid, The Witness) did a few talks about the fact that the biggest progress in recent years had been in hardware performance, making lazy software development standard since the hardware made it so easy to ignore any limitations.
I'm not as much of a fan these days but I do hope these limitations have the effect of improving best practices.
Looks like the blog could use a HN=True. Hope the author won't get banned...
> Error: API rate limit exceeded for app ID 7cc6c241b6e6762bf384. If you reach out to GitHub Support for help, please include the request ID E9FC:7BEBA:6CDB3B4:6485458:699EE247 and timestamp 2026-02-25 11:51:35 UTC. For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https://docs.github.com/en/site-policy/github-terms/github-t...).
Exactly, I've seen people who bought a Mac Mini and ended up running claw against a claude subscription. Completely misunderstand the point of local models. Plus, there was more hype about running claw way cheaper on Raspberry Pi which cost the stock price of Raspberry maker to skyrocket.
Some of the comments here show that technical people set these things up for non-technical people, which is just one step away from a misstep. Time will show whether this is similar in behavior to the "I can run it" mindset that people had with local models before. A small dopamine hit to see "it can be done" in order to end up a cloud service in the long run.
The host shenanigans are simpler addressed with `git config core.sshCommand` which overrides the default key and selects the desired one on a per repository level.
Doesn’t work for cloning, obviously. The way I handle it is I have ssh look at the hostname and path passed by git and decide which identity to use. This is very easy in openssh 10.0+ using the command matching syntax, and more difficult to varying degrees on earlier versions of openssh, depending on your OS.
"Green: account older than 1 year — senior devs making first OSS contributions shouldn't be flagged" - this makes old accounts more valuable, suggesting account takeovers to flag accounts as valuable.
That's a fair point. Right now the logic assumes age equals trust, which is obviously a bit of a leap. It also has the side effect of flagging a real person who just created an account to make a legit contribution.
The goal here was just to catch the obvious burner accounts created yesterday. How would you handle this verification instead? Or would you just not use account age at all as an indicator? I'd love to make the logic more robust.
Do you know by any chance if Bedrock custom model import also works with on-demand use, without any provisioned capacity? I'm still puzzled why they don't offer all qwen3 models on Bedrock by default.
OpenAPI openly encourage users to use their subscription with their SDK and 3rd party tools like opencode, openclaw. Until they change it, they're still better than Anthropic subscription.
It is extreme cope from the Anthropic audience to claim its products and policies have shortcomings only because they are the best and that OpenAI would be as bad as they are if they were the ones in the lead
"OAuth authentication (used with Free, Pro, and Max plans) is intended exclusively for Claude Code and Claude.ai. Using OAuth tokens obtained through Claude Free, Pro, or Max accounts in any other product, tool, or service — including the Agent SDK — is not permitted and constitutes a violation of the Consumer Terms of Service."
reply