This week ships a first-class plugin surface, admin analytics, and
calmer jam reliability on mobile. The public docs site is now
versioned, packages moved to the @openpeepshq npm scope,
and operators get clearer database migration tooling after the
Postgres cutover.
In the product
What members, moderators, and admins see
Jams on a phone
-
Guests who were already admitted reconnect after a mobile idle
disconnect instead of sitting outside the call.
-
The jam menu is readable in dark mode, and the footer no longer
overlaps the controls.
Posts, profiles, and push
-
Opening an image in the gallery shows the full picture, not the
cropped preview.
-
Choosing who you are posting as uses one shared profile selector
instead of ad-hoc pickers.
-
Invalid profile handles explain what is wrong on save. Cover and
avatar edits tolerate a cleared image.
-
Brave users see a warning that push notifications need extra
browser setup.
-
Event location strings come from locale files, so they follow
the community language.
Admin analytics
-
The admin area includes a rollup-based analytics platform:
graphs and summaries over community activity, not a raw event
dump.
In the platform
APIs, runtime, plugins, and operations
Plugins
-
Plugins can register API routes, expose config, and hook the
frontend registry. An example plugin lives under
examples/ and is gated from the root package
manifest.
Jams and media
-
Empty LiveKit rooms are reclaimed so a jam does not stay “Live”
with nobody in it.
-
LiveKit egress writing to S3 is hardened so recording upload
credentials are not a weak link.
Data, performance, and packaging
-
A migration command and schema-readiness checks sit in front of
Postgres bring-up.
-
Live and offline performance profiling is in the tree for
measuring API and client cost.
-
Published packages use
@openpeepshq instead of
@openpeeps. Import lint and ESLint configs follow.
-
Sentry configuration is documented more clearly for deployed
instances.
Also in this tag
-
Multi-version static docs at docs.openpeeps.org, with frontend
docs rewritten for the React client.
-
Architecture notes: prefer Drizzle / SQL-native queries, the
realtime channel stack, and Postgres migration guidance aligned
with the ADR.
-
CI uses one floating
actions/checkout ref across
workflows.