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.

[WorkAdventure] Allow Room API to bind to IPv6

The Room API currently binds explicitly to IPv4, causing connection failures when clients use hostnames with IPv6. Modify the Room API to listen on both IPv4 and IPv6.

Original Source

@@github-luckow-org | 0 pts | 14d ago

Hi, while packaging and testing WorkAdventure for self-hosted deployment, I found that the Room API currently binds explicitly to IPv4: `RoomAPI.bindAsync(`0.0.0.0:${ROOM_API_PORT}`, ...)` This causes a practical problem on hosts that publish both A and AAAA records. ## Problem If the public hostname resolves to both IPv4 and IPv6, clients may prefer IPv6 when connecting to the Room API. In that case, the TCP connection fails because the Room API only listens on IPv4. In my case: - hostname had both A and AAAA - Room API was reachable on IPv4 - Room API connection on IPv6 failed with connection refused - using the hostname for Room API clients failed unless I forced the IPv4 literal address ## Why this matters This is not specific to my packaging. It affects any self-hosted setup where: - the hostname has IPv6 enabled - clients connect to the Room API via hostname instead of hardcoded IPv4 - address selection prefers IPv6 That makes the Room API effectively IPv4-only by defau

Discussion

Loading comments...