solaire_oa

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.

I installed it, I tried the examples, it works.... But forgive my lack of imagination... what is this useful for?

Like, their example is of classification for a support interface.... `refund_requested`. Pretty convenient bool given the example is about a refund- what if 99% of submissions don't ask about a refund? Also, is that user not a `churn_risk`? What could possibly qualify as a churn risk if not a user asking for a refund?

https://ollaya.dev/library/laya The examples suffer the same problem of why I'd prefer to use a string column vs an enum. Changing an enum means you need to update the db, using a string you can do whatever.

I'm not trying to be negative, I genuinely want to know about some practical examples (that don't require tons of backwards maintenance).

It's lame, but a todo list app: jatabag.com

It's tailored toward implementing a web version of the original cli app and whitepaper "grit" https://github.com/climech/grit

So basically it creates a DAG and each task node can receive some annotated data (traits) about whether the task is actionable or not.

I've been using it daily for a year or so. Slight bummer that I feel I released it 5 years overdue, though, and it's doomed to drown in noise.

Pinky-promises, embarrassing. I'd point to tinfoil.sh. I'm not a shill for tinfoil, I haven't even used it or looked past its homepage really, but if we are able to legitimately secure privacy, then training data questions are moot (and the market for training data would probably shift/expose).

Even if Zitron is hopelessly wrong and a complete fool, he's an engaging writer. Like the original article itself states, it's not about the numbers, it's about catharsis. The transparent absence of AI tells in his articles is refreshing, and just rampaging against the AI boosters who lack empathy and self-awareness (which so many of them absolutely do) is cathartic. Even if it's all bunk, fake, and stupid, it's nice to have a way to self-soothe and manifest how much some of us want AI to have a reckoning.

Does that make his readers suckers? Possibly. But personally I also think it's a very human trait to seek comfort.

Yeah. Maybe to add to that: I like my current job, and I consider myself a steward of the codebases that I'm a stakeholder in (I want it to be good).

There's little space for stewardship when LLMs induce psychosis and learned-carelessness in peers, so even though I'm here, I'm still motivated, and I'm still trying to stop crappy software (usually in code review), it feels like it is going to be a losing battle in the long run. The point being that "so little stability" with respect to financial stability may not necessarily factor- stability is threatened from all angles (code, motivation, fatigue, identity, etc).

I generally agree that software has been getting worse, and AI isn't the cause, necessarily, but certainly is accelerating the decay.

Maybe a corollary to the growth of programmers is that pride/artisanship in the work decreases. Bugs happen more when the engineers dgaf, or aren't as dedicated to the craft. Software was pretty solid when I was a teenager (I'm thinking Windows, MSN Messenger, Flash, CDs, general web usage), complaints about tech/bugs weren't as common (or when they did happen, they were major, like BSOD). But I could just be romanticizing the past... idk.

In any case, say we were master woodworkers and we took pride in handcrafting great beds, but now the machines can make beds 150% faster at a 70% defect rate. There's 3 new problems: 1 is obviously that 30% of beds are shit, 2 is that woodworking as an industry is on the decline (expertise vacuum), and 3 is that the master woodworkers are disillusioned, their motivation and utility is decreased.

I believe that in time, the beds will get better, sure (the machines will improve). But in the meantime, huge numbers of people get shit sleep.

I'd be interested in seeing your prompts, out of curiosity.

Either way I had a good laugh when I realized it wasn't going to end and getting the coins/tokens was pointless.

For a period of time, I was graphing HN AI sentiment on BULL/BEAR LOVE/HATE axes.

https://r5d.me/vibeschism/

The mania and lament continues at full speed, I suppose. And related to the brazen contempt for consent:

https://r5d.me/robots.txt

I like the article's sentiment, but a do-over sounds... unrealistic. Sadly, this is very common with the lamentation links, where the article accurately describes the problems at hand, but is alack of actionable advice.

Bubble stress test, stage 1.

Not all prompts require the same compute, and Gemma-4B runs on our phones with parity output for ordinary 1-5 sentence queries. The common use case of Google-style queries is already solved locally, saying we're miles off is ridiculous.

Yeah this is context poisoning, not model poisoning, which is way, way more effective.

Google and Reddit have contracts: Google has official scraping access to Reddit (probably more than that at this point since the contracts were signed 1-2 years ago). But the fact that Reddit does a good job at moderating human content makes it a boon for plausibly "up-to-date" info (which a model doesn't have). Google's LLM summaries even include Reddit as its foremost "citations".

Anyway, Google does a RAG or something similar for its LLM responses, and takes Reddit info at face value. I'm very interested to see what the "thresholds" are, like how much context poisoning do you need to be effective. If the above link is reliable then the answer is "mere sentences".

Certainly bad-actor merchants would try this sort of thing on merchandise subreddits; welcome to the new AIO/GEO everyone.

If you're implying that it's a violation of the original hacker ethos, I disagree.

"Information wants to be free" is a small part of the hacker ethos venn diagram. There are many hacker ethos traits that aren't about cracking, specifically.

Also, the server "information" isn't free (as in beer) to begin with, it costs server availability. Coming up ways to penalize greedy actors is not only well within the server operator's perogative, it's an interesting tit-for-tat problem that could pique any hacker's interests.

A bonus hacker trait is that these poisoning responses are individualistic, i.e. the government doesn't get involved, where certainly more aggressive anti-AI sentiments could (wrongly) call for that.

So I'd say this type of LLM-resistance falls squarely in the original hacker ethos, even though it incidentally counteracts one minor aspect of "information availability". Though I'd certainly agree that the picture today is a lot different than it was. Ironic even.

As far as I'm aware, "source of truth" refers to data/code that drives the actual app, so Figma could never be a source of truth (Figma is a reference of what the app data/code is supposed to do). Saying Figma is a source of truth is like saying JIRA is a source of truth, which doesn't make any sense.

Pretty cool to see stacks being given due attention. Also check out git-spice, which works with Gitlab (possibly others). Personally I use git-spice in place of all the conventional git commands.

I got to the second section before I decided to scan how long it was, saw a wall of text, and decided that this article was low taste.

Moreover, the submitter of this article (probably not the author) spams ~4 submissions per day.

I'm not sure I believe them though, at face value anyway. Or at least, I would suspect the entire spectrum of levels 0-9 are constantly at play at Anthropic (or any sizeable company). Fully disavowing the code as a matter of policy seems needlessly reckless.

(Thanks for visidata btw, awesome tool that helped me with a side project not long ago.)

I can confirm that tool calls failed for me (Ubuntu server with charmbracelet/crush, if that matters)

I know that it's discourteous to write-off a potentially valuable project because the release post showed a lack of self-awareness, but I think it's indicative of the larger struggle taking place: that trust is decaying.

It's decaying for a lot of the reasons displayed in the post, like you described, but the post also:

  - is overlong (probably LLM assisted)
  - is self-congratulatory
  - boosts AI
  - rewrites an existing project (vs contributing to the original)
  - conjures long-term maintenance doubt/suspicions
  - is functionally an advertisement (for CloudFlare)

So yeah, maybe EmDash is revolutionary with respect to Wordpress, but it hasn't signaled trust, and that's a difficult hurdle to get past.

> However, our recent analysis found over 90 times more malware from sideloaded sources than on Google Play

https://android-developers.googleblog.com/2025/08/elevating-...

> The scale of this threat is significant: our recent analysis found over 50 times more malware from internet-sideloaded sources than on apps available through Google Play

Bald face lies are getting baldier.

This is good info, thanks. Can I ask how you detected that version of axios? I checked the source (from another comment) and the package.json dependencies are empty....

I couldn't tell from the title whether is was client or the server code (although map file and NPM were hints). Looks like the client code, which is not as exciting.