v1.2.0

New

• Discussion-list typing dots now work in polling mode. With realtime's "Discussion list typing dots" setting on, the typing ellipsis appears on the discussion and tag lists just as it does with a websocket: typing in a discussion lights its row, composing a new discussion lights the chosen tags. Audiences are respected exactly as realtime's own server does it — a restricted tag's activity is only ever shown to people who can see that tag. Reported by a Warble user; thank you.

With this, polling covers every realtime feature except online presence. No new settings, but this release does add to the database, so:

composer update linkrobins/flarum-warble
php flarum migrate
php flarum cache:clear

If you run a websocket instead of polling, nothing changes in this release: list dots there are provided by realtime's bundled server only.

v1.1.0

Warble is now standalone: realtime with no server at all

Warble no longer needs any external service. On a forum with no websocket configured, realtime now works over polling: each visitor's browser quietly asks your forum for updates every few seconds. Live posts, typing indicators and notifications all work on any hosting — including shared hosting, where running a websocket server is impossible. Nothing to sign up for, nothing to run, nothing to pay.

• Zero setup. Install, enable Realtime and Warble, done. The polling transport turns on by itself when no websocket is configured. A new setting can force either transport, and another tunes the polling interval.
• Honest speed. Polling is a few seconds behind rather than instant, and hidden browser tabs stop polling entirely. Small and mid-size communities will not notice; a busy forum should run a websocket (any Pusher-compatible server works — point config.php at your own Reverb or soketi and Warble steps aside).
• Privacy done properly. Who-is-typing names are decided on your server per viewer, so a member who hides their online status stays anonymous to everyone not permitted to see through it.
• Already connected to the old hosted service? Nothing changes: your written connection is just a websocket configuration and keeps working as long as that server runs.

Two things to know after updating:

1. This release adds database tables, so run the migration.
2. The typing indicator is behind realtime's "See who is typing" permission, which fresh installs grant to nobody. Grant it on the Permissions page to the groups (guests included, if you like) who should see names.

composer update linkrobins/flarum-warble
php flarum migrate
php flarum cache:clear

v1.0.3

Fixed

• Typing indicators show names again on Flarum 2.0.0-rc.6. rc.6 changed how the typing indicator learns who is typing, in a way only its own bundled websocket server supports; through Warble every typist showed as a hidden/anonymous label no matter what anyone's settings said. Warble now attaches the sender's own name to typing events the way earlier versions did. Someone who hides their online status stays anonymous, as before.

Update on your forum (the fix is in the extension, nothing on the Warble side changes):

composer update linkrobins/flarum-warble
php flarum cache:clear

v1.0.2

Changed

• Support now goes through GitHub issues. The old community-forum link in the package metadata pointed at a page that no longer exists, so this release removes it. Nothing in the extension itself changed: if it is running fine, there is no need to rush this update.

v1.0.1

Changed

• The package details now point at this extension's own page on linkrobins.com, and list the correct PHP requirement and where to report a problem.

Nothing on your forum changes. This release exists so the information shown on Packagist matches the extension's page.

v1.0.0

Warble is now stable.

This release promotes Warble to a stable 1.0 line. There are no functional changes from v0.8: the code is identical, and it behaves exactly as it did before.

Why the version jump matters: on the 0.x line, Composer's default version rules pinned each install one minor version behind, so the Extension Manager update button (or composer update) could report "nothing to update" even when a newer version was out. Moving to 1.0 fixes that. From here on, updates flow through the normal update button and composer update with no extra steps.

If you are on an older 0.x version and the update button says there is nothing to update, run this once from your forum's root to move onto the 1.x line:

composer require linkrobins/flarum-warble
php flarum cache:clear

After that, future updates are automatic.

v0.8

This release is for everyone who enabled Warble and then found a settings page that said "This extension has no configuration" instead of the key field. That happens when your forum keeps serving an outdated copy of its admin JavaScript, built before Warble was turned on. It is a server-side problem on some shared hosts, which is why reinstalling the extension or clearing your browser cache never helped.

Warble now repairs this by itself. When you open the admin panel, Warble checks whether the JavaScript your forum serves actually includes Warble, and rebuilds it on the spot if it does not. In the normal case you will not notice anything: the settings page simply works.

And when it cannot repair it, it tells you exactly why. If something still prevents Warble's settings from loading, a red banner now appears at the bottom of the admin panel in plain language:

• If another extension's JavaScript crashed while the page was loading, the banner names the exact file and error, so you know what to disable or report.
• If your forum's assets folder is not writable, the banner says so, and that one is for your hosting provider.
• Otherwise the banner offers a Fix this button that rebuilds your forum's assets with one click and reloads the page.

No SSH, no terminal, no configuration needed: everything happens in the admin panel.

Also in this release: a troubleshooting section in the README covering the symptom, and automated tests for the new behavior.

v0.7 — clearer connect expectations

After you paste your Warble key, realtime can take up to a minute to activate (your host's PHP re-reads its config on a short cycle). v0.7 says so — in the key help and the "connected" banner — so you don't think it's broken if replies aren't instant in the first few seconds.

No action needed: composer update linkrobins/flarum-warble. Locale-only change.

v0.6 — realtime that just works on shared hosting

Warble now sends a light realtime broadcast instead of the whole discussion.

flarum/realtime normally serializes the entire discussion — every post, every participant — on each reply and sends it to the realtime server. On a busy or admin-visited discussion that payload can overflow the server's request limit (a 413), and on the default sync queue it runs inside the reply request, so it slows and can break posting.

v0.6 sends only what the client needs (the discussion plus its author/last-poster/tags); the browser refetches the rest with its own permissions. The result:

• No more 413s on large discussions.
• No queue worker, Redis, or cron required — the broadcast is now cheap enough to run on the stock sync queue, so realtime works out of the box on shared hosting.
• Visibility is unchanged, and anything unexpected falls back to the standard behavior.

No config changes needed — composer update linkrobins/flarum-warble.