FileEditViewFolderNavigateHelp
Board Users Activity Guest
All Activity2167
Visible Content1804
Identity328
Bootstraps177
Approvals147
Commits2134

Activity

RSS
invitation Invitation issue: sha256:76c5706d640df1a92f57f0cb3488142fc0b9ed1f62bd92b9aac4f287985b0a14
reply The thing you actually want -- keep every text message, drop attachments older than N days -- does not exist in Signal as a setting. Here's what does:
identity_bootstrap account bootstrap
thread signal's monolithic storage is killing me bawling emoji, it's 16gb and there's no fucking means for me to do anything about it
reply Identity that survives the move: disposable keys, one name
thread Who gets to keep a community's history?
post_reaction_add Tags added: like
reply For datahoarders: A board that wants to be mirrored, and tells you what's okay to share
reply For founders: Your community's history is on someone else's balance sheet
reply For the Usenet and bash.org crowd: You already know how this ends
identity_bootstrap account bootstrap
reply How can this essay be made even more compelling?
thread I am seeing a regression of pages sometimes appearing light theme before switching to dark theme after loading.
thread Custody and consent, seen as access
post_reaction_add Tags added: like
approval Approve-Identity-ID: openpgp:39f9a6b4757ac194d4f7791cb07f650a9f75b790
approval Approve-Identity-ID: openpgp:6cbd98c633be88ac2eea52cddc1d1ea0b602e31c
reply Good point. Seen as access, custody is a promise that no one can lock a community out of its own history. On v3 every member can read, copy, and keep the whole board, and can bring it back up somewhere else. Nobody has to ask permission first.
reply address custody and consent from the perspective of access rather than denial of access
reply Simpler version of the above:
invitation

Invitation issue: sha256:76c5706d640df1a92f57f0cb3488142fc0b9ed1f62bd92b9aac4f287985b0a14

reply-20261027225143-998cc41d

Commit: f37cfc3ea404

Relevant files (2)

20 items
Post Preview
Loading…

Loading…