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.

[Penpot] Allow plugin code and icons to resolved relative to the manifest

Allow plugin code and icons to be resolved relative to the manifest file for easier plugin hosting and management, especially in containerized environments.

Original Source

@@eniac11 | 0 pts | 10d ago

### Is your feature request related to a problem? Please describe. I have setup penpot using podman and now wanted to explore hosting plugins. I setup a container with nginx and one of the plugins provided in the repo (I use pnpm build and copy the dist output to the image). One container works fine. Now I wanted to expand it to multiple so I created one image per plugin (nginx + plugin dist). Then a used another nginx container to proxy_pass to the internal network. Everything should be fine on the container side. When I try to load a plugin it cannot resolve the icon and plugin.js. ### Describe the solution you'd like. Allow assets and code to resolved relative to the manifest path. Currently this is not possible because the frontend store set plugin manifest host to the origin. Line 88. <https://github.com/penpot/penpot/blob/52496243ac83409acb71a82adcec2fca113932fa/frontend/src/app/plugins/register.cljs#L81-L91> ### Describe alternatives you've considered. - Exposing each

Discussion

Loading comments...