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.

[Pi-hole] Improve client IP visibility on eero network

Users are seeing all network traffic as originating from their eero router's IP address instead of individual client IPs. A feature to maintain client IP visibility directly on the Pi-hole would help resolve this issue.

Original Source

@u/mcar91 | 11 pts | 2/28/2026

I'm currently seeing all network traffic as originating from [192.168.4.1](http://192.168.4.1), my eero router's IP address. I'm pulling my hair out trying to figure out how to maintain client IP visibility! Here are all the details on my setup: * Pi-hole running in a Docker container, hosted on Unraid. It has its own IP address, [192.168.5.60](http://192.168.5.60), separate from its Unraid host, which is 192.168.5.42. * The Custom DNS on my eero network has [192.168.5.60](http://192.168.5.60) set as the primary DNS server, with [1.1.1.1](http://1.1.1.1) as the secondary DNS server. * Devices on my network span 192.168.4.x and 192.168.5.x subnets. * eero support recommended I switch to manual DHCP, which I did and I see no changes. * I have rebooted client devices and renewed their leases, but they still see [192.168.4.1](http://192.168.4.1) as their DNS server. * Running nslookup confirms [192.168.4.1](http://192.168.4.1) is the DNS server. Have others gotten this working on eero so the client devices talk directly to Pi-hole without proxying through the eero router?

Discussion

Loading comments...