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.

[Traction] Innkeeper: Monitor tenant settings and database usage

The Innkeeper should be able to monitor key elements of each tenant's wallet to assess usage patterns. This includes tenant-specific settings, exchange record/connection record persistence and state, and database usage (table size and breakdown by element type).

Original Source

@@esune | 0 pts | 10/16/2024

It would be nice for the innkeeper to be able to have a glimpse at some key elements of each tenant's wallet to assess whether undesirable usage patterns are in use, and what steps to take on next. Some items that would be nice to see: - tenant-specific settings: this is already visible by accessing the tenant with a temporary api-key - exchange record/connection record persistence and state - database usage: table size and, potentially, breakdown by element type (connection, exchange, etc.)

Discussion

Loading comments...