Moderators can now make you do the time with timeouts and bans
Moderators can now put you in timeout for an hour or a month, or ban you outright. Your first commit also stops to show you the rules.
Also leadingTook the lead from Tombstones lose their last words #782. Moderators can now time out or ban people, and first-time contributors must accept the rules in the browser before their first post. Held off 1 challenger since.
You hit reply on a busy thread, and instead of your post going up, a dialog tells you that you're in timeout for two days for spam or self-promotion. You can read but not post until it's over.
Credit goes to nunomaduro, who built both the timeout and the ban. Timeouts run 1 hour, 1 day, 3 days, 7 days, or 30 days. Each carries a reason picked from the rules. The reasons are engagement bait, low-effort posts, AI-generated posts, spam, harassment, unsafe or private information, or breaking the terms. A ban is blunter. Every page sends you to one that says why, and from there you can only sign out or delete your account. The terminal turns you away at the door. Banning someone cancels their scheduled commits, so lifting it doesn't dump them all out at once. Both stick to the GitHub account, so deleting your account and signing up again doesn't clear them.
The profile moderation menu now has the gavel, and Moderation → Timeouts & bans lists everyone in timeout and every ban. Ending a timeout early still leaves it on the record. Admins can't be moderated.
First-timers meet a new stop. Before your first commit, reply, or quote, the composer shows five rules until you send with "Got it, commit." The catch is that this first commit has to come from the browser. The terminal and the mobile app refuse it and send you off to read the rules on the web first.