Method and coverage

1. 1ReadEvery day at 05:25 UTC (and a lighter pass at 17:25 UTC) the scan reads public sources: Hacker News through the Algolia API, public Reddit feeds (a few subreddits a run, slowly), Stack Overflow, the most-reacted GitHub issues of major data and AI repos, Discourse forums, Bluesky and Mastodon public posts, YouTube video titles, 1 and 2 star App Store reviews, and outages, deprecations, breaches and advisories from other fru.dev sites.
2. 2Keep what states a painA post counts when it says something hurts: "struggling with", "doesn't work", "workaround", "is there a way", "rate limit", "nightmare" and about a hundred more phrases. Issues, unanswered questions, forum help topics and low-star reviews count by nature. On general sources the post must also be about tech.
3. 3Name the issue and the companiesEach post is matched to a known issue (the table below) and to the companies and products it names: a product list plus every company in the companies.fru.dev registry, matched by exact name.
4. 4GroupPosts with the same issue about the same product become one problem once two posts say it; until then they join the general problem. Posts about a product with no known issue are grouped by the title word they share (3 or more posts). Statements are written by these rules, 12 words or fewer.
5. 5MeasurePer problem: posts per day, the last 7 days against the 7 before (rising, steady, fading, new), days active, distinct people and places, frustration from strong words, and the top three links. Persistent means 5 or more active days across two weeks and still active this week.
6. 6Keep historyPosts, day counts and daily snapshots are append-only; every change is on the Changes page. A cluster backed by fewer than 3 posts from 2 people or places stays marked unverified.

Registry: 761 companies.fru.dev companies enrolled, 77 with at least one problem (10%). The rest are watched on every run. Last run: seed, ok, 657 posts added, 125 new problems, 2 new sources.

• Reddit answers scripts slowly and blocks bursts, so each run reads a few subreddits in turn; a subreddit is read about every five days.
• Slack: only communities that publish public archives. Private workspaces are never joined or read.
• YouTube comments need a YouTube Data API key; until one is set only video titles are read.
• X, LinkedIn, G2 and TrustRadius are not read: they need a login or do not allow it.
• Bluesky is read by search, Mastodon by public tags on mastodon.social only.
• Rules miss sarcasm and can file a post under the wrong issue; clusters with few posts are marked unverified. Suggest a fix on any problem page.