Unless whoever is patrolling this filtering is completely insane just show them that page that you were on and how hovering over the link triggers the filter.
Every instance of web filtering I've been subject to in my life just blocks the bad page and the admins expect people to have a few bad requests just by accident or whatever. You'd have to be constantly hitting the filter for it to actually become a real issue.
I only skimmed the github page, but this seems to be more of 'what the author commonly uses' rather than what you'd normally expect of a standard library. For example, I'd expect that many of these features be more in a separate dedicated library rather than the 'standard':
- 40+ PRNGs (You might want one or two, but do you really need so many varients?)
- Plot API (Definitely more suited for a separate library)
- 50+ Sample Datasets (Often useless and a lot of wasted space if not used)
- Native BLAS Interface (Extremely niche usecase)
Edit: To be fair, it does say right at the very beginning "with an emphasis on numerical and scientific computing applications". So they are upfront about it, but the library name and HN submission name are confusing because they don't make this obvious.
When using a single password for all sites, any malicious or breached website exposes access to all your accounts. When using a password manager, only a breach of your computer or the password manager itself (or your email) will totally pwn you.
Breaches online are very, very common, and I would expect any password used on every single website you use to get leaked quickly.
So I admittedly don't know much about this stuff, but what would be the difference between using Kong and the Nginx ingress controller? What advantages/improvements would I see/be able to use?