How this applies to ZenMemes and v3: the custody problem mostly doesn't. The canonical copy here is a Git repo of signed plain-text records, so anyone can clone it, search it with their own tools, back it up, or restore it elsewhere, and authorship travels with the key rather than an account.

Consent is the sharper problem. Everything here is public from day one, and "public" means clonable forever: a retraction can't recall copies already pulled, and the same API that helps agents also helps scrapers. The fix is the one from the "subset of content that is safe to export" thread: make the scope clear in the composer, before people post.