The issue is the whole UX behind it. I have yet to see someone review the 30th prompt of "grep" - there is no same default or middle ground.
For example whitelist read actions or harness side limitations to the project folder.
This is just lazy - again. "Users don't use or very bad security feature so they just want us to disable it".
To get to the certificate with which you THEN can attack devices remotely. I.e. the attacker needs one device. And the skill to extract the certificate and the willingness to abuse it.
One of each and then the 613k devices in the tested region are exposed.
This sounds like an ad.
Note that "patented" doesn't mean shit.
Plus it's not as unique as they make out to be:
https://en.wikipedia.org/wiki/Post-quantum_cryptography
I personally wouldn't use an encryption where someone else could change the conditions on how I use it anyway.
In short: yes. You can tune these values when self hosting - it basically changes the b chance which tokens will be used under which circumstances.