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.

[Meshtastic] Implement separate screen timeout settings for battery and USB power

User requests separate screen timeout settings for when the device is running on battery power versus USB power. Currently, a single setting applies to both, which is inconvenient. A longer timeout is useful for monitoring on external power, while a shorter one is essential for battery saving.

Original Source

@@kawashirov | 0 pts | 3/18/2026

### Platform Cross-Platform ### Description Adding a separate screen timeout for battery power would be a great quality-of-life improvement. Right now, `display.screen_on_secs` applies to both USB and battery, which isn't ideal for nodes that move between home and field use. On external power, it's useful to keep the screen on longer for monitoring, but on battery, a quick timeout is essential for power saving. Since the firmware already tracks charging and power states, implementing an additional parameter like `display.screen_on_secs_bat` should be straightforward. This would allow for a "set and forget" configuration for any mixed-use node, removing the need to manually toggle settings every time the power source changes. Thanks🙏🏻

Discussion

Loading comments...