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.

[phpList3] Process bounced unidentified messages

The user requests that the system process bounced unidentified messages, as currently no action is taken when bounces are signaled as such.

Original Source

@@lwcorp | 1 pts | 2/18/2024

After noticing my bounce count is roughly the same after there were supposed to be consecutive bounces, I've realized when bounces were signaled as `bounced unidentified message` - and in those cases it seems no processing takes place at all. In other words, a subscriber's mail can bounce indefinitely and no action will be taken. The reason is [function processMessages](https://github.com/phpList/phplist3/blob/main/public_html/lists/admin/processbounces.php#L409) checks `$GLOBALS['tables']['user_message_bounce']`, but that table only lists identified bounces, so it's kind of a vicious circle. The irony is the user is known, it's just the message that is unknown. So if the user is known and we know there was a bounce, it should definitely go against that user's consecutive bounces and unconfirm if needed. Otherwise it affects being considered as a spammer.

Discussion

Loading comments...