Skip to content

Releases

v0.1.0-alpha.2

v0.1.0-alpha.2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 12 Nov 04:50
25971ae

Clients

  • Add Windows x64 and ARM64 NSIS installer builds to CI and release publishing,
    with native Rust runtime tests on both architectures and SHA-256 checksums.
    Installers are currently unsigned.
  • Add a native Windows launch presentation without layered-window startup overhead.
  • Align Android native libraries for 16 KB page-size devices and improve notification
    badges and launcher-specific guidance.
  • Add macOS and Linux alpha clients, desktop notifications, and a macOS Dock unread badge.
  • Unify native notification policy in Rust and align Web delivery, cooldowns, and
    click navigation. Silently restore surviving cards on restart where supported;
    Linux starts fresh without clearing old cards. Warn on uncertain delivery results
    without blocking later notifications.
  • Add system notifications for friend and group join requests across Web, desktop,
    and Android, with clicks opening the corresponding request list or review panel.
  • Coordinate Web service-worker updates and session restoration to avoid startup
    races between authentication, push registration, and notification delivery.
  • Fix Android startup hangs and native login restoration by making Rust the single
    owner of credential activation and session transitions.
  • Fix native profile and avatar updates, account cache initialization, and namespace
    catch-up when an empty page is already current.
  • Preserve conversation drafts and composer state across message-window jumps and
    initial-load retries. Cancel abandoned window requests without cancelling
    account-level uploads or already-admitted database commits.
  • Reconcile refreshed messages and deletion notices without moving the reading
    position, and persist deletion markers so stale cached messages do not reappear.
  • Improve synchronous cached-history pagination, message navigation, contact lookup,
    mentions, responsive layouts, and playground regression coverage.
  • Rework login methods with a Material 3 segmented selector and runtime language updates.
  • Improve native calls, SSE reconnection, Android launch presentation, and retryable
    voice-upload handling.

Server and deployment

  • Prevent duplicate mirrored-group leave notices by resolving member ownership
    in the origin's namespace coordinates before applying local notification policy.
  • Prevent group creation from generating a spurious invitation or unread request
    for the founding owner.
  • Expand administrator user, session, media, and federation diagnostic tools.
  • Unify daily quotas and add configurable per-file size limits.
  • Add TLS-ALPN-01 certificate challenges for standard-port deployments through
    CADDY_CERT_MODE, alongside the existing certificate modes.
  • Generate Caddy configuration in TypeScript at supervisor bootstrap, with golden
    configuration checks and real routing tests.
  • When a separate Web domain is configured, serve federation only on the identity
    domain and application routes only on the Web/LAN domains. Deployments without
    a separate Web domain keep the combined surface.
  • Extend CI coverage for native IPC permissions, Rust and Android contracts,
    PostgreSQL integration, deployment tooling, and browser lifecycle behavior.
  • Update federation to SOMFP 1.0.0-draft.2; see the protocol changelog.

Compatibility and upgrade

  • SOMFP draft.2 is incompatible with draft.1. Upgrade peers together and use matching
    alpha.2 clients and servers.
  • Discovery moves from /.well-known/somfp to /somfp/discovery; federation APIs
    move from /s2s/v1/* to /somfp/v1/*. The old routes have no compatibility aliases.
    Update custom reverse proxies and monitoring probes before switching traffic.
  • With a separate Web domain, clients must use the application domain rather than
    the federation-only identity domain. DNS SRV changes the connection destination,
    not the identity domain used for TLS validation, SNI, or HTTP authority.
  • Alpha.1 databases cannot be upgraded in place. Back up needed data and use a fresh
    test database; do not bypass migration checksum checks.
  • See the deployment guide for certificate modes,
    domain configuration, and routing requirements.

v0.1.0-alpha.1

v0.1.0-alpha.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 25 Oct 00:03
d24cc39
  • Add a Docker Compose configuration generator for public and LAN/NAS deployments.
  • Improve container startup, automatic database migrations, and multi-platform image publishing.
  • Add administrator account security controls and improve user management.
  • Expand network self-checks with public IP detection, DNS checks, and federation diagnostics.
  • Allow runtime log output levels to be managed from the administration console.
  • Update the federation profile contract to SOMFP 1.0.0-draft.1.
  • Fix web client asset loading on sub-path deployments and deep links.
  • Fix profile resolution and login configuration handling.

SOMS v0.1.0-alpha.0

SOMS v0.1.0-alpha.0 Pre-release
Pre-release

Choose a tag to compare

@hapood hapood released this 22 Oct 23:27
3d7ff9c

SOMS v0.1.0-alpha.0

The first public alpha of Simple Open Messaging Service: self-hosted messaging, a web client,
an administration console, and federation between independently operated servers.

This is a prerelease. SOMS and the SOMFP federation protocol are under active development, and
the wire contract remains subject to revision before a stable release.

This release distributes server container images. Android APKs are not included.

Deploy the server

The container includes the API, web client, administration console, Caddy TLS edge, and database
migration runner. Docker selects the appropriate image for linux/amd64 or linux/arm64.

docker pull ghcr.io/hapood/simple-open-messaging-service:v0.1.0-alpha.0

The same release is also available through the moving latest channel:

docker pull ghcr.io/hapood/simple-open-messaging-service:latest

latest follows published versions, including alpha releases. Development branch builds update
dev independently and never replace latest. Keep application and migration services on the
same image reference.

The generator and NAS template default to this exact version. The manual public-server template
uses latest. PostgreSQL runs separately in Compose, and migrations complete before the application
starts. Preserve existing deployment credentials and back up the database and application data
before upgrading an existing installation.

Image digest

Anonymous registry access was verified for both architectures. The version tag and latest
resolve to the same multi-platform digest:

sha256:09e2cf9eecf4bc477e195c3c8400d0117fbf4d70584899b419d8728d179a2b6e

Pin that exact image with:

docker pull ghcr.io/hapood/simple-open-messaging-service@sha256:09e2cf9eecf4bc477e195c3c8400d0117fbf4d70584899b419d8728d179a2b6e

Container build and runtime verification

Included in this alpha

  • Direct and group messaging, media, message history, search, and one-to-one WebRTC calls.
  • Federation discovery, signed server-to-server requests, recoverable synchronization, and
    access-controlled media transfers.
  • Browser-local Compose generation for public-server and NAS deployment modes, including DNS and
    port instructions and escaped credentials.
  • Administration tools for sessions, diagnostics, federation controls, and runtime log output.
  • Independent container publishing with native amd64/arm64 image checks.

Configuration notes

  • Log output starts at error on each backend restart. Change it under Logs → Live tail →
    Output level
    in the administration console. This process-local setting resets on restart;
    LOG_LEVEL no longer controls the threshold.
  • Execution measurements additionally require a nonzero EXECUTION_MEASUREMENT_SAMPLE_RATE and
    debug or trace log output.
  • Generated Compose files contain credentials. Keep them private and retain existing credentials
    when regenerating deployment configuration.
  • No database migrations are added by the release-preparation pull request. New deployments must
    still apply the migrations included in the image through the Compose migration service.

Verification

The release source passed backend, web, administration, and Docker CI checks. Each
container architecture is checked for Caddy, FFmpeg, native Argon2 and Sharp modules, server and
migration entry points, and both frontend bundles before publication.

Prepared in PR #1, squash-merged
into main as 3d7ff9cb.