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.

[Gumroad CLI] Add browser-based OAuth login

Implement browser-based OAuth login for the CLI to eliminate the need for manual API token copy-pasting, similar to the existing Expo mobile app pattern.

Original Source

@@gianfrancopiana | 0 pts | 1d ago

## What Add browser-based OAuth login so users don't need to manually copy-paste API tokens. ### Gumroad side (prereqs) - [ ] Register a CLI OAuth application in production (same pattern as the existing Expo mobile app) - [ ] Store its UID as `CLI_OAUTH_APPLICATION_UID` in production env vars - [ ] Mark the app `confidential: false` (public client — no secret needed for CLI) - [ ] Scopes: `edit_products view_sales mark_sales_as_shipped edit_sales view_payouts view_profile account` - [ ] Optionally add to Doorkeeper's `skip_authorization` so logged-in users don't see an extra authorize screen ### CLI side - [ ] Implement browser-open + localhost callback flow: open `https://app.gumroad.com/oauth/authorize`, start HTTP server on `127.0.0.1:<port>`, receive auth code, exchange for token via `/oauth/token`, store in config - [ ] Embed the OAuth app's client ID in the binary - [ ] Headless/SSH fallback: print the authorize URL, prompt user to paste the redirect URL back - [ ] Keep `gum

Discussion

Loading comments...