Sorry, I don't understand, why you closed this. The problem is:

• You can block commits, for example, if you don't want to see private data there
  • But if you want to block private data, you need to put in that data in a global herald rule, which is public visible
    • But if you don't use regex, you can block private data, yes, but everyone who can access herald, can see the data, so this feature is not very useful at the moment.

We prefer people follow our posted guidelines on filing feature requests. We don't take feature requests that don't state a problem. Specifically "feature does not exist" does not satisfy our criteria for requesting features.

More specifically we'd prefer if people:

1. Use Phabricator (in production)
2. Have users run into problems (in production)
3. Tell us what those problems are

It might be we end up at the same solution, or we have something larger planned that covers lots of other edge cases. Mostly though, even if we take a new feature request, it could be years before coding would occur. We're very small (2 people) and have limited ability to tackle edge case requests. You're best bet is always to just describe the problem and we'll help find a solution.

You may also be interested in T9212 which explains a bit better why "free support" is increasing burdensome for the upstream.