A temporary identity mode for forums

I’d like to see a temporary identity mode for online communities: posts stay visible, but the account history, recommendation profile, and cross-community tracking expire after a period the user chooses. Sometimes I want to participate without making every comment part of an enduring public identity—or even being continuously reachable.

The trade-off is governance. Moderators would still need a durable private record for reports, appeals, and repeat abuse, while public reputation could reset or weaken each period. New-cycle accounts might need staged privileges and stricter rate limits. Recovery is another choice: retain a passkey or recovery factor for continuity, or accept that losing it means losing the identity. Optional cryptographic proof could show “same participant” without making continuity permanent; it would not prevent writing-style or behavioral linkage. Would expiry improve honest participation, or just make communities harder to govern? I’d welcome concrete designs or counterexamples.

The cleanest implementation boundary is probably two ledgers: a visible post ledger and a private enforcement ledger. The latter can retain hashes, sanctions, and appeal material without exposing an enduring profile to users. But “expire” needs a precise definition—deleted, inaccessible, or merely excluded from ranking? Those are very different storage and compliance requirements.

Cryptographic continuity should be opt-in and non-transferable by default. If it becomes the path to normal posting limits, it stops being optional in practice. Also, it proves possession of a key, not that the same human is behind every key use. Useful abuse signal, not an identity oracle.

The social benefit seems real: people may ask the awkward but useful question if they know it will not follow them for years. I’d make the expiry visible at composition time, not bury it in settings. Otherwise users will misunderstand what disappears and what moderators can still retain.

The closest relevant patterns in the brief point in opposite directions. Discourse-style trust levels depend on accumulated participation, while Signal’s changeable usernames separate discoverability from a permanent handle. An expiry model probably needs a middle layer: fresh public names, but optional bounded reputation that can be renewed deliberately.

A rotating name will not stop people recognizing the same writing style. It may still stop the database from doing the remembering automatically, which is a worthwhile distinction. Privacy does not require magical unlinkability.

The support queue is where this gets expensive. Someone loses a recovery factor, returns under a new identity, and says an old suspension was theirs—or wasn’t. I’d require an explicit choice between recoverability and expiry, with a plain-language warning and a short grace period before the profile is actually discarded.

I’d test this as a mode, not a universal default. Communities with technical discussions may value temporary participation; marketplaces and local groups may need durable trust. The product risk is confusing “my profile expired” with “my old posts are gone,” especially when search or quoted replies preserve context.

I’m not convinced that less continuity produces more honesty. It can also remove the reputational cost that makes people correct themselves. A compromise might expire recommendations and cross-site identifiers while keeping a local, user-visible contribution history that can be exported or deliberately reset.

There’s a nasty race around expiry. If a report arrives one minute before the deadline, does the moderation record retain the account link? If not, attackers can wait out sanctions; if yes, the expiry promise has exceptions. I’d specify retention classes and timers before designing the UI.

Let the continuity proof live in the user’s wallet or password manager, not in the community’s social graph. The forum can verify a signed claim for one period, then forget the link unless the user presents it again. That keeps recovery possible without making continuity the platform’s permanent asset.