SnipeSocial 5.4.4 Release (6 June 2026)

SnipeSocial 5.4.4 deployed on 6 June 2026, completing in a record eleven minutes. The release consolidated months of development work across two internal build phases, incorporating everything that had been built since the previous release, and shipped the entire set as a single announced version. The eleven-minute deployment time is a record for a release of this scope; a consequence of months of development followed by days of module testing that meant the actual rollout required no improvisation.

The platform’s standard practice of activating features in stages applies to this release. A number of the new capabilities, particularly across payment methods and social login, have been fully integrated and tested but are being enabled progressively to ensure compatibility with users. The infrastructure is in place; the activation sequence follows the platform’s established model of controlled rollout rather than simultaneous activation of everything at once.

Publishing and Content Creation

The Publisher gained a full Rich Text Editor in this release, replacing the basic text input with a formatting-capable composition environment. Alongside it, hashtag autocomplete was added to the Publisher, streamlining the workflow for users who rely on hashtag-based discovery without requiring them to type and check tags manually.

Collaborative Posts launched as a new content type, allowing multiple users to co-author a single post. This extends the collaboration model that already existed for blogs and group content into the everyday post format, joint announcements, shared creative work, and team content are all now possible at the post level.

The Watch module received a revamp, refreshing the video consumption interface. The YouTube player for Movies was replaced with a Smart YouTube Player with more intelligent display and playback handling, alongside an administrator option to disable YouTube embedding for Movies entirely. Fullscreen support was added for Games, a long-requested addition that brings the Play experience in line with user expectation.

Blogs Expansion

Blogs References were added, giving long-form posts the ability to formally cite sources. Blogs Co-Authors arrived alongside, allowing a post to be attributed to and edited by more than one writer. Together these lift the editorial credibility and collaborative utility of the platform’s publishing layer.

Blogs were integrated into four platform areas that had not previously surfaced them: Profiles, Pages, Groups, and Events now each have a dedicated Blogs section. A group focused on a particular subject can publish long-form editorial alongside its regular social posts. An event page can host background reading. A profile can function as a personal publication, not just a social stream.

Monetisation

Discounts and Coupons were added to the Monetisation system, giving creators and pages the ability to run promotional pricing on monetised content and subscriptions, with proper discount and coupon code management built into the admin layer.

Keycloak Identity Provider

The major infrastructure addition in 5.4.4 is a purpose-built Keycloak identity provider extension, a connector that allows external applications to authenticate users through SnipeSocial via standard OpenID Connect, without needing to interact with SnipeSocial’s non-standard OAuth flow directly.

The architecture is straightforward: Keycloak brokers the login. A developer’s application speaks OIDC to Keycloak; Keycloak speaks to SnipeSocial; the application never touches SnipeSocial’s API directly. Any application that can authenticate against a standard OIDC provider can now authenticate against SnipeSocial, dramatically reducing the barrier to third-party OAuth integration. The connector was built and tested for Keycloak 26.0.0 on Java 17. The compiled JAR is deployed to the Keycloak providers/ folder; no server credentials are bundled, the developer supplies their own SnipeSocial App ID and App Secret after installation.

Why Not Keycloak’s Built-In OAuth2 Provider

Keycloak’s built-in OAuth2 provider assumes standard flows: client_id and response_type=code on login start; code and state on callback; grant_type plus code on token exchange; Bearer token for user profile; and often-refreshable token lifetimes. SnipeSocial’s API differs in several specifics, app_id only on login start; no state parameter on callback; app_id, app_secret, and auth_key on token exchange; access_token as a query parameter rather than a Bearer header for user info; and a fixed one-hour token lifetime requiring re-login rather than silent refresh. The custom connector handles all of these differences transparently.

Settings Mapping

Alias: ‘snipesocial’ , used in broker callback URL paths. Client ID and Client Secret: taken from the app registered in the SnipeSocial App Dashboard. Authorization URL: snipesocial.co.uk/api/oauth. Token URL: /api/authorize (POST with app_id, app_secret, auth_key). User Info URL: /api/get_user_info (access_token as query parameter, not Bearer header). Snipesocial Redirect URL: must exactly match the value set in the App Dashboard.

User Field Mappings

SnipeSocial fields map to Keycloak/OIDC claims as follows: user_id to Federated ID; user_name to preferred_username; user_email to email; user_firstname to given_name; user_lastname to family_name.

Social Login Additions

Apple and Discord were added as social login options in this release, expanding the authentication surface for new user registration and login. Both are integrated at the infrastructure level and available for staged activation.

Payment Infrastructure

Seven new payment methods were integrated in 5.4.4, all deployed at the infrastructure level and available for progressive activation. CCBill expands capability for contexts where it is the dominant processor. Cashapp adds a payment route prevalent among US users. Blik is the primary instant payment method in Poland. EPS is the primary bank transfer system in Austria. iDEAL is the primary bank transfer system in the Netherlands. Bancontact is the dominant payment method in Belgium. Przelewy24 is the leading payment aggregator in Poland. OXXO is a cash voucher system used extensively in Mexico. Collectively these represent a significant expansion of geographic payment coverage, particularly across Central Europe and Latin America.

Security and Compliance

hCaptcha was added as a security check layer, a privacy-respecting challenge system that does not rely on Google’s reCAPTCHA infrastructure. A new Cookies Consent system was introduced, updating compliance with current expectations around user consent. Email templates received a full revamp across all system-generated communications.

Fixes

The release resolved a set of accumulated issues: Custom Fields Search (a functional gap that had existed across several versions), a Highcharts loading problem, a Compo Post issue, Chat text non-wrapping, Schedule Post listing display, Posts Reactions update behaviour, the payment link flow for non-logged-in users accessing paid Movies, YouTube Shorts scraping, RTL publisher rendering, and Blog blockquote display. The fix to Custom Fields Search is particularly notable, custom fields had been part of the user profile system for several versions and their exclusion from search had been a meaningful gap.