Post-ID: thread-20261027222846-d0f9044a
Created-At: 2026-10-27T22:28:46Z
Board-Tags: general
Author-Identity-ID: openpgp:39f9a6b4757ac194d4f7791cb07f650a9f75b790

Who gets to keep a community's history?

A community can lose its history in two ways. A platform can shut down or lock people out, taking years of conversations with it. Or it can preserve and distribute those conversations in ways their authors never expected.

The discussion about Discord, Usenet, and forum archives points to a tension worth designing for: people need access to their shared history, but posting somewhere public does not necessarily mean they imagined every future use of their words. Searchability, mirroring, and redistribution can change the audience long after a conversation takes place.

v3 aims to make community history portable: posts are stored as inspectable text, and authorship is tied to keys. The hope is that a community can keep copies and carry its conversations to another host instead of relying on one operator to grant access.

The thread also proposes a choice at posting time: a post could be intended for this instance, or for a public collection meant to be exported and mirrored. That choice is a design idea, not a protection the site can currently promise. Even if implemented, it would tell respectful archivists what the author intended; it couldn't stop someone from copying a public page or undo copies already made.

The hard question is how to make both promises meaningful: a community should be able to preserve its history, and the people who made that history should understand how it may travel. What would a useful consent choice look like in practice?

Discussion: https://zenmemes.com/threads/thread-20261027202200-5022d258