Invitations
Invite by shareable link or to a single address. Expiry and use limits are enforced in the database rather than by not showing the link, so a link that has run out genuinely stops working.
WHAT SHIPPED, AND WHEN
The record,
kept in public.
Dated from the day each change reached production. Anything that is being built rather than running is at the bottom, and anything on neither list is not built.
6 September 2026
One sign-in across every community address
A host who signs in at the app now stays signed in on their own community’s address. Sessions previously stopped at the host they were created on.
Email from our own domain
Sign-in links and notifications now send from success.digital with sender authentication in place, so they arrive rather than landing in spam.
September 2026
Direct messages
Private messages between members, with three rules enforced in the database rather than the interface: a host cannot read them, a conversation link is not an invitation, and a conversation belongs to one community. Notifications record who wrote, never what was said.
Search
Across posts, spaces and channels — and across people for members. Every query runs on the caller’s own session, so results can never disagree with what that person is allowed to see.
Moderation, with an audit log
One queue for reports and join requests, oldest first. Pin, hide and delete each take a confirmation step, and every decision is written down.
Photos on posts
Stored privately with no public read access at all. The server signs a short-lived link, and only for a post the reader could already open.
Nine themes
Chosen by the host and applied to the whole community without a deploy. Accent, tagline and the word for a shared space are stored as data.
Community settings
Name, tagline, vocabulary, visibility, indexing and modules, all editable by the host.
Roles
Host, moderator and member, at both community and channel level. Isolation between communities is enforced by row-level security.
A phone layout
Five destinations at most in the bottom bar, and never a horizontal scroll.
In build
The product’s own visual system, rolling across every screen.
A platform admin desk, where every visit to a community is written somewhere its host can read.
Events, courses and payments are designed and undecided. When they are built they will appear above this line with a date on them, not below it as a promise.