RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Candor] Add typography guidance for Noto Serif in AI/generative prose content

Request to add specific guidance to documentation on when to use Noto Serif for AI/generative prose content, distinguishing it from UI chrome fonts, as current documentation lacks specific instructions.

Original Source

@@pawn002 | 0 pts | 3d ago

## Background Candor includes Noto Serif in its font stack but provides no guidance on when to use it. The existing documentation implies it's for article/long-form reading contexts. During the Sovereign Council migration, a more specific and reusable pattern emerged. ## The pattern: prose/UI font split In AI-augmented apps, there is a meaningful distinction between: - **UI chrome** — labels, buttons, badges, metadata, status messages. Written by developers. Should be in Roboto Flex / Atkinson Hyperlegible. - **AI-generated content** — response text, analysis, reasoning, minority positions. Written by a model. Should be visually distinguishable from UI text. Using Noto Serif for AI-generated prose creates a clear visual contract: **serif = the AI wrote this, sans = the UI is telling you something**. This distinction: - Helps users immediately identify which parts of the screen are model output vs. interface - Reduces the risk of confusing UI instructions with model-generated conte

Discussion

Loading comments...