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.

[Azure] Improve logging granularity for ACL changes in ADLS Gen2

The user is trying to build a notification system for when an ACL is removed on a folder in ADLS Gen2. They find that the current logging does not specify whether an ACL change was a modification or a removal, making it difficult to track changes effectively. They request improved logging to provide more detailed information about ACL changes.

Original Source

@u/Shot-Row6907 | 2 pts | 3/14/2026

I’m currently banging my head against AzureBlobLogs (StorageBlobLogs) trying to build a basic notification system for when an ACL is removed on a folder in ADLS Gen2. I’m focusing on two operation types: 1.SetPathAccessControlRecursive 2.SetPathAccessControl The Problem: SetPathAccessControlRecursive is at least somewhat helpful because it captures the mode (modify, or remove) within the URI. I can work with that. However, SetPathAccessControl tells me absolutely nothing. It logs the operation, but doesn't specify if it was a modification or a full removal. On top of that, the RequesterObjectId is missing half the time (I was doing acl changes via portal btw) making it impossible to see who did what. I really don't want to resort to building a complex Azure Function or taking scheduled ACL snapshots to do a "before and after" comparison. I want to achieve the bare minimum using just the logs if possible. Has anyone found a clever way to correlate these logs with other signals to get the missing Requester identity? Am I fighting a losing battle trying to use BlobLogs for this level of granularity? Any tips clarifications would be appreciated.

Discussion

Loading comments...