3 ms·
This is a misunderstanding of how standards come about. Standards don't come about because someone theorizes pushing the envelope and then everyone gets togethe
by renewiltord 4y ago
This is a misunderstanding of how standards come about. Standards don't come about because someone theorizes pushing the envelope and then everyone gets together to form a convention to decide the best way to push the envelope.
Standards describe existing behaviour of value that benefits from a single interface. For that, the behaviour has to be first demonstrated. That's how the envelope is pushed. You make an implementation, then you show how that solves something worthwhile, and then if there are multiple implementations that could benefit from a single interface, you do that.
- orf 4y agoTotally agree, and I do hope that at some point this will be standardised. Ideally you’d have an endpoint that returns a set of patterns to check for and a way to submit a set of tokens for checking, along with some kind of context. It would probably be something like what GitHub requires[1]. Unfortunately that has somewhat limited value when GitHub can do most of the legwork for you, and as the de-facto place to publish code the majority of “accidental secrets exposed in code” are leaked there. 1. https://docs.github.com/en/code-security/secret-scanning/secret-scanning-partner-program#create-a-secret-alert-service https://docs.github.com/en/code-security/secret-scanning/sec...
- remram 4y agoAt the very least I would think GitLab might be interested in providing a similar feature.
- remram 4y agoThat's right, the behavior exist, on GitHub. Multiple services, including open-source ones like PyPI, integrated with it because they find it worthwhile. Yet it remains impossible for anyone to use it except through GitHub.