Fastest Growing India 2020

Wednesday, June 3, 2026

Show HN: Live breath detection and biofeedback from a phone microphone https://ift.tt/UuOR5HQ

Show HN: Live breath detection and biofeedback from a phone microphone https://ift.tt/V3yLOlU June 2, 2026 at 09:32PM

Citywide Muni Goal Rush Connects Soccer Fans Starting June 11

Citywide Muni Goal Rush Connects Soccer Fans Starting June 11
By Nashelly Chavez

The Muni Goal Rush is a new citywide crawl that connects soccer fans across San Francisco from June 11 - July 19. A new citywide crawl — the Muni Goal Rush — is coming to San Francisco! This crawl invites you to root for your favorite teams and explore the city during the FIFA World Cup 26™ SF Bay Area. From June 11- July 19, experience world-class soccer, public transit and the best of nine San Francisco neighborhoods. With amazing prizes and the opportunity to explore, you won't want to miss out. How to play First, pick up a Muni Goal Rush game card. Find it at any of the participating...

Published 2026-06-02T00:00:00Z
https://ift.tt/nfb1h5B

Show HN: RePlaya – self-hosted browser session replay with live tailing https://ift.tt/sb7dprX

Show HN: RePlaya – self-hosted browser session replay with live tailing Hi HN, I'm one of the founders of s2.dev. RePlaya ( https://ift.tt/2dx9n7F ) is a self-hosted browser session replay tool using rrweb ( https://ift.tt/ZtnyMEk ). It occurred to me that a durable stream per session would be a much neater architectural foundation for much of what you'd want from such a tool. As a unique feature, it also made live tailing straightforward because the player can read from the same stream the recorder is appending to. The alternative architecture is likely an ingest firehose which is then indexed, with associated complexity and latency. You'd have to string together multiple data systems like a message queue, a metadata database, and blob storage and/or an OLAP database. Here the only dependency is S2, which has an open source version you can self-host called s2-lite ( https://ift.tt/RdGn7IH ). How it works: - one S2 stream per browser session - large rrweb events (like a full snapshot) get framed across multiple binary S2 records and reassembled on read - active sessions are tailed with an S2 read session, and bridged to the browser over SSE - session listing relies on stream names encoding reverse timestamps, as S2 returns a lexicographic order listing - relying on fencing tokens so a stopped session can't be written to again by a late recorder - retention and GC are handled via S2 stream config, so no background job needed Curious to hear from folks on the tool or the stream-per-session model! https://ift.tt/2dx9n7F June 2, 2026 at 11:10PM