johnandersen777.bsky.social/knotless

Switch repository

Loading…

<script lang="ts">
	import Meta from '#lib/atoms/Meta.svelte';
</script>

<Meta title="community guidelines · knotless" />

<article class="policy">
	<h1>Community guidelines</h1>
	<p class="updated">Last updated: October 27, 2026</p>
	<p>
		knotless.dev is a place to build software together in the open. Treat people the way you would
		want to be treated in a code review, and use the service for what it is for: code, and the work
		around it.
	</p>
	<p>
		These guidelines apply to everything knotless.dev shows and runs: repositories, pulls, issues,
		comments, profiles and CI. They apply to people and to the agents that act for them. They are
		part of the <a href="/terms">terms</a>.
	</p>
	<h2>Not allowed</h2>
	<ul>
		<li>
			Anything illegal where you or knotless.dev are, including sharing code or content you have no
			right to share.
		</li>
		<li>Child sexual abuse material, in any form.</li>
		<li>
			Harassment: targeting a person with abuse, piling on, or following them across repositories
			after being asked to stop.
		</li>
		<li>
			Hate: attacking people for their race, ethnicity, religion, gender, sexual orientation,
			disability or similar traits.
		</li>
		<li>Threats of violence, or encouraging others to harm someone.</li>
		<li>
			Doxxing: publishing someone's private information, such as a home address, without their
			consent.
		</li>
		<li>Impersonating a person, project or organization in a way meant to mislead.</li>
		<li>Spam: unwanted promotion, link farms, or repeated posts that add nothing.</li>
		<li>Malware served to people to harm them or their machines.</li>
		<li>Abusing compute, on the runners or anywhere else.</li>
		<li>Evading moderation, such as making a new account to come back after a takedown.</li>
	</ul>
	<h2>For a code host</h2>
	<p>
		Hosted CI is for building and testing the code in the repository. Don't mine cryptocurrency or
		use the runners as general compute, and don't attack other systems from CI.
	</p>
	<p>
		Security research is welcome. Exploits, proofs of concept and malware samples kept for study are
		allowed. Live malware served to people who don't know what it is, or a repository set up to
		spread it, is not.
	</p>
	<p>
		Don't mass-generate repositories, pulls, issues or stars. Generated code is fine when it is
		meant to be useful; a stream of empty or near-identical items is spam whoever wrote it.
	</p>
	<p>
		An account's agents, such as MCP clients and bots, are its owner's responsibility. They follow
		the same rules as people, and what they do counts as the owner's doing.
	</p>
	<h2>How moderation works</h2>
	<p>
		Anyone logged in can report an account, a repository or a single record with the report action
		in the app. The knotless project's maintainers read reports and decide what to do.
	</p>
	<p>
		When something breaks these guidelines, the maintainers can take it down. It leaves the index,
		its pages and clones answer "not found", and it is published as a <code>!takedown</code> label. A
		takedown of an account also stops it logging in to knotless.dev. The records themselves stay on their
		author's PDS, the server that hosts their atproto account: knotless.dev cannot delete them, only stop
		showing them.
	</p>
	<p>
		Owners moderate their own repositories. An owner can hide a pull, issue or comment, or block an
		account, and readers of that repository then don't see it there. Nothing is deleted, and it
		stays in its author's account.
	</p>
	<p>
		The maintainers may also take moderation labels into account from labelers elsewhere on the
		network.
	</p>
	<h2>Reporting</h2>
	<p>
		Log in, use the report action on the account, repository or record, choose a reason, and say
		briefly what is wrong. Report the specific record where you can, rather than the whole account.
		If something puts someone in danger, contact local authorities as well.
	</p>
	<p>Reports go to the maintainers, not to the person reported.</p>
	<h2>Appeals</h2>
	<p>
		If you think a takedown was wrong, open an issue on the <a
			href="https://knotless.dev/chadtmiller.com/knotless/issues"
			rel="noopener noreferrer">knotless issue tracker</a
		>. Say what was taken down and why it should come back. If your account can no longer log in,
		open it from another account. The maintainers will look again and answer there.
	</p>
	<p>
		If an owner hid your item or blocked you on their repository, that is their call to make on
		their own project. Your records are still yours, on your PDS.
	</p>
</article>