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.

[Open WebUI] Add confirmation modal to delete shared link when archiving chat

Shared links for chats in Open WebUI continue functioning even after archiving the respective chat, leading to unintended exposure. A confirmation modal is needed to ensure users understand that archiving does not revoke shared access and to allow them to delete the shared link explicitly.

Original Source

@@silentoplayz | 1 pts | 6/7/2025

### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Upon discovery, I've found that shared links for chats in Open WebUI continue functioning even after archiving the respective chat. This can lead to unintended exposure of chat content if a user expects archiving to also revoke shared access. Specifically, if a chat is shared and then archived, the shared chat URL remains active and viewable by anyone with the link. Furthermore, while the archived chat is hidden from the regular user's chat list, and also from the admin panel's user chat list, it can still be directly accessed and viewed by an administrator if they possess the shared URL. This creates a potential privacy and data control issue as the chat becomes 'hidden' but not truly 'inaccessible' via its shared link, making management of shared content after archiving unclear and difficult. ### Desired Solution you'd like To improve the user experience and control over

Discussion

Loading comments...