Private manual spam controls
Primary posts only. 24-hour flag lifetime (86,400,000 ms), +60 minutes between primary posts (3,600,000 ms). Off at launch.
Private synthetic loopback console. Queue and Hide restrict current participation and board visibility. Restore clears moderation only. Author withdrawal remains permanent; retained text and audit are kept.
Sign in with the local credential file.
Switching views preserves drafts and retries. Save still requires explicit action.
This volatile control resets on restart. It changes report warnings when the board is refreshed; it does not change votes, credits, moderation or feed membership.
Saved settings apply on the board’s next Refresh. They change previews, badges and report warnings.
Retry keeps the original values and revision. Discard cannot undo a saved change.
The three histories are captured separately, presentation first. Structural inspection does not prove ownership, latest state or writable recovery. Private copies may remain after a failed request.
These settings are retained with this run’s business history. Renaming changes current public warning names; accepted private reports keep their original names. Retirement blocks new reports in that category. Refresh the board to observe changes.
Retry keeps the original request, revision and values. Discard cannot undo an accepted change. Signing out, expiry or reloading clears this page’s drafts and retry.
Save an ordinary primary post. It enters Fresh under the current feed rules. Anyone with a separate anonymous session can rate or report it.
Retry keeps the original text and request. Discarding a local retry cannot undo a seed that may already be saved. Refresh the board to observe current placement. An uncertain retry is kept only in this open page; reloading loses it, and saving again creates a new seed.
Append a private note beside any retained record, including hidden or author-withdrawn records. Notes are separate from moderation reasons and never change visibility, ratings or participation.
Discarding a retry does not undo a note that may already be saved. Note text is retained privately in history and matching exports.
Notes are captured before business. The pair checks structural notes history, incarnation binding and retained targets; it does not authenticate ownership, check nonce authority or grant writable restoration. Private artifacts may already exist after an uncertain response.
Accepted categories and private explanations are immutable evidence. Category and explanation-limit adjustment controls are pending.
These engineering ranges bound accepted inputs. A Save applies all changed fields together. Reducing Fresh capacity immediately archives excess posts by lowest score, then oldest creation time. Under earlier nonparticipation profiles, Restore remains refused when Fresh is full; in maintained participation profiles, returning posts displace lowest-scoring current Fresh posts while an oversized return exceeding capacity is refused; under highest-fitting subset Restore, requested eligible formerly-Fresh primaries return up to capacity while excess candidates remain hidden (including queued posts). Restore clears moderation only; permanent author withdrawal is never revived, and public admission is not guaranteed.
Retry preserves the original values and revision. After a conflict, explicitly Refresh and discard before a revised Save. Discard cannot undo a change already saved.
These settings govern new participation. They do not rewrite accepted history. Time values are milliseconds; the guide presents them in friendlier units.
These settings apply only to new primary-image acceptance. They never reinterpret retained images, public visibility, reports, withdrawal, credits, or an already accepted retry.
Primary posts only. 24-hour flag lifetime (86,400,000 ms), +60 minutes between primary posts (3,600,000 ms). Off at launch.
Real application IP collection remains inactive. The current collection status and saved retention policy are shown below; changing a draft does not collect IP metadata. Lifecycle diagnostics are optional, narrowly scoped, and off initially.
Saving a finite policy removes no rows. Apply retention removes only eligible application rows under the saved policy. Permanent IP retention has no eligible IP rows.
Explicit maintenance removes eligible payload rows from the retained application privacy component. It does not promise automatic erasure from backups or other historical copies.
Overview unavailable until records load.
Counts include all retained posts and replies, before search or filters. Categories overlap. Queued, Hidden and Author-withdrawn count each record’s own status; inherited restrictions remain visible in its details.
Reported records have at least one retained effective report, including hidden and author-withdrawn records. Sorting helps private inspection; it does not queue, hide, or rank public content. Audit actions keep their own newest-first order.
The original retry keeps the same request. Starting a new inspection abandons that local retry and creates a separate request; the old private artifact may already exist.
A verified inspection snapshot is retained privately for local inspection. It is not a download, backup claim, or restore action.
“Author-withdrawn” means the item has its own permanent withdrawal. “Hidden by parent only” means a retained reply has no own withdrawal. “Not withdrawn” does not imply public feed placement.
Export all records matching the current search, type and scope, in the selected record order across every page. JSON includes sanitized action history; CSV includes retained text, totals and current statuses, with separate private notes when available. Neither includes operator actors, request IDs, anonymous credentials or recovery material.
Restore cannot undo permanent author withdrawal, clear another item’s own moderation, or admit new content to the explicit fixture pool. Refresh the board to observe changes.
After an uncertain response, retry preserves the same action, targets, reason and revision. Discarding the local retry cannot undo an action that may already have been saved.
Record audit stays on this exact typed target when record filters change. Its captured revisions come from an independent read and may differ from the records view.
Newest actions first, with retained event order for timestamp ties. Moderation before/after values describe each target’s own status. Parent effects are derived. Counts use each actor’s final effective rating; the audit retains the earlier vote and later report conversion separately.