Unless you’re somehow on a different quota system, or maybe using Haiku, there’s no way you can sustain five continuous hours of parallel agents running without hitting the 5h quota limit, even on the 20x max plan. But maybe your company is flagged as VIP or something.
Yes, it’s extremely obvious. The recent “we give you $100/$200 extra credit for a month” is clearly just “you’re supposed to pay extra for the same usage from the now on” dressed up as a “bonus”, just like giving “bonus” usage off-peak before announcing faster burn rate during peak a short while ago.
And the recent “Investigating usage limits hitting faster than expected” [1] is probably them intentionally gauging how much they can push it without too much of an uproar.
> Adding to the awkwardness: Sim.ai was actually a Delve customer, Karabeg told TechCrunch. Both startups were grads of the startup accelerator Y Combinator, and Y Combinator alumni frequently buy each other’s products. So while Sim.ai paid Delve, Delve did not do the same for Sim.ai.
So it’s not all it takes.
<s>Cheating</s> sorry hustling and <s>bullshitting</s> sorry storytelling are more important.
These are web accessible resources, e.g. images and stylesheets you can reference in generated HTML. Since content scripts operate directly on the same DOM, it’s unclear how you can tell an <img> or <link> came from the modification of a content script or a first party script. You might argue it’s possible to block these in fetch(), but then you also need to consider leaks in say Image’s load event.
This behavior has been improved in MV3, with option to make the extension id dynamic to defeat detection:
> Note: In Chrome in Manifest V2, an extension's ID is fixed. When a resource is listed in web_accessible_resources, it is accessible as chrome-extension://<your-extension-id>/<path/to/resource>. In Manifest V3, Chrome can use a dynamic URL by setting use_dynamic_url to true.
Any project with Claude’s signature misaligned ASCII diagram just screams DON’T USE to me. If you can’t even bother to read your damn generated README, how do I know you have QC’ed anything else? At the very least supported features claimed in README / on website could be totally fake, which is extremely common among all the vibed Show HNs.
I love how a comment pointing out glaring lack of human review of this project (with clear evidence) is flagged to death. With zero counter-argument no less. Can’t wait for the bright future of vibed crap with zero human quality control getting hacked every day.
To be that guy for a moment: those are not ASCII as those characters are not in the standard 7-bit ASCII set. The closest you get to rounded corners with just ASCII is something like:
/-----\ .-----.
| bah | or | bah | (the latter usually looks best IMO, but that can depend on font)
\-----/ `-----'
You'd get away with calling the linked diagram ANSI. While that is technically incorrect most people accept the term for something that uses one of the common 8-bit character sets that include those box-drawing characters (CP437, CP850, ISO-8859, Win1252, …), because that is what MS has for a long time called Win1252 in its tools.
> is already a red flag
I wouldn't call using box-drawing characters a red flag, I've known people use them this way for years and do so myself. The LLM generates them because they were in its training data because people use them. It might be something to consider amongst other flags but I don't consider it a strong signal on its own. The red flag for me is the alignment - if you are going to have your documentation ghostwritten at least make the effort to do a cursory editing pass afterwards.
My visceral AI disgust response here is just a subset of my more general lazyly-slapped-together-without-sufficient-testing-or-other-review disgust response. If it doesn't look bad in that way, whether hand-made or ghostwritten, then I'll not react to it that way. But if someone can't be bothered to do a simple clean-up pass on that documentation, what mess could they have left in the code too?
As far as I'm concerned the social contract (“the rules”) has already been broken by people taking insufficient care, and my reaction to that is a healthy one from the PoV of self-preservation. Acting in good faith works both ways, or it doesn't.
>Acting in good faith works both ways, or it doesn't.
Well said, polluting hacker news with low effort slop for self promotion cannot be good faith.
The rules are enforced on commenters but good faith is not expected for submissions somehow
That “balanced take” severely mischaracterizes dissenting expert Camarda’s attitude, so it’s not balanced at all. Its answer to “Could the NASA engineers convince Olivas and Camarda?” is a “maybe” for Camarda, which couldn’t be further from what Camarda had to say himself, which is he was more concerned after the meeting than before.
From Camarda’s own account after the meeting:
> Hold a “transparent” meeting with invited press to “vet” the Artemis II decision with one of the most public technical dissenters, me, in attendance (Jan 8th, 2026).
> Control the one-sided narrative and bombard the attendees with the Artemis Program view
> Do not allow dissenting voices to present at the meeting
> Do not even allow the IRT or the NESC to present their findings
> Rely on the attending journalists to regurgitate the party line and witness the overwhelming consensus of knowledgeable people
You’re pointing to something entirely different: those are Copilot-created PRs. They can include anything Copilot wants to include. People using the Copilot PR feature know what they’re buying into.
OP is about Copilot doing post-hoc editing of a human-created PR to include an ad, allegedly without knowledge or approval of the creator (well I assume they did give their team member permission to update the PR body, but apparently not for this kind of crap).
reply