frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: AiTz – A universal gateway for discovering AI tools

https://aitz.site
1•muktari_dev•4m ago•0 comments

HyperThink: Text-to-Parameter Hypernetworks for Efficient Reasoning

https://hyperthink-llm.github.io/
1•nnx•9m ago•0 comments

Tesla's $30k Cybercab comes with a $299 monthly catch

https://www.wired.com/story/tesla-cybercab-is-the-subscription-hell-they-told-you-not-to-worry-ab...
1•nobody9999•12m ago•0 comments

Jujutsu Primer

https://ethanlowman.com/posts/jj-primer/
1•renehsz•13m ago•0 comments

Google threatens OEMs to not work with GrapheneOS

https://grapheneos.social/@GrapheneOS/117645917131936200
3•drewfax•14m ago•0 comments

Show HN: SoundBench – AI vocal remover and audio tools that run in the browser

https://soundbench.net/
1•btccit•15m ago•1 comments

Show HN: Light Sleep – Sounds that settle the night

https://nonloop.github.io/lightsleep/
1•lucakk•15m ago•0 comments

Humans.md: tell your AI agents how to work with you

https://humansmd.dev/
1•furkanonder•16m ago•0 comments

Tufazip: Tufa Labs Squeezes 1 GB of Wikipedia into 105.39 MB with a Transformer

https://explainx.ai/blog/tufazip-tufa-labs-neural-text-compressor-enwik9-105-39-mb-large-text-com...
1•peter_d_sherman•17m ago•0 comments

Show HN: Mergepond – a Mac Git client for worktrees and coding agents

https://mergepond.dev
1•riley-wv•19m ago•0 comments

The Desktop Metaphor is Dead (2025)

https://rusz.space/posts/os/
1•zenincognito•21m ago•0 comments

RPEG: Training Reasoning Language Models Scalably and Cost-Effectively

https://arxiv.org/abs/2611.09207
1•matt_d•24m ago•0 comments

Moats in the Age of Floods

https://twitter.com/nayakkayak/status/2092276375935963537
1•gmays•27m ago•0 comments

Woman uses monkeys as outlets for her hatred of babies and pregnant women

https://www.bbc.com/news/uk-england-hereford-worcester-68968718
1•illidan1000•27m ago•0 comments

Who Is Work For?

https://golikehellmachine.com/ephemera/who-is-work-for/
2•toomuchtodo•28m ago•0 comments

The 50-Yard Line

https://daringfireball.net/2026/11/the_50-yard_line
1•JumpCrisscross•30m ago•0 comments

Aptera Completes First Customer Solar EV

https://aptera.us/first-vehicle-for-customer-delivery/
3•TeaVMFan•32m ago•0 comments

I benchmarked 22 local LLMs looking for the Qwen 3.8 35B we didn't get

https://sevangelatos.github.io/spiruxbench-results/blog/
2•koukopoulos•34m ago•0 comments

Google is pushing OEMs against GrapheneOS and bootloader unlocking

https://grapheneos.social/@GrapheneOS/117645038299496084
46•mraniki•38m ago•4 comments

Type inference and narrowing with reverse arrows in Elixir programming language

https://elixir-lang.org/blog/2026/11/10/inference-narrowing-reverse-arrows/
1•RebelPotato•38m ago•0 comments

New Ask Maps features to help with holiday travel and prep

https://blog.google/products-and-platforms/products/maps/ask-maps-holiday-travel-features-2026/
1•jimt1234•43m ago•0 comments

Princeton loses No. 1 spot in U.S. News and World Report after 15 years

https://thehill.com/homenews/education/6103606-princeton-us-news-rankings-mit-harvard-uc/
1•gmays•44m ago•0 comments

Foundering of the sailing yacht Bayesian with the loss of seven lives

https://www.gov.uk/maib-reports/foundering-of-the-sailing-yacht-bayesian-with-the-loss-of-seven-l...
4•longerthoughts•46m ago•0 comments

Zotero 10

https://www.zotero.org/blog/zotero-10/
2•evolve2k•49m ago•0 comments

Autonomous Trail Racing

https://pages.rai-inst.com/autonomous-trail-racing/
2•num42•54m ago•0 comments

The Discipline of Deliberate Building

https://elzohairy.me/deliberate-building/
2•noktasizvirgul•58m ago•0 comments

Show HN: Temporaland – Multiplayer digital jam space

https://margeux.com/temporaland/login.html
1•vegnus•1h ago•0 comments

Spray Bottle

https://mechanical-pencil.com/products/spray-bottle
1•allenc•1h ago•0 comments

Why ClickHouse and Agents Are a Great Combo

https://blog.exe.dev/meet-exe-finops-the-custom-tool-i-built-for-our-billing-data
1•pradeepchhetri•1h ago•0 comments

Windows Narrator LockScreen Bypass 0day

https://github.com/MSNightmare/FastUnlock
2•taspeotis•1h ago•0 comments
Open in hackernews

Show HN: ReJot – Database replication framework aimed at developers

https://github.com/rejot-dev/rejot
9•WilcoKruijer•1y ago
Hi Hacker News! We're Jan & Wilco from ReJot (https://rejot.dev). With ReJot we're building a framework that turns the write-ahead log of your database into an asynchronous communication channel for your services. ReJot enables application developers to define how the database tables they own should be replicated to other databases. Something we wish we had at in our previous job at a large fintech.

There is a gap between building internal (REST) APIs and Kafka (event streaming) to share data between services.

Internal APIs start to break down when you have more than a couple services communicating. Their synchronous nature makes them brittle in a distributed system: failures cascade and latency adds up. Companies operating internal APIs at scale often face challenges like managing implicit schemas and versioning. They also need to write significant amounts of code to implement features like circuit breakers and internal load balancing.

Event streaming addresses these issues by using asynchronous communication, but it also introduces significant drawbacks. Kafka is known for its operational complexity and high cost. Engineers must manage outbox tables, outbox processors, and consumers, which makes the system more difficult to understand and maintain.

ReJot is the middle ground solution that re-uses a database system's write-ahead log as an asynchronous communication channel. The WAL is well-suited to double as an outbox, this has been proven by CDC systems like Debezium. ReJot is a lightweight addition to existing infrastructure, and even re-uses existing (relational) database systems to store messages (temporarily) before sending them to the destination/sink databases.

We're developer focused, as opposed to being infrastructure focused. Much like how developers define the database table schemas they use, we enable developers to say how their data should be published to others in the distributed system. This is done through something we call "Public Schemas", they consist of a schema and a (SQL) query. When an item in the underlying table changes, the query is executed to produce an object conforming to the schema. This data is then forwarded through ReJot, ready to be consumed by a different service using a "Consumer Schema". This is again a simple (SQL) query that contains an INSERT statement. All of this is defined from within the codebase of the application, much like how ORMs or query builders work.

In short, ReJot re-uses your database in two ways: by consuming the WAL, and also by using queries to encapsulate and integrate data. This makes ReJot a good middle-ground between the brittleness of synchronous communication and the complexity of event streaming.

Excited to hear what you think!

Comments

raoulritter•1y ago
I'm thinking that now with all these agent to agent frameworks this could potentially work for that. If you send off one agent you want them to keep up to date and sync / talk to each-other. Could your solution work for something like A2A by google or similar to enhance the synchronization across the different agents doing their tasks and prevent them from landing in a loop or similar.
WilcoKruijer•1y ago
I'm not too familiar with how people store the state of AI agents, but I do think there's some opportunity to use ReJot for this use case. Hooking up an agent to ReJot and giving them access to all available Public Schemas could be an interesting way of letting an agent explore and use the data in a distributed system.
jasonthorsness•1y ago
If the consumers stall, doesn't the WAL have to grow in unbounded fashion? Does it place any backpressure on the writers?
WilcoKruijer•1y ago
You're right. Since we don't want to put too much pressure on the source database, we do save the (transformed) WAL items in an intermediary database (we call this the event store), so the source can clear its WAL.

This does mean the intermediary database can grow in an unbounded fashion. The use case really determines if this is fine or not. Since our focus right now is on (micro)service communication, we think this is fine in most cases, as the throughput usually is not gigantic.

Since the event store is just a Postgres database, it's easy to set up partitions to only retain data for a certain amount of time. On the near-term roadmap we also have back-fill support which will make it easier to work with shorter retention windows.