ads

Saturday, July 18, 2026

Show HN: Get alerts for good seats at 70mm IMAX showings of The Odyssey https://ift.tt/ei6bNBj

Show HN: Get alerts for good seats at 70mm IMAX showings of The Odyssey https://imaxxing.io/ July 19, 2026 at 01:06AM

Show HN: Randomly Generated ASCII Trees https://ift.tt/eNwshuZ

Show HN: Randomly Generated ASCII Trees Code : https://gist.github.com/Soham-Saha/12296c059cea074b2fed5e97a... https://ift.tt/hlPi9KQ July 18, 2026 at 10:57PM

Friday, July 17, 2026

Show HN: Lific: Issue trackers should be simple, right? https://ift.tt/2wpNzWv

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 from an issue tracker like linear. Since I started using lific, my agent flow is that I open the web UI, find a few issues I want to work on, then tell the agent "work on LIF-298, 299 and 301, and if you find bugs, file them as new issues." At the end of the day the project has tracked itself. Issues have statuses, blockers, and comment threads, so "what's workable right now" is a query instead of the agent guessing. Plans are persisted step trees, so a session tomorrow resumes with the same understanding of the goal and the path as the session that made the plan. My largest project has 300+ issues and 100+ docs and agents search it fast. Everything exports to markdown in one click, and the database is just a file on your machine. Setup is ` cargo install ` ` lific init ` ` lific connect ` then pick your harness (OpenCode, Cursor, Claude Code, etc). One honest caveat: on Windows there's no service install yet, so the binary has to be actively running for MCP or Web UI to work on windows. The biggest reason I think Lific is different than a lot of the other options is the lightweight nature of it alongside still having a fully featured web UI. It's meant for self hosters to work on big projects with agents, without sacrificing the other benefits of an issue tracker like a nice management UI or authentication for teams using it. Would genuinely love feedback and bug reports either here or on the discord! https://lific.dev July 18, 2026 at 12:52AM

Show HN: A zoomable timeline of 4M Wikipedia events https://ift.tt/owHUOyc

Show HN: A zoomable timeline of 4M Wikipedia events I'm building a journal app in Kotlin Multiplatform and for this purpose I have created a zoomable timeline interface. This is a side-project where I reuse the timeline interface to display 4 million events imported from Wikipedia / Wikidata, scored using PageRank. There is more information on the about page. If you're interested in the stack: I use Kotlin Multiplatform extensively, with Compose Multiplatform for the UI, communicates with the backend using Kotlinx-RPC and behind the hood a simple Postgres database on a Hetzner machine. https://ift.tt/XFnBLZ2 July 18, 2026 at 01:37AM

Show HN: Proton – A Pure Go, Immediate-Mode GUI Library (Zero CGO) https://ift.tt/JV0cit8

Show HN: Proton – A Pure Go, Immediate-Mode GUI Library (Zero CGO) Hi everyone, I’ve been building Proton to solve a specific pain point in the Go ecosystem: building native GUIs without the "web dev" trade-offs or CGO complexity. If you’ve tried to build desktop apps in Go, you’ve likely dealt with the frustration of CGO dependencies, bloated build pipelines, or feeling like you’re just writing a thin wrapper around a browser. Proton aims to fix this with a clean, pure-Go approach: Zero CGO: Cross-compile to Windows and macOS seamlessly from any machine. Immediate-Mode API: No setState, no complex component trees, and no XML. You just write your draw function, and it runs every frame. API Immunity: The public API is shielded from the underlying rendering engine (built on top of Gio). If the backend changes, your code remains untouched. Full Feature Set: Includes inputs, lists, overlays, alerts, and 46 built-in themes (or easy custom hex-code styling). It’s currently in development for v0.4.0, but it’s stable enough for cross-platform apps and even supports Android deployment out of the box. I’d love to hear what you think, especially if you’ve been looking for a more "Go-native" way to handle GUIs. Repo: https://ift.tt/miVGnjr July 17, 2026 at 10:20PM

Thursday, July 16, 2026

Show HN: QBasic Gorillas (Repeeled) https://ift.tt/Nj7F5ca

Show HN: QBasic Gorillas (Repeeled) I've found the most engaging way to practice techniques for AI-assisted development and test models is to build fun side projects in vanilla JS. I spent many hours playing (and studying and editing) QBasic Gorillas, and this is a vanilla JS implementation using Fable and Opus. Play 1-on-1 hotseat or against the computer. A bit of extra camera snazz as well. https://ift.tt/XNgrpGE July 16, 2026 at 09:34PM

Wednesday, July 15, 2026

Show HN: Lineation – One security control plane for all agents https://ift.tt/h6M9frk

Show HN: Lineation – One security control plane for all agents TLDR: Distributed policy enforcement and a "black box" for AI agents https://lineation.ai July 15, 2026 at 11:25PM

Tuesday, July 14, 2026

Show HN: A device for never missing the surf turned into something more https://ift.tt/Zq6Lu7G

Show HN: A device for never missing the surf turned into something more https://ift.tt/W1x0QAu July 15, 2026 at 02:12AM

show hn: 1d data to 3D topology, AI deepfakes to protien folding https://ift.tt/EBSvUer

show hn: 1d data to 3D topology, AI deepfakes to protien folding https://ift.tt/8Xr9PpH July 15, 2026 at 12:29AM

Show HN: Pullrun – Run One OCI Image as a Container, Firecracker, or Apple VM https://ift.tt/x6ey8QC

Show HN: Pullrun – Run One OCI Image as a Container, Firecracker, or Apple VM https://ift.tt/C6fq487 July 15, 2026 at 12:19AM

Show HN: BeePub – A reading-first alternative to Calibre-Web https://ift.tt/yxHYgkO

Show HN: BeePub – A reading-first alternative to Calibre-Web I've used Calibre's content server and calibre-web, and for actual reading I was on Calibre + Apple Books. It got the job done, but it never felt smooth — so I built my own, working with Claude Code. It's fully compatible with Calibre — that's how I run it myself: my books still live in a Calibre library, and BeePub just points at it and stays in sync (read-only; Calibre remains the source of truth). Same as calibre-web. I've put a lot of work into CJK / Traditional Chinese support (including vertical text), and into manga EPUBs. There's also a native app built with Capacitor, currently on TestFlight (iOS). It also speaks OPDS and KOReader progress sync (kosync), so it plays nicely with e-ink readers. If you're curious, play with it at https://demo.beepub.app (login: demo / demodemo — the data resets every 6 hours). This is a project I dogfood every single day, so expect it to keep getting updates! https://ift.tt/Aib1jQL July 14, 2026 at 11:21PM

Monday, July 13, 2026

Show HN: Jacquard, a programming language for AI-written, human-reviewed code https://ift.tt/g29xiGE

Show HN: Jacquard, a programming language for AI-written, human-reviewed code https://ift.tt/1eDzEGR July 13, 2026 at 10:56PM

Sunday, July 12, 2026