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.

[DSJAS] Expose module configuration in admin panel

Currently, some modules require manual modification of local storage to enable or configure features. The user should be able to configure these values via the admin panel, based on the module config file. DSJAS should modify these values before the module code runs via a script at page startup.

Original Source

@@ejv2 | 0 pts | 9/4/2023

Currently, there are at least two modules that I know which require you to enable or configure features by manually modifying local storage. This is a very good method of *storing* the configuration, but I see no reason why the user should do it manually. Instead, I propose that DSJAS expose these configuration values as specified in the module config file. Then, on request DSJAS will simply modify these values before the module code runs via a script which runs at page startup. Where there is currently just a link for "More Info" and "Uninstall" on the modules settings panel, I think we should add another link for "Settings" which then simply loads up the module configuration values. Additionally, we could add an abstraction via the new module API for module developers to have the settings loaded by the DSJAS API for them. To be clear, I envision this implemented in a completely backward compatible way such that users who are already using the local storage interfaces for the

Discussion

Loading comments...