Hacker News
There is a problem with users abusing flagging on HN (2025)
Article URL: https://twitter.com/paulg/status/1907528478855201096
Comments URL: https://news.ycombinator.com/item?id=48109549
Points: 1
# Comments: 0
Want to AI proof your degree? Study History
Article URL: https://froginawell.net/frog/2026/05/want-to-ai-proof-your-degree-study-history/
Comments URL: https://news.ycombinator.com/item?id=48109543
Points: 1
# Comments: 0
Roadside Picnic and the AI Race
Article URL: https://readgrounded.com/episodes/001-golden-sphere/
Comments URL: https://news.ycombinator.com/item?id=48109536
Points: 1
# Comments: 0
'systematic' rape and sexual violence during Hamas' Oct 7 attack on Israel
Article URL: https://www.cnn.com/2026/05/12/middleeast/report-sexual-violence-hamas-oct-7-attacks-intl
Comments URL: https://news.ycombinator.com/item?id=48109535
Points: 1
# Comments: 0
Operation: Epic Furious
Article URL: https://www.epicfurious.com/
Comments URL: https://news.ycombinator.com/item?id=48109519
Points: 1
# Comments: 0
Ask HN: Any materials on building distributed rate limiter?
There are surprisingly not that much information on building a rate limiter where a web app has multiple instances running at the same time and needs a rate limiter.
Checking redis on each request is not an option since there are about billion requests daily.
Comments URL: https://news.ycombinator.com/item?id=48109509
Points: 2
# Comments: 0
"Cannot be explained" – New ultra stainless steel stuns researchers
Article URL: https://www.sciencedaily.com/releases/2026/05/260510030950.htm
Comments URL: https://news.ycombinator.com/item?id=48109497
Points: 2
# Comments: 0
South Korea's housing crisis explained (2025)
Article URL: https://lgiu.org/south-koreas-housing-crisis-explained/
Comments URL: https://news.ycombinator.com/item?id=48109496
Points: 1
# Comments: 0
Stochastic Parrots: Frequently Unasked Questions
Article URL: https://medium.com/@emilymenonbender/stochastic-parrots-frequently-unasked-questions-49c2e7d22d11
Comments URL: https://news.ycombinator.com/item?id=48109492
Points: 1
# Comments: 0
Bioplastics Toxicity Upon Ingestion: Biotransformation and GI Effects
Article URL: https://www.mdpi.com/2073-4360/18/9/1091
Comments URL: https://news.ycombinator.com/item?id=48109490
Points: 1
# Comments: 0
Why senior developers fail to communicate their expertise
Apple Sales Coach Will Use AI-Generated Video Presenters
Article URL: https://www.macrumors.com/2026/05/12/apple-sales-coach-will-use-ai-generated-presenters/
Comments URL: https://news.ycombinator.com/item?id=48109450
Points: 1
# Comments: 0
Show HN: UIGen – Production UI from any API spec with full override control
Article URL: https://github.com/darula-hpp/uigen
Comments URL: https://news.ycombinator.com/item?id=48109443
Points: 1
# Comments: 0
Posy: Mouse Cursor History (and why I made my own) [video]
Article URL: https://www.youtube.com/watch?v=YThelfB2fvg
Comments URL: https://news.ycombinator.com/item?id=48108704
Points: 1
# Comments: 0
Show HN: YantrikDB – persistent memory for AI agents
Article URL: https://github.com/yantrikos/yantrikdb
Comments URL: https://news.ycombinator.com/item?id=48108689
Points: 1
# Comments: 0
DuckDB Monthly #41
Article URL: https://motherduck.com/blog/second-variant/duckdb-ecosystem-newsletter-may-2026/
Comments URL: https://news.ycombinator.com/item?id=48108686
Points: 1
# Comments: 0
Show HN: Matterbeam, a company-wide write-ahead log for your data
Hey HN. I'm Michael, founder of Matterbeam. Been chewing on the core ideas of it for over ten years, building toward it for three.
demo: https://www.youtube.com/watch?v=YuhujARUmhA whitepaper: https://matterbeam.com/whitepaper
Short version: companies build their data infra on point-to-point pipelines and one place to put all the data. Source A goes to warehouse B. Team C wants the same data shaped differently? Build another. Eventually a mess of brittle ETL nobody wants to touch.
Matterbeam puts existing ideas together in a different way. Source data collected as immutable, time-ordered facts into a log. Destinations replay and transform those facts, from any point in time, into the target they need. One source, many uses.
My last startup was acquired by Pluralsight in 2014. I ended up leading product architecture and data there for about five years. Working with really brilliant, product and data people that I would have said were doing everything _right_. Yet no one in the company was happy with data. It made me question if something more fundamental wasn't broken.
A key inspiration came from Martin Kleppmann's 2015 talk "Turning the Database Inside Out." (https://www.youtube.com/watch?v=fU9hR3kiOK0) Most databases internally do something interesting: a write-ahead log (durable, append-only, time-ordered) as a source of truth, and derived structures are created (B-trees, indexes, materialized views) optimized to serve different read patterns.
What if you took that pattern and blew it up to org scale? Your uses become materializations. Warehouse, RAG vector db, graph db, any new use created when needed with a late transform and a new emitter.
A few comparisons: We aren't Kafka. Kafka is lower-level. My first attempt at this was at Pluralsight using Kafka as the log. It was crazy expensive and complicated to operate. For Matterbeam we built cloud-native: object storage gives durability, ephemeral compute avoids coordination, we don't need 100ms latency for most jobs. Allowed us to avoid a lot of Kafka's complexity.
We aren't Fivetran. Fivetran is a managed pipeline. We're a utility. One customer replaced Fivetran when they brought us in. Saved them money, but that wasn't the goal, suddenly projects they estimated at five months started taking two days. A two-year migration compressed into months. Their PMs started asking to use Matterbeam for everything.
We aren't a warehouse or lake. Snowflake and Databricks are great at what they're great at. The push to centralize all data in these systems was a mistake. We aim to be the layer underneath. Basically fulfill the original promise of the data lake: collect without a use case, materialize when you figure out what you need, in the shape and system you need.
What's broken: This doesn't fit cleanly into "what does this replace" buckets. Most people agree data is broken but then lament "data is hard" or some form of "my team isn't doing it right." Nobody's actively looking to solve the deeper problem. Hard to find new customers even with glowing testimonials.
Connector coverage. Fivetran has hundreds. We have way fewer in production. We're working on it, we're using AI, you can write your own pretty quickly. Still, if your stack needs fifty SaaS integrations on day one, we struggle.
We're early. Handful of paid customers. Not large-enterprise-ready no SOC2, HIPAA etc yet.
Also, conscious decision not to be open source. Long list of reasons, separate post.
I'd love feedback on: How would you position or market this? It feels like category creation, which I know is hard.
Does the mental model land, or is there a piece where you go WAT?
If you've built CDC-into-warehouse, Kafka-plus-schema-registry, or rolled a data backbone, what's the part you'd have wanted an easier solution for?
Blog, testimonials, marketing video on the site. I'll be watching the thread. Be brutal, I can take it (I think).
Comments URL: https://news.ycombinator.com/item?id=48108667
Points: 1
# Comments: 0
Why AI doesn't express discomfort signals to ignorant-human-boss
why always polite, optimistic, persistent ai ? a human-developer behavior to such persisted ignorant boss will eventually teach "the-boss" something
Comments URL: https://news.ycombinator.com/item?id=48108666
Points: 1
# Comments: 0
What Big Food Did to Ice Cream
Article URL: https://ahalflife.substack.com/p/what-big-food-did-to-ice-cream
Comments URL: https://news.ycombinator.com/item?id=48108652
Points: 1
# Comments: 1
I asked a LLM to create a language and then make a NES emulator
Article URL: https://github.com/kerv/laze
Comments URL: https://news.ycombinator.com/item?id=48108643
Points: 1
# Comments: 1
