Big annoyances AI might finally make fixable

A public source trail for things that keep bothering people.

The point is not a giant complaint pile. The point is to find recurring burdens with real costs, check them against the source trail, and make it clear which ones are worth taking further.

Raw titles are clues. They are not proof that a problem is big, common, important, or solvable.

That is why the project keeps observations, reviews, proposals, and validations separate.

The published list contains the strongest source-backed annoyances from the current release. It is a selection from the work, not a claim that every problem is solved.

General annoyances

Published annoyances

These made it through the current source check and Big Annoyance Test. They are the public list; the work behind each one stays linked below.

Browse general annoyances

Search the published general list by the kind of annoyance it describes.

City layer

City-specific annoyances

This is a separate collection for annoyances from specific cities. San Francisco is the first one. We can compare cities later; this section does not reclassify the general annoyance list.

The trail behind the list

How the list is made.

The homepage shows the published list. The repo keeps the work behind it: what was collected, what was grouped, what passed the source check and Big Annoyance Test, and what still needs formal problem review.

04

Formal problem review

Published annoyances can later become reviewed problems, proposed fixes, and validations.