News updates

Show HN: RewindCup – explore 23 World Cups on an interactive globe https://rewindcup.com July 19, 2026 at 03:37AM

Show HN: Peek-CLI: Let Claude Code iterate on front end designs https://ift.tt/E6iPpK0 July 19, 2026 at 12:32AM

Show HN: SDF Pelicans on Bicycle https://ift.tt/efVTqI9 July 19, 2026 at 12:47AM

Show HN: Get alerts for good seats at 70mm IMAX showings of The Odyssey https://imaxxing.io/ July 18, 2026 at 11:36PM

Show HN: Tarit – a hypervisor which is 2x faster than firecracker https://ift.tt/GQkw8d7 July 15, 2026 at 11:38PM

Show HN: Lific: Issue trackers should be simple, right? I built Lific because I direct AI coding agents on largish projects and needed somewhere for project state to live that isn't markdown files in the repo. When I was begging to work on long horizon ideas, I started on Linear, but my agent files issues faster than a human does, and I hit their limits and pricing wall almost immediately. Then I self-hosted a popular open source tracker which meant running its 13 containers, and its MCP integration was 30k tokens and I got so fed up that I eventually removed it and went back to .md files for a few weeks. Lific is the opposite shape of most of your self hosted server issue trackers: It's a single Rust binary that uses SQLite, and it has an optimized MCP server built in. Web UI is also included integrated directly into the binary. The simplicity is meant to only apply to the size and the ease of installation. The web UI is fully fleshed out with all of the UX you would expect fr...