Community Rules
We want useful discussion, aggressive testing inside authorized scope, and zero incentive for spam or malicious exploitation.
Contribute, do not make noise
Post volume does not generate score by itself. Ideas, tests, documentation and useful help may be recognized when they add real value.
Responsible disclosure
Sensitive issues must be sent through the private Bug Lab. Do not publish exploitation instructions while an issue is open and do not attack users, data or infrastructure outside authorized scope.
No farming
Spam, duplicate reports, fake accounts, reaction manipulation or attempts to farm score may lead to score removal, suspension or exclusion from future campaigns.
Respect and content
Technical disagreement is welcome; harassment, threats, fraud, illegal content or attempts to obtain other users’ credentials are not.
Scores are not K³
Contribution Score, Bug Hunter Score, Testing Score and Ideas Score are internal reputation. They have no price and do not guarantee a future amount of K³.
Moderation
The team may lock topics, reject reports, correct classifications and suspend accounts to protect the community and project. Important decisions should leave an auditable history where applicable.