Public records must stay connected to GitHub
Works, articles, stories, discussions, requests, experiments, and setbacks may be published only when their connection to a GitHub project, program, discovery, or practice is clear and verifiable.
COMMUNITY RULES
Private space belongs to the member.
The public community belongs to GitHub.
Save anything privately in your own home. Public records must stay connected to GitHub. Failure and unfinished work are welcome. Fabrication is not.
Respect copyright and open-source licenses
Credit code, images, video, and text. Open source does not make every media asset free to reupload. Do not publish full third-party videos, paid material, or restricted assets without permission.
Preserve author credit
Every public experiment links to its author and GitHub source. Edited reuse on the official channel requires the author's separate permission.
Protect privacy and credentials
Hide email addresses, tokens, API keys, orders, addresses, and other personal data before uploading screenshots. Never publish another person's private information or usable credentials.
No spam, harassment, or manipulation
Spam, deceptive promotion, repeated flooding, personal attacks, impersonation, fake engagement, and coordinated false reviews are prohibited. Disclose financial interests and promotional links.
Private freedom, public review
Members control their private space. Public submissions are reviewed for GitHub relevance, sources, truthfulness, attribution, permission, and privacy.
REPORTS AND ENFORCEMENT
A report is evidence, not a vote.
- Signed-in members can submit one report on a public record and choose a specific reason.
- A moderator checks its GitHub connection, sources, permissions, and evidence.
- Unsupported reports are dismissed. Authors are notified when changes are required. Clear or serious violations may be removed.
- Malicious, repeated, or fabricated reports may lead to account restrictions.