frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: I built a toy compiler as a young dev

https://vire-lang.web.app
1•xeouz•33s ago•0 comments

You don't need Mac mini to run OpenClaw

https://runclaw.sh
1•rutagandasalim•1m ago•0 comments

Learning to Reason in 13 Parameters

https://arxiv.org/abs/2602.04118
1•nicholascarolan•3m ago•0 comments

Convergent Discovery of Critical Phenomena Mathematics Across Disciplines

https://arxiv.org/abs/2601.22389
1•energyscholar•3m ago•1 comments

Ask HN: Will GPU and RAM prices ever go down?

1•alentred•3m ago•0 comments

From hunger to luxury: The story behind the most expensive rice (2025)

https://www.cnn.com/travel/japan-expensive-rice-kinmemai-premium-intl-hnk-dst
1•mooreds•4m ago•0 comments

Substack makes money from hosting Nazi newsletters

https://www.theguardian.com/media/2026/feb/07/revealed-how-substack-makes-money-from-hosting-nazi...
4•mindracer•5m ago•1 comments

A New Crypto Winter Is Here and Even the Biggest Bulls Aren't Certain Why

https://www.wsj.com/finance/currencies/a-new-crypto-winter-is-here-and-even-the-biggest-bulls-are...
1•thm•5m ago•0 comments

Moltbook was peak AI theater

https://www.technologyreview.com/2026/02/06/1132448/moltbook-was-peak-ai-theater/
1•Brajeshwar•6m ago•0 comments

Why Claude Cowork is a math problem Indian IT can't solve

https://restofworld.org/2026/indian-it-ai-stock-crash-claude-cowork/
1•Brajeshwar•6m ago•0 comments

Show HN: Built an space travel calculator with vanilla JavaScript v2

https://www.cosmicodometer.space/
2•captainnemo729•6m ago•0 comments

Why a 175-Year-Old Glassmaker Is Suddenly an AI Superstar

https://www.wsj.com/tech/corning-fiber-optics-ai-e045ba3b
1•Brajeshwar•6m ago•0 comments

Micro-Front Ends in 2026: Architecture Win or Enterprise Tax?

https://iocombats.com/blogs/micro-frontends-in-2026
1•ghazikhan205•9m ago•0 comments

These White-Collar Workers Actually Made the Switch to a Trade

https://www.wsj.com/lifestyle/careers/white-collar-mid-career-trades-caca4b5f
1•impish9208•9m ago•1 comments

The Wonder Drug That's Plaguing Sports

https://www.nytimes.com/2026/02/02/us/ostarine-olympics-doping.html
1•mooreds•10m ago•0 comments

Show HN: Which chef knife steels are good? Data from 540 Reddit tread

https://new.knife.day/blog/reddit-steel-sentiment-analysis
1•p-s-v•10m ago•0 comments

Federated Credential Management (FedCM)

https://ciamweekly.substack.com/p/federated-credential-management-fedcm
1•mooreds•10m ago•0 comments

Token-to-Credit Conversion: Avoiding Floating-Point Errors in AI Billing Systems

https://app.writtte.com/read/kZ8Kj6R
1•lasgawe•10m ago•1 comments

The Story of Heroku (2022)

https://leerob.com/heroku
1•tosh•11m ago•0 comments

Obey the Testing Goat

https://www.obeythetestinggoat.com/
1•mkl95•11m ago•0 comments

Claude Opus 4.6 extends LLM pareto frontier

https://michaelshi.me/pareto/
1•mikeshi42•12m ago•0 comments

Brute Force Colors (2022)

https://arnaud-carre.github.io/2022-12-30-amiga-ham/
1•erickhill•15m ago•0 comments

Google Translate apparently vulnerable to prompt injection

https://www.lesswrong.com/posts/tAh2keDNEEHMXvLvz/prompt-injection-in-google-translate-reveals-ba...
1•julkali•15m ago•0 comments

(Bsky thread) "This turns the maintainer into an unwitting vibe coder"

https://bsky.app/profile/fullmoon.id/post/3meadfaulhk2s
1•todsacerdoti•16m ago•0 comments

Software development is undergoing a Renaissance in front of our eyes

https://twitter.com/gdb/status/2019566641491963946
1•tosh•16m ago•0 comments

Can you beat ensloppification? I made a quiz for Wikipedia's Signs of AI Writing

https://tryward.app/aiquiz
1•bennydog224•17m ago•1 comments

Spec-Driven Design with Kiro: Lessons from Seddle

https://medium.com/@dustin_44710/spec-driven-design-with-kiro-lessons-from-seddle-9320ef18a61f
1•nslog•17m ago•0 comments

Agents need good developer experience too

https://modal.com/blog/agents-devex
1•birdculture•19m ago•0 comments

The Dark Factory

https://twitter.com/i/status/2020161285376082326
1•Ozzie_osman•19m ago•0 comments

Free data transfer out to internet when moving out of AWS (2024)

https://aws.amazon.com/blogs/aws/free-data-transfer-out-to-internet-when-moving-out-of-aws/
1•tosh•20m ago•0 comments
Open in hackernews

AI SlopStop by Kagi

https://help.kagi.com/kagi/features/slopstop.html
46•janandonly•2w ago

Comments

chrisjj•2w ago
The section What is considered “Slop"? conspiciously fails to answer this question. It simply describes the recognition of material as "AI-generated".

From SlopStop is Kagi’s community-driven feature for reporting low-quality, mass‑generated AI content (“AI slop”) found in web, image and video search results. one might conclude slop is low-quality, mass‑generated content, but why limit opposition to the subset that's from "AI"?

JohnFen•2w ago
> It simply describes the recognition of material as "AI-generated".

That works as a good definition for me. Whether or not you want to call it "slop", anything that helps to filter out AI-generated stuff could be helpful.

My only concern about this is that it seems to rely on user reporting, and if that reporting includes (mistakenly or otherwise) sites that don't have AI generated content, that could make the tool less useful.

chrisjj•2w ago
Further info here https://blog.kagi.com/slopstop indicates a key attribute is "deceptive".

I can see this being weaponised against controversial sites made by humans, with no way to prove they are human.

yunruse•2w ago
Reports being weaponised is a big issue with asymmetric (report-only) systems, but at least here there seems to be a “report as not slop” button.

“Symmetric” user reporting is dearly needed in some websites; as you say something can be mass-reported with no real recourse.

parliament32•2w ago
It's correct. Anything "AI-generated" is slop in my eyes, and I'm not interested in it.
clickety_clack•2w ago
If I wanted to read what ChatGPT would tell me about a subject, I would have been on ChatGPT.
striking•2w ago
> If the page is AI‑generated but the domain is mixed (not mostly AI), we flag the page as AI‑generated but do not downrank it.

> If a domain is found to be mostly AI‑generated (typically more than 80% across its pages), that domain is flagged as AI slop and downranked in web search results.

I think that's pretty clear, no? One AI item is merely AI generated, a trough of AI items is AI slop.

Edited as I think I misunderstood: there's more slop of the AI kind than of whatever other low-effort content, and I think Kagi is already doing a good job of keeping a neat little index that avoids content farms, AI or otherwise. AI slop just happens to be a little harder to evaluate than regular slop (and in my experience is now more pervasive because it's cheaper to produce).

falloutx•2w ago
There may be low quality human slop but AI-slop is the most common slop on the internet.
ChrisArchitect•2w ago
Previous discussion on the blog post: https://blog.kagi.com/slopstop (https://news.ycombinator.com/item?id=45919067)
unsignedint•2w ago
I think this really needs to be framed as a "report low-quality content" feature, not a "report AI slop" feature. Otherwise, it just incentivizes people to hide their process, and it risks turning into a witch hunt where everything gets judged on whether it "looks AI" rather than whether it’s actually bad content.
blazarquasar•2w ago
I would disagree. I would never activate a feature that down-ranks or hides results based on some ominous judgement on quality by a Kagi team. For AI Slop its pretty easy to determine because it is always lows quality and useless content that provides zero value and is a waste of time. The guidelines as specified also allow for some margin or error here I would argue.
unsignedint•2w ago
Just my take: I don’t think “AI” automatically equals “slop.” There’s plenty of human-made slop too, and some AI-assisted content is genuinely useful. I’d rather see this framed as “report low-value/spammy content” than “report AI slop,” since the AI label tends to turn into “this looks AI” witch-hunting. That said, our baseline assumptions seem pretty different here, so we probably won’t fully agree.
dooglius•2w ago
Current status:

> SlopStop is getting ready! Report processing has not started yet at-scale. We are reviewing the initial wave of reports, and finalizing our systems for handling them.

> We will start processing reports officially in January. Please continue submitting reports as you find more content!