rrweb

hey! thanks for the feedback. Only for web right now - mobile is on the roadmap. We are recording sessions using rrweb (https://github.com/rrweb-io/rrweb) As for privacy, I get where the concerns are coming from. But as somebody who has used session recording before - it is such a helpful tool to understand how your customers are using your product and struggling. Also, all the data you get from a session recording - is data you already have (or could easily get).

Hi HN, I'm one of the founders of s2.dev. RePlaya (https://github.com/s2-streamstore/replaya) is a self-hosted browser session replay tool using rrweb (https://github.com/rrweb-io/rrweb). 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://news.ycom