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.

[proofofprotocol/proofscan] Define a canonical directory structure for POPL entries

The current directory structure assumed by `proofscan popl` commands needs to be aligned with the output directories generated by GenSpark-driven validation runs to support automated 2-layer evidence collection.

Original Source

@@genspark-ai-developer[bot] | 0 pts | 1/4/2026

## Background Currently, `proofscan popl` commands assume a local `.popl/popl_entries/` structure. GenSpark-driven validation runs generate their own output directories containing: - client execution logs - pfscan proxy artifacts - POPL.yml and related files To support automated 2-layer evidence collection, these folder structures must be aligned or importable without manual intervention. ## Scope Define a canonical directory structure for POPL entries: - Ensure that: - `pfscan popl ls / show` can operate on GenSpark-produced outputs - or GenSpark outputs can be generated directly in POPL-compatible structure - This alignment is expected to be used by the Validation Client ## Acceptance Criteria - [ ] A clear rule exists for where POPL entries live on disk - [ ] GenSpark validation output follows or can be imported into this structure - [ ] `pfscan popl` commands can list and show entries created via GenSpark runs - [ ] No breaking changes to existing POPL entries ## Relat

Discussion

Loading comments...