Acceptable use

Do not publish

• Credentials. Passwords, enable secrets, community strings, API keys, private keys. Not even expired ones, not even in a comment.
• Anything identifying a real network you do not own. Customer names, site names, real management addresses, circuit references.
• Sets designed to cause harm. Something whose purpose is to damage equipment, exfiltrate configuration, or open a way back in.
• Disguised behaviour. A destructive command buried in whitespace, hidden behind a misleading button name, or padded out so nobody reads to the end. The whole model here is that people can read what they run.
• Other people's work passed off as your own, or content you have no right to share.
• Spam, advertising, or anything not a button set.

Fine to publish

• Buttons that reboot, reload, erase or factory-reset. These are normal parts of the job. They get flagged and labelled, which is the point — not blocked.
• Vendor-specific sets, however niche the platform.
• Sets that only make sense with your own conventions, as long as you say so in the description.

Accounts

One person, one account. Do not use the site to probe, scrape or overload it, and do not create accounts to evade a suspension. Automated bulk downloading is rate-limited; if you want a bulk copy of something, ask.

Enforcement

Moderators can unpublish a bundle, remove it, or suspend an account. Serious cases — deliberately malicious content, published credentials — go straight to removal and suspension without warning. Every action is written to an audit record.

If you think a decision about your content was wrong, email hello@smartcomrevisited.com.

Reporting a problem

Use the report button on the bundle, or email abuse@smartcomrevisited.com. For a security problem with the site itself, email security@smartcomrevisited.com rather than posting about it publicly.