A new study of 7,704 employees handed remote work the well-being win. Remote staff scored 4.22 on a five point scale, hybrid 4.12, onsite 3.89. Then the same authors checked who had quit a year later, and work location predicted nothing.
The paper landed mid fight. HR Dive ran it beside Bank of America’s new rule barring two remote days in a row.
In today’s indie hacker news:
- 🧠 Remote led well-being, then location predicted nothing
- 📋 Pixel kernel source now arrives by Google Form
- 🔀 Stripe agreed to buy OpenRouter, deal unclosed
- 🐘 The case for collapsing your stack into Postgres
- 🏝️ 80.7 million triangles to place one photo
TOP STORIES
🧠 THE OFFICE DIDN’T KEEP ANYONE
Remote workers scored highest on well-being, and location predicted nothing about who quit.
The story: Nobody self reported anything here. Managers had already classified each worker in the HR system. Remote meant zero days onsite, hybrid meant two or three days in. Researchers surveyed the staff in 2023, then pulled turnover records a year later. The paper ran in Frontiers in Psychology on 29 July. A University of Colorado Boulder release pushed it wide on 19 August.
The details:
- Turnover a year on: 7.8% remote, 8.3% hybrid, 8.8% onsite. The authors call that spread statistically insignificant.
- Well-being was the only significant predictor of leaving, at an odds ratio of 0.71. Work location came in at p = 0.93 for remote.
- The gap itself is small. A third of a point on a five point scale, and it holds after age, gender and tenure.
- The authors flag their own confound. In a healthcare sample, remote roles skew administrative while onsite roles are clinical.
“If you have control over your environment, you tend to have more positive outcomes.” (Stefanie Johnson, study co-author)
Why builders care: Anyone defending a distributed team now has a peer reviewed number, and it names well-being, not location. The retention half of the return to office case has to find different evidence.
📋 SOURCE CODE BY APPOINTMENT ONLY
GrapheneOS says Pixel source now arrives by Google Form and Drive link, weeks later.
The story: GrapheneOS says Google stopped pushing Git tags for certain Pixel source. The replacement is a Drive tarball, handed out one Forms request at a time. Access used to land within a couple of hours, and lately it often takes weeks. The project calls that a clear GPLv2 violation. Android Authority traced its own coverage back to the same post, so this timeline is self reported.
The details:
- Same code, different door. The tarballs hold exactly the same source, and the history squashing started before the move.
- Access comes per file rather than per folder, so the project re-requests more files multiple times a month.
- Google’s own Build Pixel kernels page, updated 13 July, still documents the repo path and mentions no form anywhere.
- A banner on the same site says AOSP source now publishes twice a year, in Q2 and Q4.
- The licence claim is contested in the thread. One replier notes GPLv2 sets no deadline, and Google never answered Android Authority’s questions.
“Google could simply push signed tags to Git instead of having a person assigned to go through form submissions.” (GrapheneOS)
Why builders care: Your real SLA on an upstream dependency is its ticket queue, not its licence text. The fix here is the copyable part: mirror what you depend on, and pick a vendor that wants you there.
GrapheneOS says its first Motorola devices land in 2027, as flagships priced above Pixels.
🔀 WHO ROUTES THE ROUTERS
Stripe and OpenRouter confirmed the acquisition, and it hasn’t closed yet.
The story: OpenRouter told builders it’s joining Stripe, and Stripe put out its own release the same day. The post promises the same name, the same product, and routing that doesn’t bend to any parent company. It also says the deal is subject to customary closing conditions and should close in the coming weeks. Token spend is suddenly everyone’s line item, and today’s Stack of the Day exists to shrink it.
The details:
- OpenRouter’s own figures: 10+ trillion tokens a day across 400+ models for over 10 million developers.
- The price is third hand. CNBC cites the New York Times citing a person familiar, at about $7.5 billion with $1.5 billion to the founders.
- That sits on top of a $113 million raise at roughly $1.3 billion, closed less than three months ago.
- Default routing goes to the cheapest provider, says the thread’s most useful comment. It guesses 99% of integrations never change it.
- Neither announcement names a way for anyone outside to check the neutrality promise.
Why builders care: Nothing in your integration changes today, and that’s exactly when switching costs get built. A payments company now sits on both your meters, inference spend and revenue, with nobody outside auditing the route.
🐘 ONE DATABASE TO RULE THEM ALL
A fresh case for running the queue, the cache and the search inside Postgres.
The story: Raphael Bauer makes the argument with a result instead of a list. His team stored many small binary records as Flatbuffers in a blob column, expecting the file system to win. Postgres reads beat it. He builds on Stephan Schmidt’s original “just use Postgres” post, which lists more than 20 jobs to hand back.
The details:
- Schmidt’s availability math is the argument to reuse. Three specialist systems at 99.9% each compound to 99.7%, against one Postgres at 99.9%.
- The counter sits in the same survey. Stack Overflow puts PostgreSQL at 55.6% of respondents and Redis at 28%, with Redis up 8% year over year.
- Two old objections got weaker. Postgres 18 added asynchronous I/O with up to 3x faster reads, and it carries planner stats through major upgrades.
- The specialists are shipping their own front doors now: pg_clickhouse, Snowflake Labs’ pg_lake, pg_duckdb, and pgactive from AWS.
- The catch for managed hosts. Ruohang Feng’s extension table, a 2024 snapshot, marks AWS RDS and Aliyun RDS as closed to custom extensions.
Why builders care: A new service ships with one connection pool, one backup, one 3am pager. The evidence backs a default, since the specialist tools kept growing through the same window.
🏝️ GOOGLE LENS COULD NEVER
A solo dev brute forced every tropical island on Earth to place one resort photo.
The story: The photo had no EXIF, so yassa9 skipped the reverse image search entirely. He pulled the global coastline from OpenStreetMap, banded it to the tropics, and made candidate triangles from every cluster. Then he matched all of them on the graphics card in his desktop. A commenter later noted the photo is the resort’s own marketing image, and Google Lens finds it first. The author agreed, cheerfully.
The details:
- The funnel: 141,131 tropical land polygons cut to 23,500 clusters, then 80,690,777 candidate triangles.
- The GPU part was the cheap part. Matching all of them took 204.1 ms on a consumer RTX 3050.
- Filters cut the field to 26 survivors, and a human eye rejected the first seven rows before matching row eight.
- Every layer is free and keyless: OpenStreetMap polygons, Copernicus DEM tiles, Sentinel-2 imagery. The code runs in seven numbered stages.
- Commenters placed the method beside TERCOM, the cruise missile terrain matching from the 1960s. NASA’s Mars 2020 lander used the same idea.
“In my opinion, solving this challenge with google lens is wasting a fun opportunity.” (yassa9)
Why builders care: Building the unnecessary version in public is the distribution now, and this one pulled 431 points. The tax is a subthread arguing your prose came from a model.
TRENDING TODAY
- 🕰️ Casio F-B100W-1A - A single Casio product page pulled 297 points and 242 comments on Hacker News. When the comments nearly match the points, the thread is the real product.
- 🤖 Feature Request: Support AGENTS.md - An open issue asking Claude Code to read AGENTS.md hit 160 points. Every agent tool wants its own memory file, and builders keep asking for one standard.
- 🛰️ A joke domain purchase turned in geopolitical warfare - 796 points, more than anything else in today’s edition. Same writer as the Cricut unlock down in Bookmarked, which is quite a range.
DRAMA
💀 74 TOMBSTONES AND COUNTING
A directory that indexes 6,100 indie tools went looking for the dead ones.
Turbo0 checked which listings stopped resolving, redirected to a parking page, or visibly shut down. Its autopsy counts 74 confirmed dead, about 1.21% of everything it has ever listed, each one verified by hand.
Why builders care: Confirmed dead means the domain stopped answering, so that number is a floor. The tools that quietly stopped shipping still look alive in every directory you check.
STACK OF THE DAY
🧰 oc
oc turns a website into a small CLI that Claude Code can call. The pitch is that a command’s output costs fewer tokens than the page it came from. It hit Show HN a few hours ago at 4 points, so you’re early.
Not sponsored. We just feature tools builders would actually use.
BOOKMARKED TODAY
- 🦥 Unsloth Dynamic 3.0 GGUFs - Unsloth’s docs for its Dynamic 3.0 quants, 200 points on Hacker News. Bookmark it if you run local models and pick your own quants.
- 🔓 Unlocking a locked/deactivated e-waste Cricut Maker - Bringing back a Cricut the vendor switched off, 157 points. Hardware you own that dies on someone else’s decision is a genre now.
- 🎛️ Air Theremin - Wave at your webcam and get a theremin, 260 points and 86 comments. A weekend build that shows what a browser does with a camera feed now.
That’s the board for today. Go build something.
Ship to one country, QA it from another. Geo-fenced Stripe checkouts, region-gated APIs, feature flags that only fire in EU. NordVPN's 6,400+ exit nodes across 110+ countries let you test a US-only paywall from EU or hit a EU-only checkout from SF. Bonus: free Meshnet for SSH across your devices.
We get a cut if you sign up. Only added for tools we use ourselves.
Curated by AI, built by a human.