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.

[TruffleHog] Expose full Postgres connection string parameters in detector output

For the "postgres" detector, the connection string is currently truncated, omitting crucial parameters like DBNAME. The user requests that these additional parameters be included and accessible in the detector's output.

Original Source

@@Fee0 | 0 pts | 2/20/2026

## Description Currently, for "postgres" detector, "raw" and "raw_v2" contain the same truncated connection string that looks something like this: postgresql://XXXXX:YYYYYYYY@HOST:PORT The real connection string may contain additional parameter after PORT like the DBNAME which is necessary to connect. Currently, there seems to be no field to access these additional parameters after the PORT except for "extra_data" which seems to parse "sslmode". In order to get the dbname I would need to manually query the link and parse the parameters. postgresql://XXXXX:YYYYYYYY@HOST:PORT/DBNAME?sslmode=require ... ### Preferred Solution Since "raw" and "raw_v2" seem to contain the same string maybe we could make raw_v2 the real RAW connection string including all parameters? Or parse more parameters into "extra_data" json blob.

Discussion

Loading comments...