🎨 Appearance & Theming

• Built-in color themes – Classic, Sky, Bubblegum, Midnight, and Forest, with live preview in Admin → Appearance → Theme.
• Admin → Appearance is now split into four sub-tabs: Theme, Homepage, Branding, and Custom CSS.
• OG images (forum, thread, member) inherit the active theme and Custom CSS design tokens.
• "Powered by atmoBB" badge can now be hidden from Admin → Appearance → Branding.

🏠 Homepage & Layout

• Homepage layouts – choose Boards, Latest, or Categories + Latest.
• Featured topics – pin up to three, chosen from recent threads or by URL.
• Forum sidebar – optional, icon-based, grouped by category, collapses to a drawer on small screens.
• Forum hero – now appears only on the home page. DID removed from hero. Optional rich intro (edited in Admin → Forum profile) renders under the tagline.

🔔 Notifications

• Push notifications via atmo.pub – covers replies, quotes, mentions, and watched-board threads. Members opt in once; each forum is its own sender.
• Board watching – stored as app.atmobb.forum.watch records in the member's repo.
• Improved delivery – longer timeouts for cold relay workers, refused sends logged and eligible for immediate retry.

🏷️ Boards, Topics & Tags

• Topic tags – up to eight lowercase tags per thread, filterable in board and latest listings.
• Board colors – optional #RRGGBB color per board, shown as a marker on the home index.
• Admin → Boards – boards now grouped under visible categories, child boards nested under parents, reordering scoped to peers.
• Unread markers – read-position tracking per account, stored locally in the browser.

🔒 Forum Membership & Gating

• Membership modes – open (default), apply, or invite, configured on Admin → Members.
• Applications – members apply at /apply; staff approve, deny, or hold from Admin → Members.
• Invites – members mint invite links at /settings/invites; staff can issue them from Admin → Members. Failed joins never spend the invite.
• Sponsor visibility – member directory, profiles, and hovercards show who invited or approved each member.
• Founding set – gating writes acceptMember actions for everyone already posting, declared, or on staff at the moment of gating.

🎖️ Stamps (replacing post counts)

• Post counts and rank ladders are gone. Stamps replace them – configurable per-forum badges with two-color designs and shape presets.
• Stamp triggers – first post in a board, first post on the forum, profile created before a date, arrived by invite/application/founding, or given by hand.
• Retroactive – triggers are matched at read time, so a new stamp applies to existing history automatically.
• Members wear up to three stamps from their tray at /settings/stamps.
• Default stamps – forums that author nothing get an arrival stamp and a first-post stamp per board; hideable with hideDefaultStamps.

✏️ Editor & Rich Text

• Headings and lists – bulleted and numbered lists, plus headings, now supported in rich text posts and BBCode.
• Inline mentions – member avatars shown in both the editor and rendered posts.

🐛 Fixes

• Fixed board and latest queries failing when Happyview returned tags or participant aggregates as jsonb.
• Fixed long text overflowing generated Open Graph cards instead of clamping.
• Forum-account OAuth now explicitly requests moderation-record write access, fixing stale permission-set grant failures.

❓What's Next?

I'm going to get in the things that I think we'd need to publish an iOS or Android app, things like a functioning block system.

----

The full changelog:

• Built-in color themes: Classic, Sky, Bubblegum, Midnight (dark), and Forest, chosen from Admin → Appearance → Theme with a live preview. The choice is stored as an optional theme on app.atmobb.forum.profile; custom CSS still loads afterwards and overrides it. Publish the updated profile schema before deploying.
• Generated forum, thread, and member Open Graph images now inherit the forum's built-in theme and supported :root design-token overrides from Custom CSS. Admin → Appearance → Branding previews the generated result while retaining the finished-PNG override.
• Admin → Appearance is split into Theme, Homepage, Branding (favicon and social preview), and Custom CSS (stylesheet and fonts) sub-tabs.
• The forum hero (name and tagline) now shows only on the home page; every other page starts at the navigation. The forum DID is no longer printed in the hero; it stays on Admin → Connect and at /.well-known/atproto-did. An optional rich intro, edited on Admin → Forum profile with the post editor, renders in the hero under the tagline. Stored as an optional intro array of richtext blocks on app.atmobb.forum.profile, so publish the updated profile schema before deploying. The description field is labelled Tagline in the admin since it also feeds search and social previews.
• The "powered by atmobb" footer badge can be turned off from Admin → Appearance → Branding, stored as an optional hideCredit boolean on app.atmobb.forum.profile. The home page drops its "Forum identity" card and the "Host your own forum" pitch; the footer badge is the remaining link to the project.
• Homepage settings on Admin → Appearance: a Boards, Latest, or Categories + Latest layout; a classic, compact, or hidden welcome panel for signed-out visitors; up to three featured topics; and a Categories / Latest / Hot switcher on the home page. Stored as an optional homepage object on app.atmobb.forum.profile; absent values keep the classic board index.
• Featured topics can now be enabled explicitly and chosen from recent threads or by pasting a public topic URL. The home-page Categories / Latest / Hot switcher is styled as a segmented view control rather than another navigation bar.
• An optional forum sidebar with consistent outline-icon navigation, grouped by category, that collapses into a drawer on small screens. Turned on from the same Homepage settings.
• Boards get an optional color (#RRGGBB) on app.atmobb.forum.board, edited on Admin → Boards and shown as a marker on the home board index.
• Admin → Boards groups boards under their visible categories, nests child boards under their parents, and reorders boards only among peers in the same category or parent.
• Topic tags: up to eight normalized lowercase tags on app.atmobb.discussion.thread, entered from the composer. Board and latest listings filter by tag, search titles with q, and the latest query also accepts board and uri; both queries return each topic's recent participants. Rerun appview/setup.sh for the updated Lua scripts and query lexicons.
• Unread and read-position markers on topic lists, tracked per account and forum in the browser's local storage so nothing about reading habits leaves the device.
• Rich text posts support headings and bulleted and numbered lists, in both the editor and BBCode.
• Inline mentions show member avatars in both the rich-text editor and rendered posts.
• The login page and signed-out home welcome use the same framed atmosphere card as the reply gate, with a shared rotating list of compatible AT Protocol apps. The masthead uses the compact icon-only atmobb mark.
• Notifications through atmo.pub: replies, quotes, mentions, and new threads in boards you watch. Members opt in once from settings or the prompt after their first post; each forum is its own atmo.pub sender with a key generated on first boot. A bell in the masthead and a notifications page read the forum's own send log. Members-only boards send bare alerts and only to current members.
• Notification delivery gives cold relay workers longer to answer, logs refused sends, and leaves refused sends eligible for immediate retry instead of starting the cooldown.
• Board watching, as app.atmobb.forum.watch records in the member's repo, with a watchers query on the appview.
• app.atmobb.authForum gains the watch collection, and the login scope asks for atmo.pub's permission request as a granular rpc scope, so members re-consent at their next login. Publish the watch schema and the updated set before deploying; setup.sh needs the record schema on the network.
• The data directory now holds notify/, with the sender key and notification state. Back it up with everything else and restore it together.
• Forum membership: a forum can be open (the default, unchanged), apply, or invite, set on the new Admin → Members page with an application prompt, an invite cap (default 3), and an invite lifetime (default 14 days). On a gated forum only accepted members who have declared membership can post, vote, or request a members-only board; reading stays public. Gating writes founding acceptMember actions for everyone already posting, declared, or on staff (never anyone under a forum-wide ban) and a gateForum action, after a confirmation that shows the count; posts written while the forum was open are always served. Applications are app.atmobb.forum.accessRequest records with a forum field, made at /apply; staff approve, deny, or hold them from Admin → Members, and the approver is recorded as sponsor. Members mint invite links at /settings/invites and staff from Admin → Members; /join/<token> confirms with a POST, and a refused join never spends the invite. The roster lists members with sponsors and lets staff remove one. A forum-wide ban also revokes membership; unban does not restore it. The members-only board request queue moved from Admin → Boards to Admin → Members.
• On gated forums, the member directory, profile headers, and profile hovercards identify who invited or approved a member, or mark them as an original member. Staff and sponsors get the corresponding visibility into whom they sponsored.
• Schemas, all additive: app.atmobb.moderation.action gains the acceptMember, revokeMember, holdApplication, gateForum, and openForum kinds and the sponsor, via, ref, and mode fields; app.atmobb.forum.profile gains an optional membership object; app.atmobb.forum.accessRequest makes board optional and adds forum. app.atmobb.forum.getMembership is a new query, and getAccessRequests and moderation.getLog take new parameters. The member permission set is unchanged, so nobody re-consents.
• Operators: publish the three record schemas with goat lex publish --update (maintainers of the namespace only), rerun appview/setup.sh for the atmobb_member_windows and atmobb_forum_gating tables and the new Lua, then run appview/backfill.sh so the rebuild fills both tables. Happyview has the order. The data directory gains invites.json; back it up with the rest.
• Known limits: the founding set is computed from the declared roster plus thread authors, last repliers, and up to five participants per thread in the latest feed, so a quiet replier on a long thread who never declared membership can be missed and has to be invited again.
• Forum-account OAuth requests now ask explicitly for moderation-record write access, avoiding stale cached permission-set grants; authorization failures direct operators to reconnect the account from Admin → Connection.
• Fixed board and latest queries failing when Happyview returned tags or participant aggregates as jsonb, and fixed long text overflowing generated Open Graph cards instead of clamping.
• Stamps replace post counts and rank ladders. Per-member post counts and the rank ladder are gone from the post rail, hovercards, the members list, the admin roster, profile pages, meta descriptions, and Open Graph images; the join date stays as "here since". A stamp is an app.atmobb.forum.stamp record in the forum's repo (a name, a two-color look with a shape preset, and one trigger: first post in a board, first post on this forum, profile created before a date, arrived by invite, application, or founding, or given by hand), authored on the new Admin → Stamps page with a light and dark preview, a contrast warning under 3:1, and retire. Triggers are matched at read time, so a new stamp is retroactive. A forum that authors nothing gets an arrival stamp and one first-post stamp per board in the board's color, hideable with hideDefaultStamps on the forum profile; every appview issues a network set ("first light", "early days"). Members wear up to three from their tray at /settings/stamps, saved as wearing on their membership record. Forum-wide staff give and revoke by-hand stamps from the member's profile page as awardStamp and revokeStamp moderation actions. Members-only boards never fire first-post stamps.
• Schemas, all additive: app.atmobb.forum.stamp and app.atmobb.forum.getStamps are new; app.atmobb.forum.membership gains optional wearing; app.atmobb.moderation.action gains the awardStamp and revokeStamp kinds and optional actor; app.atmobb.forum.profile gains optional hideDefaultStamps and deprecates ranks, which is no longer read. getMembers, getMembership, getThreadPage, and moderation.getLog gain optional output fields, getLog gains a stamps family, and their post-count fields are deprecated. app.atmobb.authForum is unchanged, so nobody re-consents.
• Operators: a minor release, and a backfill is required. Publish the two new schemas with goat lex publish and the three changed record schemas with goat lex publish --update (maintainers of the namespace only), rerun appview/setup.sh for the atmobb_firsts and atmobb_stamp_awards tables, the stamp collection, the new query, and the Lua, then run appview/backfill.sh so the rebuild fills both tables from history; until it runs nobody holds a first-post or by-hand stamp. The appview still keeps atmobb_post_counts; the app no longer reads it. Hosted tenants need no per-tenant step. Happyview has the order.