[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fiZpTdyaWVcSbbigDnldBC4Q1VnbwvM2RBs_RrbUspo4":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"wpsignal","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpsignal\u002F",1,0,100,30,94,"2026-05-20T03:12:08.719Z",[13],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":8,"num_ratings":6,"last_updated":20,"tested_up_to":21,"requires_at_least":22,"requires_php":23,"tags":24,"homepage":30,"download_link":31,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":32,"fetched_at":33},"wordsocket","WordSocket","0.14.0","\u003Cp>WordSocket sends realtime events from your WordPress site to connected browsers.\u003Cbr \u002F>\nWhen 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).\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>One-click automatic connection via the WPSignal dashboard (no API key required)\u003C\u002Fli>\n\u003Cli>Manual connection via API key for advanced setups\u003C\u002Fli>\n\u003Cli>Disconnect button with inline confirmation, removes the site from the server immediately\u003C\u002Fli>\n\u003Cli>WebSocket-first with automatic SSE fallback\u003C\u002Fli>\n\u003Cli>Per-site JWT signing secrets: each site’s connection tokens are cryptographically isolated\u003C\u002Fli>\n\u003Cli>AES-256-GCM encrypted event payloads: the WPSignal relay receives ciphertext only and never has access to plaintext message content\u003C\u002Fli>\n\u003Cli>Real-time collaborative editing in the block editor (WordPress 7.0+, via Yjs sync provider)\u003C\u002Fli>\n\u003Cli>Admin toggle to disable the collaboration provider and fall back to WordPress HTTP polling\u003C\u002Fli>\n\u003Cli>Built-in triggers for post updates and custom post types\u003C\u002Fli>\n\u003Cli>Custom trigger builder: map any WordPress action hook to a realtime event\u003C\u002Fli>\n\u003Cli>Public JavaScript API (\u003Ccode>window.WPS\u003C\u002Fcode>) for themes and plugins to share the connection\u003C\u002Fli>\n\u003Cli>Extensible connection token: \u003Ccode>wpsignal_token_channels\u003C\u002Fcode> and \u003Ccode>wpsignal_token_channel_prefixes\u003C\u002Fcode> filters let other plugins add channels and namespace permissions to the JWT without modifying core\u003C\u002Fli>\n\u003Cli>Admin explorer page with live event log, publish form, and token inspector\u003C\u002Fli>\n\u003Cli>Short-lived JWTs (5 min) with automatic refresh\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>How it works:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Install the plugin and connect to the WPSignal service.\u003C\u002Fli>\n\u003Cli>When content changes in WordPress, the plugin encrypts and publishes an HMAC-signed event to the WPSignal server.\u003C\u002Fli>\n\u003Cli>The server pushes the ciphertext to all browsers subscribed to that channel.\u003C\u002Fli>\n\u003Cli>The browser decrypts the payload and dispatches \u003Ccode>wpsignal:*\u003C\u002Fcode> DOM events. The relay never sees plaintext content.\u003C\u002Fli>\n\u003Cli>On WordPress 7.0+, the block editor uses the same WebSocket connection for collaborative editing with no extra configuration.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Third-Party Service\u003C\u002Fh4>\n\u003Cp>This plugin connects to the \u003Cstrong>WPSignal service\u003C\u002Fstrong> at api.wpsignal.io for the following operations:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Site registration\u003C\u002Fstrong>: 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.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Event publishing\u003C\u002Fstrong>: when a trigger fires (e.g. a post is saved), the plugin sends an encrypted, HMAC-signed HTTP request to the server.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Realtime connections\u003C\u002Fstrong>: logged-in users’ browsers connect to the server via WebSocket or SSE to receive events.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Collaborative editing\u003C\u002Fstrong>: on WordPress 7.0+, Yjs document updates are relayed over the same WebSocket connection.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>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 \u003Cstrong>not persisted\u003C\u002Fstrong> on the server.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwpsignal.io\u002Fterms\" rel=\"nofollow ugc\">Terms of Service\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwpsignal.io\u002Fprivacy\" rel=\"nofollow ugc\">Privacy Policy\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","WordSocket is the official WordPress plugin for WPSignal (wpsignal.io), a third-party WebSocket\u002FSSE delivery service.",245,"2026-04-13T03:41:00.000Z","7.0","6.2","7.4",[25,26,27,28,29],"collaboration","events","push","realtime","websocket","https:\u002F\u002Fwpsignal.io\u002Fwordsocket","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwordsocket.0.14.0.zip",null,"2026-04-16T10:56:18.058Z"]