Niche data-aggregation Show HNs: one painful lookup, turned into a product

Unfenced lists land for sale that actually borders public land. Listings say 'borders state land' but you have to line up county GIS parcel lines against public-land maps by hand. Another commenter says they were about to build the same thing. Indigene recommends native plants for where you stand, though users flag a wrong soil guess and no way to change it, and suggestions that skew toward common weeds. Flipflop makes persistent filesharing tunnels on Iroh, and Ito builds terminal UIs in Lua.

The pattern is a single sharp problem, a public dataset joined with another, and a clean UI. Questions in the comments are all the same: where's the data from, how fresh is it, can I correct it? The data source and the override matter more than the interface.

The skeptics ask real questions. Is land next to public land actually desirable, with people wandering through? Why native code for a tunnel when WebRTC exists?