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.

[Geocoder] Multiple Lookup Strategy

Implement a strategy for using multiple geocoding APIs, including fallback mechanisms for unavailable APIs, bad results, or quota limits, and the ability to use different APIs for different query types or regions.

Original Source

@@alexreisner | 3 pts | 12/8/2012

We need a way to effectively use multiple geocoding APIs. Situations that need to be handled: - The primary API is unavailable and we'd like to automatically fall back to another. - The primary API is returning bad/unexpected results (or quota is reached) and we'd like to automatically fall back to another. - We'd like to use different APIs for different queries, depending on whether the query is an IP address or a physical address, but also if the query is for a certain part of the world where one API is significantly better than another (eg: Yandex in Russia). Ideas for implementation: 1. Set :lookup to an array of preferred APIs (descending preference). 2. Set :lookup to a block which takes a query and returns a lookup name, or an array of names (as in #1). Need to determine: - How to "fall back" to a less-preferable API. On timeout? On any API-related exception? On any Geocoder exception? On a particular API response? On a `nil` result? And how configurable does it need to be? -

Discussion

Loading comments...