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), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[ProbOS] Implement question-adaptive retrieval routing

The system should route recall queries using different retrieval strategies based on the question type (e.g., TEMPORAL, SOCIAL, FACTUAL), as the current system only uses intent_type and lacks awareness of question content. This would allow for type-specific weight profiles for scoring recall.

Original Source

@@seangalliher | 0 pts | 18d ago

## Summary Route recall queries through different retrieval strategies based on question type (TEMPORAL/SOCIAL/FACTUAL/CAUSAL/PROCEDURAL/EXPLORATORY). Currently `classify_retrieval_strategy()` uses only `intent_type` — it has no awareness of question content. A temporal query and a factual query use the same retrieval weights and budget. ## Design - Question type classifier: `classify_question_type(query) → QuestionType` enum - Type-specific weight profiles for `score_recall()`: TEMPORAL boosts recency + temporal_match, FACTUAL boosts keyword + anchor - Strategy adjustment: `classify_retrieval_strategy()` gains optional `question_type` parameter - Budget tuning per question type ## Depends on - AD-568a (RetrievalStrategy) - AD-570c (parse_anchor_query) - AD-584b (Query Reformulation) ## Research Question decomposition pipeline in `docs/research/memory-retrieval-research.md` Section 3, 8.2-8.4. Anderson & Pichert (1978).

Discussion

Loading comments...