solaire_oa

The more things change, the more they stay the same.

Is HN upvoting just because they agree with the title?

Clearly the "author" didn't even put in the effort necessary to make a real title. Not "SRE persists but a skill crisis looms" not "SRE careers remain but competency lowers in spite of AI" not "AI lowers SRE skill but demand is steady". Moreover, hasn't this type of insufferability been dramatically reduced in recent models? It screams that in addition to being slop, it's outdated.

Why would anyone take this at face value?

I think this is a better analogy, particularly because it illustrates that the more demanding company might not need to be 10x more efficient. A company that opts to to be lighter/cheaper may lose to the competitor regardless, especially in winner-take-all or discerning markets. Maybe not always, and we're obviously speaking theoretically, but it's an interesting thought.

I use a combination of Hacker Smacker (seems roughly the same idea), and TrustSpark for HN, which I also vibed (pre-Opus, probably could be improved at this point).

Hacker Smacker in particular would be awesome if more users picked it up (since it's a web of trust, albeit 1 hop only).

The submitter posts approximately 5 articles per day, has relatively low comment engagement per submission, and the account was created in 2023, for what that's worth. Low trust.

I vibed TrustSpark for HN plugin some months ago, and I get true positive flags from this account all the time. Unfortunately my RSS feed doesn't see the flags, and I have to click the link to find out.

Anthropic plausibly uses Brave Search... and Brave search maintains its own index. Makes sense: cheaper search API, leveraging non-Google, etc.

Here we are, one layer of indirection more: Ceramic, Exa, Linkup. Who knows what they use. If you told me that those 3 build and maintain their own index, I'd first question whether that was true, and if it is, I would question whether it was any good (relative to Google/Bing/Brave).

So what is CF providing here? Maybe some free credits to entice us to use their router? No, not that either ("billed to your AI Gateway credits"). Maybe a comparison of which agent search yields the best results? Nope.

It's a crappy proxy- probably less efficient and more volatile than hitting the agent API directly.

This is only if I understand the product correctly (which I admittedly skimmed) due to the sheer number of screeching vibey nothingburgers coming out of CF over the past month.

I also run Qwen3.8 Flash Next "locally at home", on a Framework Desktop, so Strix Halo and 128GB... we're not talking laptops, exactly, if that's what you wanted to know.

Still, the halogen version only occupies < 40GB RAM on my machine (which is surprising... the Q4 takes over 100GB), so perhaps a 64GB version is on the table.

I coincidentally just installed this (like 30 minutes ago), and gud dayum, it's pretty awesome.

I say this is awesome, even as I glossed over the README and vomited in my mouth. The halogen repo looks like the same utter AI bullshit littering GitHub. But this one delivers, in spite of it's slop-riddled hallmarks.

In any case, yeah, ~55 tok/s on a high quality model (and massive RAM savings I think?), seems dope.

Does the Internet have a trust problem? What the slop suggests...

This is the 7th submission on HN in the last week which has entered my RSS feed, which has AI-tell slop right in the title. It's really discouraging.

It has some jargon hallmarks, which I noticed, but vibed or not, it's a massive improvement on other repos. Maybe it's because it's only a few commits so far... perhaps if you were to vibe 100 more commits it would devolve. Or maybe 5.5 really did improve (doubt it, still sounds like an asshole for me). But idk.

I still think that `churn_risk` above is incorrect and unacceptable (perhaps there are sensible fixes, but saying "no churn risk" about a refund, in a leading example on their homepage, flabbergasting).

But if that were solved, I could see giving ollaya/grev to LLMs themselves, giving LLMs their own massive token-saver.

Ok, those are pretty decent examples, and clears up the utility a bit: speed and tokens. Some of it's still a bit iffy (e.g. `cutv 'email address' 'phone number' < examples/users.csv`, csv is already in columns), but I can see using it for some niche queries. Neat tool.

I very much appreciate your to-the-point, non-vibed README as well, ty for that.