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] Allow Power Amplifier (PA) selection in userspace

User requests the ability to select between various amplified modules (Power Amplifiers) in userspace via a configuration protobuf. This would simplify supporting different EBYTE modules and hardware revisions by allowing appropriate Tx power curves to be programmed without extensive sub-environments.

Original Source

@@ndoo | 1 pts | 15d ago

### Platform NRF52, Cross-Platform ### Description I would like to introduce a configuration protobuf (I am guessing a struct) to select between various amplified modules to program in the appropriate Tx power curve. This would greatly simplify the proliferation of many different sub-environments needed to support various EBYTE modules, for example, and possibly different hardware revisions of products like Heltec v4 which may use different FEMs between hardware revisions. E.g. this would simplify the XIAO nRF sub-variants that exist for E22-900M22S, E22-900M30S, E22-900M33S. Additionally, a build-time define like LORA_PA_OPTIONAL for example, should clamp the Tx power to 0dBm (which still transmits, albeit weakly) for safety (avoid burning the PA) until a PA (or explicitly selecting that there is no PA e.g. E22-900M22S) is specified. I bring this up now because I don't feel like we should continue expanding variants to add E22-915M30P, E22-915M33P, which also have different cur

Discussion

Loading comments...