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.

[Directus] Fix 'list-m2m' interface not found error

Resolve the issue where modifying a field type to 'Many-to-Many' causes the interface to become corrupted, showing 'Interface not found'.

Original Source

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

### Describe the Bug Description: When creating or modifying a field to "Many-to-Many" (or switching from O2M), the interface sometimes gets corrupted. The UI shows "Interface 'list-m2m' not found". Even after manually updating directus_fields to set interface='list' and restarting, the error persists or the UI remains broken. The only workaround is often to completely drop the field and recreate it. ### To Reproduce Steps to Reproduce: Create a O2M field. Delete it via SQL or try to switch it to M2M. Recreate the field as M2M. Observe the error in the App. Version: Directus 11.15.4. The following SQL query didn't fix the UI until a full restart + cache clear: UPDATE directus_fields SET interface = 'list', display = 'related-values', options = '{"template": "{{rule_id.name}}"}' WHERE collection = 'accession' AND field = 'applied_rules'; ### Directus Version 11.15.4 ### Hosting Strategy Self-Hosted (Docker Image) ### Database PostgreSQL Version: 13.23 (Alpi

Discussion

Loading comments...