Here in the Seattle area ferry schedules can matter. I cooked up this webapp, 4.5k bytes to load the front page, another 1/2k per destination you query.
Web technologies call out to the minimalist in me, but I appear to be in the minority.
When I wrote the login program for my VSTa microkernel, I took a page from the CDC side of the world--it echoes a _random_ (but small, non-zero) number of *'s. So you get feedback, but indeed peering over your shoulder will not disclose password length.
And yes, it remember how many it echoes so backspace works correctly.
Same motivation, different generation. I carry my own fork of vim 5.7, from around 2000. It did what I needed, and did it well, and I could already see where it was going.
Yes, I'm glad to see a comment on Prolog. I think of it as _the_ foundational programming language for solving such problems. It isn't so much that it's a back propagation language; it's just that, based on which variables are bound at a given point, it will go forward deductively, or backwards inductively.
To me, it feels like most feed readers are made by people who don't use RSS, and just exercise their feed reader on a few feeds. I seem to be at 211 feeds with (currently) 13,000 cached entries, organized across a couple dozen categories.
A reader where you'll click into the body under a headline only 1-5% of the time is a totally different beast.
A solid starting point, but it's easy to lose sight of the other critical part of the puzzle--integrity of the voting rolls. High quality vote tabulation needs to start from voters, where _only_ legitimate voters vote, and each only votes (at most) once, after which yes, their vote is accurately tabulated.
I converted a van to an RV, and now we stay in RV sites. Never going back to AirBNB/VRBO/Hotels! I know, useless for international travel, but within the USA it has become--by far--the most congenial option.