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.

[OpenVINO] Add native ov::op::v17::atan2 to opset17

Request to add a native atan2(y, x) operation to OpenVINO's opset17. Currently, it's decomposed into ~40 nodes by frontends, and a native implementation would improve efficiency and consistency across frameworks.

Original Source

@@goyaladitya05 | 0 pts | 4/9/2026

### Request Description Hi team , I'm Aditya Goyal. I've previously contributed to the Keras OpenVINO backend (#34017) and would like tocontribute directly to OpenVINO's opset. I've drafted a proposal for the atan2 op as a starting point. **atan2(y, x)** is currently decomposed in the PyTorch, TensorFlow, and PaddlePaddle frontends via a shared translator in src/frontends/common_translators/src/op/atan2.cpp. The decomposition expands to ~40 nodes to correctly handle all IEEE 754 edge cases (quadrant selection, ±0, ±inf). A native op would: - Reduce the graph to 1 node - Delegate IEEE 754 correctness to std::atan2, which handles all edge cases natively - Enable plugin-level optimization (e.g. JIT emitters for x64/aarch64) torch.atan2 and tf.math.atan2 both map to this. It is also present in ONNX's extended opset (com.microsoft::Atan2). Note: atan2 was previously removed in PR #1184 (nGraph era). The codebase has been significantly restructured since then, and a native op fits in

Discussion

Loading comments...