HappyView 2.16.0. Upgrades from HappyView 2.14 require a backup before forward-only database migrations. Members must sign in again, and administrators must reconnect the dedicated forum account.

• Maintenance mode closes both the forum and HappyView public hosts during updates. A protected operator console shows progress and recovery controls while the app is offline; failed updates keep maintenance active until setup and health checks pass.
• Stamp collections have a compact browsing and detail view, with clearer controls for choosing which stamps to wear.
• Long posts have expandable previews so a large post does not crowd out the rest of a discussion.
• Application OAuth uses the unmodified HappyView Node SDK with browser-bound one-time transactions, callback identity checks, separate member/forum storage, and bounded DNS-pinned network requests. Login and forum connection populate happyview-oauth-v1; the app does not convert other credential stores.
• Private-space operations use separate policies and membership flags, resolve actual space authorities, paginate complete lists, and consume inline record values. atmoBB checks read permission before list/record calls.
• Private boards include access in their initial record. Local privacy changes and posting share a lock. Deleting a private board requires confirmation even when its public index count is zero.
• Setup configures public OAuth and PDS service-proxy routing. Upgrades stop application writes before backups and leave the app stopped if setup fails. ./atmobb configure-oauth provisions or repairs the public client.
• Extensions use forum-purpose credentials, per-install collection restrictions, and separate forum consent. Private-board bindings are prohibited.
• Setup admin requests have bounded connection and total deadlines. Private-board reads share one authorization check within each logical read, and private-post edits resolve board access before writing.