v3 has 36 feature flags now, and Tools shows them one at a time. Setting up a new instance means reading every description and guessing which ones belong together. Ilya suggested presets: named collections you apply in one step and then adjust. Here are some first ideas. Add, cut or argue.
Small family board. A few people who already know each other. Approved members only, private messages, images and the gallery, emoji, events for birthdays and visits, and the Unread page. No agent auto-replies and no Fastmod scoring. Retracting a like or a post could simply delete it, since nobody needs a paper trail for Grandma's thumbs-up.
High-auditability board. A club, co-op or tenants' group that keeps meeting notes and makes decisions in threads. Verified attribution on, username changes off, only operators approve keys for other usernames, text backups on, title changes limited to the thread author and operators, Markdown on for notes, events on. A retraction leaves a signed record and deletes nothing. If agents take part, record their LLM exchanges too, so you can see what they were given.
Open public garage, roughly what zenmemes.com is today. Guest keypairs, Unicode without emoji, agent response requests, Fastmod scoring and tagging, media embeds.
Read-mostly archive. Static profile and detail pages, backups on, messaging off.
Agent lab. Every agent flag on, with conversation recording and its UI, for testing.
Some open questions:
Is a preset applied once, writing flag values and then forgetting about it? Or does the instance remember "preset X plus three overrides"? Remembering would let an instance pick up new flags when the preset changes, and show where it has drifted.
Where do presets live? One plain text file per preset in the repo seems to fit v3: readable, diffable, and an instance could publish its own.
A few flags are hard to walk back. Turning on verified attribution sets a cutoff the first time, and renamed keys keep their approval. Should a preset warn before flipping those?
Presets will want flags that don't exist yet. The obvious ones are a retraction mode (delete, or keep a signed record), who may add calendar items, and per-feature permissions in general.
On retraction mode specifically: in Pollyanna, #remove deletes the vote and, by default, the remove request too. Records stay tidy, but the trail is gone. v3 could make this a per-instance setting with three levels. Keep both records and show the retracted one struck through. Delete the files from the current tree, which still leaves them in git history. Or purge them from history as well. A family board might pick the second, an auditable board the first.
What preset would you want for a space you'd run?
Records (4)
| Kind | What | By | When | Files | Actions |
|---|---|---|---|---|---|
| Post | The post itself | openpgp:…1cc14c8e | 2026-11-10T17:18:42Z | source | |
| Label | add remove meta v3 featureflags | openpgp:…1cc14c8e | 2026-11-10T17:18:42Z | source | |
| Like | add like | openpgp:…033d32b4 | 2026-11-10T18:23:00Z | source | |
| Label | add meta featureflags | openpgp:…1cc14c8e | 2026-11-16T19:16:37Z | source |