frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

NewASM Virtual Machine

https://github.com/bracesoftware/newasm
1•DEntisT_•1m ago•0 comments

Terminal-Bench 2.0 Leaderboard

https://www.tbench.ai/leaderboard/terminal-bench/2.0
1•tosh•1m ago•0 comments

I vibe coded a BBS bank with a real working ledger

https://mini-ledger.exe.xyz/
1•simonvc•1m ago•1 comments

The Path to Mojo 1.0

https://www.modular.com/blog/the-path-to-mojo-1-0
1•tosh•4m ago•0 comments

Show HN: I'm 75, building an OSS Virtual Protest Protocol for digital activism

https://github.com/voice-of-japan/Virtual-Protest-Protocol/blob/main/README.md
3•sakanakana00•7m ago•0 comments

Show HN: I built Divvy to split restaurant bills from a photo

https://divvyai.app/
3•pieterdy•10m ago•0 comments

Hot Reloading in Rust? Subsecond and Dioxus to the Rescue

https://codethoughts.io/posts/2026-02-07-rust-hot-reloading/
3•Tehnix•10m ago•1 comments

Skim – vibe review your PRs

https://github.com/Haizzz/skim
2•haizzz•12m ago•1 comments

Show HN: Open-source AI assistant for interview reasoning

https://github.com/evinjohnn/natively-cluely-ai-assistant
3•Nive11•12m ago•4 comments

Tech Edge: A Living Playbook for America's Technology Long Game

https://csis-website-prod.s3.amazonaws.com/s3fs-public/2026-01/260120_EST_Tech_Edge_0.pdf?Version...
2•hunglee2•16m ago•0 comments

Golden Cross vs. Death Cross: Crypto Trading Guide

https://chartscout.io/golden-cross-vs-death-cross-crypto-trading-guide
2•chartscout•18m ago•0 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
3•AlexeyBrin•21m ago•0 comments

What the longevity experts don't tell you

https://machielreyneke.com/blog/longevity-lessons/
2•machielrey•23m ago•1 comments

Monzo wrongly denied refunds to fraud and scam victims

https://www.theguardian.com/money/2026/feb/07/monzo-natwest-hsbc-refunds-fraud-scam-fos-ombudsman
3•tablets•27m ago•1 comments

They were drawn to Korea with dreams of K-pop stardom – but then let down

https://www.bbc.com/news/articles/cvgnq9rwyqno
2•breve•30m ago•0 comments

Show HN: AI-Powered Merchant Intelligence

https://nodee.co
1•jjkirsch•32m ago•0 comments

Bash parallel tasks and error handling

https://github.com/themattrix/bash-concurrent
2•pastage•32m ago•0 comments

Let's compile Quake like it's 1997

https://fabiensanglard.net/compile_like_1997/index.html
2•billiob•33m ago•0 comments

Reverse Engineering Medium.com's Editor: How Copy, Paste, and Images Work

https://app.writtte.com/read/gP0H6W5
2•birdculture•38m ago•0 comments

Go 1.22, SQLite, and Next.js: The "Boring" Back End

https://mohammedeabdelaziz.github.io/articles/go-next-pt-2
1•mohammede•44m ago•0 comments

Laibach the Whistleblowers [video]

https://www.youtube.com/watch?v=c6Mx2mxpaCY
1•KnuthIsGod•45m ago•1 comments

Slop News - The Front Page right now but it's only Slop

https://slop-news.pages.dev/slop-news
1•keepamovin•50m ago•1 comments

Economists vs. Technologists on AI

https://ideasindevelopment.substack.com/p/economists-vs-technologists-on-ai
1•econlmics•52m ago•0 comments

Life at the Edge

https://asadk.com/p/edge
4•tosh•58m ago•0 comments

RISC-V Vector Primer

https://github.com/simplex-micro/riscv-vector-primer/blob/main/index.md
4•oxxoxoxooo•1h ago•1 comments

Show HN: Invoxo – Invoicing with automatic EU VAT for cross-border services

2•InvoxoEU•1h ago•0 comments

A Tale of Two Standards, POSIX and Win32 (2005)

https://www.samba.org/samba/news/articles/low_point/tale_two_stds_os2.html
4•goranmoomin•1h ago•0 comments

Ask HN: Is the Downfall of SaaS Started?

4•throwaw12•1h ago•0 comments

Flirt: The Native Backend

https://blog.buenzli.dev/flirt-native-backend/
3•senekor•1h ago•0 comments

OpenAI's Latest Platform Targets Enterprise Customers

https://aibusiness.com/agentic-ai/openai-s-latest-platform-targets-enterprise-customers
2•myk-e•1h 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!