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.

[Meshtastic] Streamline and reduce the number of node roles

User proposes reducing the current list of 11 node roles to a more concise list of 6 (Client, Client_base, Router_late, Router, Tracker, Sensor). Additional functionalities like TAK features and disabling rebroadcast would be managed via switches for each role, simplifying the overall role management.

Original Source

@@NomDeTom | 4 pts | 13d ago

### Platform Cross-Platform ### Description The current role list is as follows: 1. CLIENT 2. CLIENT_MUTE 3. CLIENT_HIDDEN 4. CLIENT_BASE 5. TRACKER 6. LOST_AND_FOUND 7. SENSOR 8. TAK 9. TAK_TRACKER 10. ROUTER 11. ROUTER_LATE Proposal: Reduce the role list as follows: 1. Client 2. Client_base 3. Router_late 4. Router 5. Tracker 6. Sensor Additional switches would be available for the role to adjust the following: - TAK features - Disable rebroadcast (for `client`, to replicate `client_mute` & `client_hidden`) - Disable routine broadcast (to replicate `client_hidden`) - Power saving (to make the "sleepy sensor" and "sleepy tracker" options more obvious) The tak-specific roles and `LOST&FOUND` roles would be retired. Further reductions could be made if replay allows deprecation of `client_base` and/or `router` roles. `Router_late` may need to be retained as a strategic infill type, as might `router`

Discussion

Loading comments...