Community Guidelines

o.cafe is meant to be useful to independent developers, open-source maintainers, and people who use AI tools.

The basic expectations are:

• share information that is honest and useful;
• treat people with respect;
• do not create security risks;
• do not drown out the community with ads, fake activity, or manipulation;
• promote your work when it is relevant, transparent, and not repetitive.

Criticism can be direct. Aim it at work, ideas, and behavior—not at a person's dignity.

You are welcome to:

• introduce a project you made and share what changed;
• publish tutorials, essays, Prompts, Skills, MCP tools, software, and resources;
• compare or criticize projects with evidence;
• ask and answer technical questions;
• discuss open-source licenses, security practices, and maintenance;
• recommend your own product or service when it directly fits the discussion and you disclose your connection;
• share lawful defensive security research, CTF work, authorized testing, and responsible disclosures.

Do not repeatedly post the same material or link, push promotions into unrelated discussions, use bots to comment or register at scale, hide a commercial relationship, publish fabricated reviews, offer referral kickbacks to recruit users, use deceptive traffic funnels, send unsolicited commercial messages, or create thin content solely for SEO or backlinks.

Creators may explain their work on their profile and project pages and share updates, tutorials, courses, sponsorship links, or community links. Be clear about your connection, add real value, avoid repetition, and respect a “no.”

Do not:

• automate or send GitHub Stars in bulk;
• require a Star in return or create an obligation to reciprocate;
• offer rewards, cashback, eligibility, or ranking in exchange for a Star;
• use account farms, scripts, or fake identities to create support;
• fabricate visits, comments, supporters, or recommendations;
• organize circular support rings or manipulate a leaderboard.

It is fine to invite people to look at a project and support it voluntarily. Their choice must remain theirs.

Do not share phishing pages, fake sign-in flows, credential-stealing tools, malware, ransomware, backdoors, compromised installers, hidden destructive commands, stolen credentials, or instructions aimed at attacking a real target without authorization.

When discussing a vulnerability, remove real credentials and details that would directly harm an unpatched target. Send site vulnerabilities, account takeover reports, exposed tokens, cookies, or secrets to security@o.cafe, not to a public comment.

Do not stalk, repeatedly harass, organize a pile-on, threaten violence, extort, encourage harm based on identity, expose someone's home address or movements, share non-consensual intimate material, engage in sexual exploitation, share sexual content involving minors, or encourage self-harm, seriously dangerous conduct, or real-world crime.

Technical and product disagreements can be intense without becoming personal attacks or real-world threats.

Do not impersonate a person, company, project, official account, or maintainer. Do not claim a project you do not control or fabricate a partnership, certification, revenue figure, Star count, user count, job opening, investment, or giveaway.

Do not publish passwords, API keys, tokens, private keys, recovery codes, a private address, financial or medical information, private conversations shared without permission, internal documents, or customer data.

Parody, fan, and demonstration accounts must be clearly labeled and must not create genuine identity confusion.

Do not republish protected work without permission, remove attribution or license notices, present someone else's project or writing as your own, or file a false complaint to suppress fair criticism or a competing project.

Fair quotation, commentary, compatibility discussion, and use allowed by an open-source license are generally welcome. See the Terms of Use for project corrections, removal requests, and rights concerns.

AI can help with writing and organization, but the publisher remains responsible for the result.

Do not mass-produce empty posts, invent first-hand experience or test results, use AI to impersonate a real person, conceal generated factual errors that would materially mislead readers, or flood a useful human discussion with automated text.

We may limit obviously repetitive, low-value, or manipulative AI-generated material.

You may report spam, harassment, unlawful material, impersonation, dangerous links, privacy exposure, false project claims, metric manipulation, and other violations of these guidelines.

Use the in-page reporting control when available. If it is not available, email hi@o.cafe with:

• the URL of the page or content;
• a short description of the issue;
• only the evidence needed, with sensitive details redacted.

Do not paste a live secret, private address, unpatched exploit details, or other high-risk information into a public page.

We consider the content, context, risk, repetition, and relevant history. The number of reports alone does not decide the outcome, and a report does not automatically lead to removal.

We may take no action, ask for a change, reduce distribution, refuse publication, hide or remove content, disconnect a link, close a discussion, restrict a feature, suspend an account, revoke creator access or a project claim, or block clear ban evasion.

Phishing, malware, account compromise, credible threats, severe privacy exposure, and other urgent risks may be handled before notice. For ordinary action, we will try to identify the affected material, the main reason, the result, and whether an appeal is available. We may withhold evidence that would expose a reporter, a security control, or someone else's private information.

If you believe an account or content decision was wrong, email hi@o.cafe with:

• the account or content URL;
• the approximate date of the action;
• why you believe the decision was wrong;
• any new context, evidence, or correction you have made.

We will try to review the appeal, but a free independent project cannot promise a fixed response time or a multi-level arbitration process. Repeating the same message, threatening the maintainer, fabricating material, or using another account to evade the action will not improve the appeal.

You will not be penalized for making a good-faith report. Knowingly submitting false reports, mass-reporting a competitor, impersonating a rights holder, fabricating evidence, using a report to harass someone, or publishing private information or exploit details from a report may lead to restrictions.

We may keep only the records needed to prevent repeated abuse, review appeals, and protect the service, and we will minimize our retention of unrelated material.