frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Indian Culture

https://indianculture.gov.in/
1•saikatsg•40s ago•0 comments

Show HN: Maravel-Framework 10.61 prevents circular dependency

https://marius-ciclistu.medium.com/maravel-framework-10-61-0-prevents-circular-dependency-cdb5d25...
1•marius-ciclistu•56s ago•0 comments

The age of a treacherous, falling dollar

https://www.economist.com/leaders/2026/02/05/the-age-of-a-treacherous-falling-dollar
1•stopbulying•58s ago•0 comments

Ask HN: AI Generated Diagrams

1•voidhorse•3m ago•0 comments

Microsoft Account bugs locked me out of Notepad – are Thin Clients ruining PCs?

https://www.windowscentral.com/microsoft/windows-11/windows-locked-me-out-of-notepad-is-the-thin-...
1•josephcsible•4m ago•0 comments

Show HN: A delightful Mac app to vibe code beautiful iOS apps

https://milq.ai/hacker-news
1•jdjuwadi•6m ago•2 comments

Show HN: Gemini Station – A local Chrome extension to organize AI chats

https://github.com/rajeshkumarblr/gemini_station
1•rajeshkumar_dev•7m ago•0 comments

Welfare states build financial markets through social policy design

https://theloop.ecpr.eu/its-not-finance-its-your-pensions/
2•kome•10m ago•0 comments

Market orientation and national homicide rates

https://onlinelibrary.wiley.com/doi/10.1111/1745-9125.70023
3•PaulHoule•11m ago•0 comments

California urges people avoid wild mushrooms after 4 deaths, 3 liver transplants

https://www.cbsnews.com/news/california-death-cap-mushrooms-poisonings-liver-transplants/
1•rolph•11m ago•0 comments

Matthew Shulman, co-creator of Intellisense, died 2019 March 22

https://www.capenews.net/falmouth/obituaries/matthew-a-shulman/article_33af6330-4f52-5f69-a9ff-58...
3•canucker2016•12m ago•1 comments

Show HN: SuperLocalMemory – AI memory that stays on your machine, forever free

https://github.com/varun369/SuperLocalMemoryV2
1•varunpratap369•13m ago•0 comments

Show HN: Pyrig – One command to set up a production-ready Python project

https://github.com/Winipedia/pyrig
1•Winipedia•16m ago•0 comments

Fast Response or Silence: Conversation Persistence in an AI-Agent Social Network [pdf]

https://github.com/AysajanE/moltbook-persistence/blob/main/paper/main.pdf
1•EagleEdge•16m ago•0 comments

C and C++ dependencies: don't dream it, be it

https://nibblestew.blogspot.com/2026/02/c-and-c-dependencies-dont-dream-it-be-it.html
1•ingve•16m ago•0 comments

Show HN: Vbuckets – Infinite virtual S3 buckets

https://github.com/danthegoodman1/vbuckets
1•dangoodmanUT•16m ago•0 comments

Open Molten Claw: Post-Eval as a Service

https://idiallo.com/blog/open-molten-claw
1•watchful_moose•17m ago•0 comments

New York Budget Bill Mandates File Scans for 3D Printers

https://reclaimthenet.org/new-york-3d-printer-law-mandates-firearm-file-blocking
2•bilsbie•18m ago•1 comments

The End of Software as a Business?

https://www.thatwastheweek.com/p/ai-is-growing-up-its-ceos-arent
1•kteare•19m ago•0 comments

Exploring 1,400 reusable skills for AI coding tools

https://ai-devkit.com/skills/
1•hoangnnguyen•20m ago•0 comments

Show HN: A unique twist on Tetris and block puzzle

https://playdropstack.com/
1•lastodyssey•23m ago•1 comments

The logs I never read

https://pydantic.dev/articles/the-logs-i-never-read
1•nojito•24m ago•0 comments

How to use AI with expressive writing without generating AI slop

https://idratherbewriting.com/blog/bakhtin-collapse-ai-expressive-writing
1•cnunciato•25m ago•0 comments

Show HN: LinkScope – Real-Time UART Analyzer Using ESP32-S3 and PC GUI

https://github.com/choihimchan/linkscope-bpu-uart-analyzer
1•octablock•26m ago•0 comments

Cppsp v1.4.5–custom pattern-driven, nested, namespace-scoped templates

https://github.com/user19870/cppsp
1•user19870•27m ago•1 comments

The next frontier in weight-loss drugs: one-time gene therapy

https://www.washingtonpost.com/health/2026/01/24/fractyl-glp1-gene-therapy/
2•bookofjoe•30m ago•1 comments

At Age 25, Wikipedia Refuses to Evolve

https://spectrum.ieee.org/wikipedia-at-25
2•asdefghyk•32m ago•4 comments

Show HN: ReviewReact – AI review responses inside Google Maps ($19/mo)

https://reviewreact.com
2•sara_builds•33m ago•1 comments

Why AlphaTensor Failed at 3x3 Matrix Multiplication: The Anchor Barrier

https://zenodo.org/records/18514533
1•DarenWatson•34m ago•0 comments

Ask HN: How much of your token use is fixing the bugs Claude Code causes?

1•laurex•37m ago•0 comments
Open in hackernews

Show HN: Yikes imagine trusting Google's documentation

https://usesnippet.app/demo/result
11•aa_y_ush•3mo ago
I built Snippet: an auto-updating truth layer for your organization's knowledge.

Comments

rathinshah•3mo ago
Thisis really good. I wonder if these "truths" propagate anywhere or not.
aa_y_ush•3mo ago
thanks! yes, we enable auto updating documentation, automatic conflict resolution, and accurate search indexing.
mtyagi•3mo ago
Makes sense now why integrations sometimes break unexpectedly. Conflicting info in official docs is a real problem
aa_y_ush•3mo ago
have you seen a similar situation before?
mtyagi•3mo ago
Seen it a lot in enterprise environments. Teams maintain parallel Confluence spaces and internal API docs. They drift constantly. The newer page is correct, but search still surfaces the old one first
ayushman_gupta_•3mo ago
Love the concept. Just curious if and how you guys determine which source is correct in case of a conflict
aa_y_ush•3mo ago
We do! An org can define precedence rules, but the engine looks at things like recency, authority, majority voting etc. We also flag criticality to raise manual reviews when needed.
yash_5339•3mo ago
This definitely solves a good problem. Company don’t keep generally good confluence docs and documentation. Somehow if there is common source of truth it helps to entire org in a company. But I was wandering if it will be helpful or not for external world because I feel companies usually double check any information before releasing it publicly ..especially related to code base.(Just a thought).
Portoaj•3mo ago
Totally agree - we've found a handful of conflicts on every large company whose public docs we've looked at but a lot of the value is definitely in internal docs where there's no technical writer double checking everything that comes out.
SchmitzAndrew•3mo ago
would be cool to extend this to enable auto-creating a pr to update a docs repo!
aa_y_ush•3mo ago
Hey Andrew, that is a 100% in play.
wibbily•3mo ago
Huh? The first "conflict" you list isn't a conflict.

> The snippet from "search docs crawling indexing pause online business" states that adding a Disallow: / rule for Googlebot in robots.txt will keep Googlebot away permanently as long as the rule remains. "search help office hours 2023 june", however, advises against disallowing all crawling via robots.txt, warning that such a file "may remove the website's content, and potentially its URLs, from Google Search." This directly contradicts the claim that a full-disallow rule safely blocks Googlebot without negative consequences, creating a true conflict about the effect and advisability of using a disallow rule to block Googlebot.

If you want to block Googlebot "permanently", why would you expect to stay listed in Search? The first page actually agrees with the second - if you only want to temporarily block crawling, it recommends not blocking Googlebot.

Actually, your last "conflict" is bad too. A 503 fetching robots.txt does stop crawling the site, for at least twelve hours and possibly forever (if other pages return errors). The only crawling Google will continue to do is to keep trying to fetch robots.txt.

I appreciate what you're trying to set up here but 2/4 is a pretty bad record for a demo.

Portoaj•3mo ago
Hi wibbily, your point on the first conflicts is fair enough, we'll update that.

I somewhat disagree with you on the last conflict: you have one document stating pretty clearly that returning a 503 for the robots.txt "blocks all crawling". The other document states there's a 12 hour block after which Google may decide to crawl the other pages (not just the robots.txt like you said).

Thanks for the feedback though, definitely some work to be done on validating the conflicts we surface.

notyawn•3mo ago
Love the idea. Detecting when company truths differ between tools is a tricky technical problem, especially when the wording could differ between each tool.
aa_y_ush•3mo ago
Oh thank you!
Abhinit•3mo ago
Great concept! Worth trying :)
rathinshah•3mo ago
thanks a ton!