Community guidelines

You don’t need an account to read a public spec or copy its text.

Copy and fork with credit

When you publish a spec here, readers can copy and adapt its spec text. If you publish a version based on someone else’s spec, credit the author and link to the source. Use “Fork this spec” on the original to start a draft with that credit. If you publish it as a separate spec, add the credit yourself.

That reuse is for the spec text, not the images or GIFs alongside it. Posting media here doesn’t give other readers permission to republish it. Only attach images you made or have the rights to share.

Keep private information out

Don’t post passwords, API keys, access tokens or other credentials, or other people’s personal data. Check spec text, comments and screenshots before posting. Don’t use Specbin to harass people or post spam.

Report a problem

Use the Report link for the spec, comment or attachment in question. Sign in and choose a username, then pick the reason that fits. Don’t paste secrets or personal data into the report. Reports aren’t public: moderators review them and can hide the item or dismiss the report.

Removal and privacy

Your published specs, attachments, comments and handle are public. Your sign-in email isn’t shown on your public profile. You can delete a spec you posted. Deleting or hiding content removes it from public reading here, but won’t recall copies readers saved. Published forks stay up even if the source is no longer available. Private reports and decision records can remain after the reported item is removed.