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.

[Jitsi Meet] Configurable Security URL for External API

Enhance the security warning system by allowing the configuration of the security URL for external API deployments, utilizing the existing `legalUrls.security` config field.

Original Source

@@dipanshurdev | 0 pts | 3/14/2026

### Description The security warning system currently uses a hardcoded URL (`https://jitsi.org/security/`) which limits external API deployments. However, the config structure already includes `legalUrls.security` field that should be utilized. ### Solution Leverage existing `legalUrls.security` config field by: 1. Adding `DEFAULT_SECURITY_URL` constant 2. Enhancing [getLegalUrls()](cci:1://file:///c:/Users/hp/Documents/Work/git%20forked/jitsi-meet/react/features/base/config/functions.any.ts:428:0-448:1) to include security URL 3. Creating [getSecurityUrl()](cci:1://file:///c:/Users/hp/Documents/Work/git%20forked/jitsi-meet/react/features/base/util/contants.ts:5:0-16:2) helper that uses existing structure 4. Updating cross-platform implementations ### Benefits - ✅ Uses existing config patterns - ✅ Maintains architectural consistency - ✅ Enables custom security endpoints - ✅ Cross-platform compatibility - ✅ Zero breaking changes ### What solution would you like to see? _No response

Discussion

Loading comments...