wpsignal

WordSocket sends realtime events from your WordPress site to connected browsers. 
When content changes: a post is published, a comment is approved, an option is updated: the plugin pushes the event to subscribers instantly via WebSocket (with SSE fallback).
On WordPress 7.0+, WordSocket also registers as a WebSocket-based Yjs sync provider for real-time collaborative editing in the block editor, replacing the default HTTP polling transport with a low-latency WebSocket connection.
Features:
<ul>
<li>One-click automatic connection via the WPSignal dashboard (no API key required)</li>
<li>Manual connection via API key for advanced setups</li>
<li>Disconnect button with inline confirmation, removes the site from the server immediately</li>
<li>WebSocket-first with automatic SSE fallback</li>
<li>Per-site JWT signing secrets: each site’s connection tokens are cryptographically isolated</li>
<li>AES-256-GCM encrypted event payloads: the WPSignal relay receives ciphertext only and never has access to plaintext message content</li>
<li>Real-time collaborative editing in the block editor (WordPress 7.0+, via Yjs sync provider)</li>
<li>Admin toggle to disable the collaboration provider and fall back to WordPress HTTP polling</li>
<li>Built-in triggers for post updates and custom post types</li>
<li>Custom trigger builder: map any WordPress action hook to a realtime event</li>
<li>Public JavaScript API (<code>window.WPS</code>) for themes and plugins to share the connection</li>
<li>Extensible connection token: <code>wpsignal_token_channels</code> and <code>wpsignal_token_channel_prefixes</code> filters let other plugins add channels and namespace permissions to the JWT without modifying core</li>
<li>Admin explorer page with live event log, publish form, and token inspector</li>
<li>Short-lived JWTs (5 min) with automatic refresh</li>
</ul>
How it works:
<ol>
<li>Install the plugin and connect to the WPSignal service.</li>
<li>When content changes in WordPress, the plugin encrypts and publishes an HMAC-signed event to the WPSignal server.</li>
<li>The server pushes the ciphertext to all browsers subscribed to that channel.</li>
<li>The browser decrypts the payload and dispatches <code>wpsignal:*</code> DOM events. The relay never sees plaintext content.</li>
<li>On WordPress 7.0+, the block editor uses the same WebSocket connection for collaborative editing with no extra configuration.</li>
</ol>
<h4>Third-Party Service</h4>
This plugin connects to the WPSignal service at api.wpsignal.io for the following operations:
<ul>
<li>Site registration: when you connect in the admin (via the automatic one-click flow or by entering an API key manually), the plugin registers your site with the server and receives credentials.</li>
<li>Event publishing: when a trigger fires (e.g. a post is saved), the plugin sends an encrypted, HMAC-signed HTTP request to the server.</li>
<li>Realtime connections: logged-in users’ browsers connect to the server via WebSocket or SSE to receive events.</li>
<li>Collaborative editing: on WordPress 7.0+, Yjs document updates are relayed over the same WebSocket connection.</li>
</ul>
Event payloads are AES-256-GCM encrypted before leaving WordPress. The WPSignal server relays ciphertext and never has access to plaintext message content. Data is delivered in realtime and is not persisted on the server.
<ul>
<li><a href="https://wpsignal.io/terms" rel="nofollow ugc">Terms of Service</a></li>
<li><a href="https://wpsignal.io/privacy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>

WordSocket

WordSocket is the official WordPress plugin for WPSignal (wpsignal.io), a third-party WebSocket/SSE delivery service.

POTAR

Mesh-Plug provides a simple shortcode that connects to your MQTT broker over WebSocket and prints incoming messages to a live log.
Shortcode: [mesh_plug]
Map shortcode options: 
– map_tiles=”voyager|osm|light|dark” (default: voyager) 
– map_zoom=”13″ map_min_zoom=”2″ map_max_zoom=”18″ 
– fit=”1|0|once” fit_max_zoom=”13″ center=”lat,lon”
<h3>External services</h3>
Mesh-Plug can connect to external services depending on how you configure and use it.
<h4>MQTT broker (configured by the site administrator)</h4>
Mesh-Plug connects directly from the visitor’s browser to the MQTT broker WebSocket URL you enter in Settings → Mesh-Plug. 
This is required for the plugin to receive and display Meshtastic/MQTT messages.
Data sent: the visitor’s browser establishes a WebSocket connection to your broker; it may send a client ID and (optionally) the username/password you configured; it subscribes to the topic filter you configured. 
When: whenever a page containing the [mesh_plug] shortcode is loaded and the user connects (or auto-connect is enabled).
Terms/Privacy: this depends on the broker provider you choose. If you use a third-party MQTT hosting provider, review their terms and privacy policy.
<h4>Map tile providers (CARTO / OpenStreetMap)</h4>
If you use the Map tab, Mesh-Plug downloads map tiles from a free provider to render the basemap. 
By default, Mesh-Plug uses CARTO Voyager tiles. You can switch to OpenStreetMap tiles with shortcode map attributes.
Data sent: standard HTTP requests for map tiles; this typically includes the visitor’s IP address, user agent, and the requested tile coordinates. 
When: whenever the Map tab is opened/visible and the map needs to load tiles.
CARTO basemaps: https://carto.com/basemaps 
OpenStreetMap tile usage policy: https://operations.osmfoundation.org/policies/tiles/ 
OpenStreetMap privacy policy: https://osmfoundation.org/wiki/Privacy_Policy
<h3>License</h3>
GPLv2 or later.
<h3>Credits</h3>
Developed by Michael Winchester 
For documentation and updates, visit <a href="https://meshplug.michaelwinchester.com/" rel="nofollow ugc">https://meshplug.michaelwinchester.com/</a>

Mesh-Plug for Meshtastic

Lightweight Meshtastic/MQTT viewer for WordPress via MQTT over WebSocket (WS/WSS).

WordSocket vs Mesh-Plug for Meshtastic