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 structured error hints

Enhance the CLI error output with actionable recovery suggestions by adding a 'Hint string' field to 'api.APIError' and populating hints for common failures.

Original Source

@@gianfrancopiana | 0 pts | 1d ago

## What Add actionable recovery suggestions to CLI error output. Currently some hints exist but are baked into `err.Error()` strings informally. - [ ] Add `Hint string` field to `api.APIError` - [ ] Define a `HintedError` interface so any error type can carry a hint - [ ] Populate hints in `internal/api/errors.go` for common failures (e.g., 401 → `"Run: gumroad auth login"`, 404 → `"Check the resource ID and try again"`, rate limit → `"Wait a moment and retry"`) - [ ] Update `classifyCommandError` in `internal/cmd/errors.go` to surface hints - [ ] In human mode, print the hint as a dimmed line below the error message - [ ] In `--json` mode, include `"hint"` in the error envelope ## Why clig.dev recommends: "Catch expected errors and rewrite them for humans — suggest the next step." Right now, a 401 prints a generic error. With hints, it tells you exactly what to run to fix it. This is a small change with outsized impact on the first-run experience.

Discussion

Loading comments...