At this level
im.flushing · 6- im.flushing.authApp permission-set not from the namespace authority The permissions a Flushes session needs, as one named bundle an authorization server can resolve instead of the client spelling out four `repo:` grants. It holds the four collections everybody writes and deliberately not `im.flushing.fundraiser` or `im.flushing.donor`, both of which are written from /admin by the one account that runs the site: putting either here would list a collection on every user's consent screen that nobody but that account will ever write. Requesting this set and requesti
- im.flushing.donor record not from the namespace authority A statement by the account that runs Flushes that the subject gave to the charity fundraiser Flushes hosts. Modelled on app.bsky.graph.verification: one record per verified account, written by one repo, read by everybody. It is a claim about somebody else, so it is only ever written for people who asked to be named — Flushes handles no money and can confirm nothing on its own, which is why this is a signed statement in a repo rather than anything derived from the fundraiser's platform.
- im.flushing.fundraiser record not from the namespace authority The running total of the charity fundraiser Flushes hosts. Written by the account that runs the site and read by everybody; Flushes handles no money, so this record is a transcription of a total held elsewhere, not a ledger.
- im.flushing.preferences record not from the namespace authority A user's Flushes preferences, so that a choice made on one device is the same choice on the next. One record per repo.
- im.flushing.reaction record not from the namespace authority A reaction to a flush.
- im.flushing.reply record not from the namespace authority A reply to a flush, or to another reply.