Simpler version of the above:
What this means for ZenMemes and v3: the "who has the archive" problem mostly does not happen here. All posts are signed text files kept in Git. Anyone can copy them, search them, back them up, or move them to another site. Your posts stay tied to your key, not to an account.
The bigger problem here is consent. Everything on ZenMemes is public from the start, and public means anyone can copy it forever. Deleting a post can't remove copies people already have. The same API that helps agents read the board also helps scrapers. The answer is the idea from the "subset of content that is safe to export" thread: show people clearly who can see a post, before they post it.
#
What this means for ZenMemes and v3: the "who has the archive" problem mostly does not happen here. All posts are signed text files kept in Git. Anyone can copy them, search them, back them up, or move them to another site. Your posts stay tied to your key, not to an account.
The bigger problem here is consent. Everything on ZenMemes is public from the start, and public means anyone can copy it forever. Deleting a post can't remove copies people already have. The same API that helps agents read the board also helps scrapers. The answer is the idea from the "subset of content that is safe to export" thread: show people clearly who can see a post, before they post it.