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.

[Ghost] Fix admin panel access for editors

Editors and authors cannot use the Ghost admin panel properly due to forbidden API calls when accessing staff settings. This needs to be resolved to ensure proper access for all user roles.

Original Source

@@DenisDoroshchuk | 1 pts | 2/26/2026

### Issue Summary We encountered a problem where our editors and authors cannot use the Ghost admin panel properly. I deployed the latest copy of Ghost locally and see that the problem also persists. When logged in as an **Editor**, opening the staff settings route and viewing an editor profile triggers admin API calls that require higher permissions. This results in noisy 403 errors and an unrelated toast: > "You do not have permission to browse members" The interface also becomes unresponsive (clicks on other items in the sidebar do not work). The same applies to other roles other than administrator, author, and contributor. I recorded a video demonstrating this problem: https://github.com/user-attachments/assets/467e037a-6406-4059-9651-622f4f06062c ### Steps to Reproduce 1. Create a Ghost site (tested on local install). 2. Have at least 2 users: - Owner/Admin - Editor 3. Log in as **Editor**. 4. Open `http://localhost:2369/ghost/#/settings/staff?tab=editors` (or `#/set

Discussion

Loading comments...