Live Event Reference

YouTube – Standard DOM Capture

Implementation: sources/youtube.js

• Keep the live chat tab open. Capture reads the membership and gift cards rendered in that session; it does not require the viewer to be the channel owner or a moderator. Account access and the selected chat view can affect which rows are visible.
• Opening the Viewer Count & Chat Activity overlay with viewers displayed automatically requests viewer counts. The Show viewer count and Track active chatters settings also enable collection.
• For follower alerts and additional events, enable WebSocket mode in extension settings.

Membership blocks also set membership for moderator/member chat, while subtitle carries either month counts or tier names. sourceName/sourceImg populate once getChannelInfo succeeds. Standard DOM chat now includes meta.messageId when YouTube exposes a native live-chat message ID, which the dock uses for delete sync.

YouTube – Websocket/Data API Capture

Implementation: sources/websocket/youtube.html, shared helpers under shared/

• Defaults to OAuth scopes youtube.readonly and youtube.channel-memberships.creator. Optional write access adds youtube.force-ssl for chat sending, moderation, bans, and stream-detail edits; Google may present this as broad YouTube management permission because YouTube does not provide a chat-only write scope.
• Channel statistics respect the per-setting toggles (showsubscount, showviewercount).
• The API cannot deliver custom badge imagery; badge fallbacks use emoji icons noted below.
• When the API explicitly reports authorDetails.isChatModerator: true, chat, Super Chat, Super Sticker, YouTube Gift, and membership-gift payloads include mod: true. Moderator status is not inferred or cached between events.
• New subscriber alerts use the myRecentSubscribers API (polled every 5 minutes). Note: Results may be delayed or incomplete; only publicly visible subscriptions can be identified.
• YouTube redirect banners are not exposed by the Data API, so redirect remains available only from Standard DOM capture.

Chat relays from the API use meta.plainText for the plain-text message alongside rich chatmessage content. It is text, not HTML, and can still contain Unicode emoji. Membership badges fall back to emoji (⭐, 💝, 🏅, etc.) to remain consistent with DOM capture. Regular chat payloads also include meta.messageId so dock-side delete actions can round-trip back to the YouTube moderation API.

YouTube Websocket: Event & Membership Quick Reference

Twitch – Standard DOM Capture

Implementation: sources/twitch.js

• Keep Twitch chat open. Membership and user notices are captured when Twitch renders them; they are not restricted to broadcaster or moderator accounts. Authentication may be needed for account-specific features.
• Viewer count requests hit https://api.socialstream.ninja/twitch/viewers every 30 seconds.
• For follower alerts, raids, and full event support, enable WebSocket mode in extension settings.
• Viewer-shared Watch Streak notices are disabled by default and require the Show Twitch Watch Streaks setting.
• The opt-in PluralMind setting may replace chatname, nameColor, and the proxy-wrapped portion of chatmessage, and may add a pronoun text badge. username remains the Twitch login; related deletes carry delete.meta.pluralmind so the dock uses that stable login.

Bits/Cheers populate hasDonation (for example “500 bits”) even though data.event remains empty; rely on that field when rendering donation widgets. Subscriber streak information appears in subtitle when badges expose months.

Twitch – EventSub/Websocket

Implementation: sources/websocket/twitch.js with shared core providers/twitch/chatClient.js

• OAuth scopes: chat:read, chat:edit, user:write:chat, bits:read, moderator:read:followers, moderator:read:chatters, channel:read:subscriptions, channel:read:hype_train, channel:moderate, moderator:manage:banned_users, moderator:manage:chat_messages, channel:manage:broadcast, channel:read:redemptions, channel:read:ads, channel:manage:ads. Broadcaster tokens unlock subscriber/follower counts.
• Events delivered by EventSub, plus Helix polling for viewer/follower/subscriber totals.
• WebSocket mode provides real-time follower alerts, subscription events, raids, cheers, Power-ups, channel point redemptions, and hype train metadata.
• Shared Chat rows use Twitch IRC source-room-id to populate sourceName/sourceImg with the originating channel when it differs from the connected channel.
• Viewer-shared Watch Streak notices are disabled by default and require the Show Twitch Watch Streaks setting.
• The opt-in PluralMind setting may replace chatname, nameColor, and the proxy-wrapped portion of chatmessage, and may add a pronoun text badge. username and userid retain the Twitch identity; related deletes carry delete.meta.pluralmind so the dock uses those stable fields.

Chat payloads reuse the shared provider, so data.event is populated for `/me` (action) and legacy bits tags even outside EventSub flows. Twitch GIF messages put the Giphy asset in contentimg, leave chatmessage empty, and preserve Twitch's fallback label in meta.gifLabel. Dedupe and deletion logic uses message IDs; messages sent through SSN use the native message_id from Twitch's IRC echo in data.id.

Twitch Hype Train Metadata

hype_train is metadata-only and does not include chatname or chatmessage. Dashboards should update an existing train display by meta.id instead of appending each progress update as chat. The Meta Data Bar (meta.html) renders these events as a top progress bar.

Twitch EventSub: Event Quick Reference

OBS Flow Actions

Implementation: actions.html through OBS WebSocket v5 events, with dock.html OBS Browser Source events as a fallback

• Keep the Flow Actions overlay open with the same Social Stream session as the Event Flow editor/background, or keep the dock loaded inside OBS.
• Configure OBS WebSocket v5 on OBS 28+; the default URL is ws://127.0.0.1:4455.
• These are Event Flow system events. They do not include chatname or chatmessage, and extra OBS details stay inside meta.

Streamlabs Alert Box

Implementation: sources/streamlabs.js (alert-box DOM); optional socket bridge at sources/websocket/streamlabs.html

• Keep your Streamlabs alert box open in a tab or browser source so alerts render; the content script reads the alert DOM for message/image/tokens.
• Donation-style alerts set hasDonation (e.g., “$10 USD” or “100 bits”) and optional donoValue in USD.
• Event types inferred: follow, subscription, gift, cheer, donation, superchat, raid, redeem, merch, sponsor.
• For the socket bridge, paste your Streamlabs Socket API token and connect; alerts relay without the alert-box page.

TikTok Live – DOM Capture and TikFinity Feed

Implementation: sources/tiktok.js for native TikTok pages and sources/tikfinity.js for TikFinity's activity-feed widget/iframe. SSApp still has a native TikTok integration with the widest event coverage (see SSApp docs). Standard chat includes meta.messageId when the page exposes a native message ID; distinct messages with identical text retain distinct IDs.

• Works on the broadcaster's live page. Gift/like/follow banners only populate when the session is authenticated.
• TikTok provides many events via DOM detection without requiring WebSocket mode – gifts, follows, likes, and opt-in joins are captured from rendered rows.
• TikFinity widget pages at tikfinity.zerody.one/widget/activity-feed* also work. The embedded activity-feed iframe emits the same canonical TikTok payload fields for chat, follows, shares, gifts, subscriptions, opt-in joins, and treasure chests.
• No additional API authentication required.
• SSApp native mode still adds events beyond the page/widget capture paths: question_new, emote, viewer_update, and the opt-in aggregate likes_update.

membership mirrors badge tooltips (subscriber tiers). Avatar caching keeps chatimg valid between events; if the DOM suppresses color for moderators the script clears nameColor. TikFinity Activity Feed capture supports legacy docks and the new widgets.tikfinity.com browser-source URLs. New stream_event messages are translated into the same chat, gift, follow, share, subscription, join, and envelope payloads described here. TikFinity gift rows also set contentimg to the gift icon when available. For explicitly streakable gifts with a repeatEnd flag, TikFinity sends only the completed streak and its final quantity; intermediate count updates are not forwarded. Non-streak gifts and older payloads without that flag continue through immediately. Native DOM gift streak updates and TikFinity gift rows include meta.tiktokGiftStreakId, meta.tiktokGiftCount, and meta.tiktokGiftQuietMs so overlays can coalesce repeated updates; legacy streak IDs are unique to the page instance. Gift metadata may also include tiktokGiftMessageId (the original TikTok message ID), tiktokGiftSenderId, groupId, giftId, giftName, streakable, and repeatEnd. Native IDs identify the same gift across capture windows; a nonzero group ID with sender and gift IDs identifies cumulative streak updates. SSApp WebSocket capture supplies the same fields after settling a streak, with count retained for compatibility. Its donation toggle is checked when forwarding each gift: disabling TikTok donations removes hasDonation and donoValue while retaining the gift event and metadata. TTS uses these identities to coalesce updates and suppress completed duplicates for up to ten minutes (bounded cache), and reads TikTok gifts as sender, quantity, and gift name. Older payloads fall back to their existing streak IDs and message text; no identity is inferred from gift text alone. TikTok gift speech uses the selected TTS/voice language, independently of the UI language. Announcement verbs are localized for English, Spanish, Portuguese, French, German, Italian, and Dutch; other languages use sender, quantity, and gift name without an English verb. Simplified TTS retains that neutral format. Gift names remain as supplied by the platform; this does not automatically translate gift catalogs or chat messages, or infer a stream’s language.

For these streak updates, the count and donation label are cumulative: 1, 2, 3 means three gifts, not six. Totals consumers should add only the increase over the largest amount already seen for that streak ID. Standard capture supports legacy gift classes and current image/count rows; both retain event: "gift" and hasDonation. Unknown prices retain gift counts/names for display and use a USD estimate of one coin per gift. Source-supplied donoValue takes priority; rendered gift metadata may provide coinsPerGift or diamondsPerGift before the gift table or default is needed. Standard/TikFinity coin estimates and SSApp native diamond estimates use their existing distinct conversions; neither represents a guaranteed cash payout.

Whatnot

Implementation: sources/whatnot.js

• Use the Whatnot source in SSApp for public chat and auction events without video, or open the live show page for website capture. Both connect to the public auction feed. Website capture also reads rendered auction and catalog sections.
• Capture Stream Events controls Whatnot system events plus auction/catalog metadata updates; joined rows also require Capture "joined" stream events; viewer counts still follow the viewer/hype toggles.

Auction/commerce display updates remain DOM-backed snapshots. To match an individual websocket event in Event Flow, use Event Type (Advanced), select Custom Event, and enter its exact name. Labels can use **{username}**\n{subtitle} with selected text weight; conditions can compare meta.paymentStatus with failed. An importable Whatnot label example is available. Existing stream-event capture settings still apply.

Additional optional fields are meta.catalogProductId (the packet's product.productId), meta.parentProductId (product.parentId), meta.transactionType (Whatnot's sale type, unchanged), and meta.placeOrderErrorReason (Whatnot's supplied order/payment error code). These product references describe the catalog or parent listing; they do not replace an order ID. Stock quantity is not treated as purchased quantity.

For payment-success automation, set an Event Type (Advanced) trigger to Custom Event: payment_succeeded, and filter the source to Whatnot. Existing conditions and templates can use that event's userid, chatname, subtitle and meta.orderId directly. No remembered purchase is needed when the notification contains the required details.

An auction ending or an item being marked sold does not confirm successful payment: these notifications are not emitted as paid purchase events and do not set donation amounts. A success event is emitted only for a received payment_succeeded notification; capture does not poll for payment completion or infer it from a sale. Other paymentStatus values are forwarded only when explicitly supplied in a captured packet. Missing identifiers are omitted; a product ID alone may cover multiple sales, so use a supplied order/auction ID to correlate notifications. Capture does not remember purchases or match payment updates; any such workflow must be explicitly configured in Event Flow. Repeated commerce notifications with the same native event timestamp/ID are suppressed across overlapping channels and reconnects, within a 2,000-event cache. Packets without a native event identity use a brief duplicate window. Raw order/payment objects are not forwarded.

eBay Live

The Monetization eBay seller connection requires a configured SSN eBay service and seller OAuth consent; eBay Live capture below is independent. Sandbox mode uses sandbox listing URLs, labels the buyer "eBay Sandbox buyer", and prefixes the message with "Sandbox test purchase:". Sandbox purchases retain the same purchase contract and can trigger enabled alerts/chat actions during testing. Its implemented payment contract emits event: "purchase", with type and platform set to ebay. It requires a paid order matching a selected product. id is a stable opaque order-line identifier; chatname is "eBay buyer", chatmessage is plain text (textonly: true), subtitle is the product name and optional contentimg is its image. meta.ebayPurchase contains itemId, itemName, quantity, and public url. No buyer identity, shipping data, hasDonation or donoValue is included. This differs from scraped auction or stock updates, which do not prove payment.

Implementation: sources/ebay.js

• Open either /ebaylive/events/<id>/chat or /ebaylive/events/<id>/stream. Both receive the same live auction feed.
• The public WebSocket feed supplies auctions, bids, winners, timing extensions and stock changes; a read-only GraphQL query supplies listing details. DOM capture remains a fallback when network data is unavailable.
• Capture Stream Events controls metadata snapshots (auction_update, commerce_update); viewer counters still honor viewer/hype toggles.

eBay metadata events intentionally omit chatname/chatmessage; downstream overlays should render from data.event + data.meta only.

Kick – Standard DOM Capture

Implementation: sources/kick.js. Chat includes meta.messageId when the page exposes a native message ID.

• Needs an authenticated session to resolve profile images and subscriber badges.
• Limited event detection via chat text matching and badges; viewer counts still work when the toggle is enabled.

Kick – Websocket/Bridge

Implementation: sources/websocket/kick.js with shared helpers under providers/kick/core.js

• OAuth via the Social Stream Kick bridge. Current scopes are user:read, channel:read, channel:write, channel:rewards:read, chat:write, events:subscribe, moderation:ban, moderation:chat_message:manage, and kicks:read. Tokens are refreshed automatically.
• Kick webhook provisioning may take several minutes; the UI lists active subscriptions per channel.

Profile lookups leverage profileCache; mapBadges merges Kick's badge assets with cached SVG when available. When Kick reports donations in KICKs, the bridge converts them into hasDonation plus meta.amount with currency fallback to "KICKs". Chat payloads include meta.messageId when the bridge exposes a native Kick message ID so delete sync can target the correct message. Reply payloads include meta.reply with the parent messageId, author, and text when known. Supplied reply details remain available even when the original message is not cached; an ID-only reply without cached context can still lack a visible quote.

Kick Websocket: Event Quick Reference

VPZone - WebSocket

Implementation: sources/websocket/vpzone.js

• Connects to wss://chat.vpzone.tv/ws?channel=USERNAME; OAuth requests profile:read, chat:read, chat:write, channel:read, channel:write, and chat:moderate. A bearer token can also be supplied manually.
• Flat VPZone frames such as type: "msg" are normalized into standard chat payloads.
• Platform-side delete_message / clear_chat frames remove the matching rows from the dock; optional toggles sync dock deletes and blocks back to VPZone (channel owner only).
• Channel owners get a page-local Stream Info panel to update the live stream's title and category (same pattern as the Twitch source page).

Joystick

Implementations: sources/joystick.js, sources/inject/joystick-ws.js, and sources/websocket/joystick.js

• The normal Joystick 2.0 website source runs on the signed-in /u/<channel>/chat page. It reads the page's ChatChannel, WhisperChatChannel, EventLogChannel, and SystemEventChannel Action Cable frames, with a rendered-row fallback for Electron and reconnect cases.
• Website chat messages use the same core fields as YouTube, Twitch, and Kick: native id, chatname, chatmessage, chatimg, chatbadges, nameColor, membership, mod, private, username/userid, and timestamp when Joystick supplies them. When the socket omits a username color, the rendered row supplies the same nameColor field used by color-enabled docks.
• Website-side message edits replace the matching dock row; deletes, mutes, and blocks remove matching rows using the native ID or username.
• The separate WebSocket source uses Joystick bot credentials (client_id + client_secret); the website source uses the signed-in page session.
• Authorizes on https://joystick.tv/api/oauth/authorize, then exchanges/refreshes tokens at https://api.joystick.tv/api/oauth/token.
• Connects to wss://api.joystick.tv/cable and subscribes to GatewayChannel.
• Optional OAuth token exchange is used for helper endpoints like https://api.joystick.tv/api/users/stream-settings.
• The separate bot-credential source does not emit viewer_update. The signed-in website source does emit viewer counts when its page socket supplies them, as described below.

XP Sync

Implementation: sources/xpsync.js

• Chat rows use the canonical payload fields with type: "xpsync", including author, message, avatar, image and inline SVG badges, name color, membership, moderator/member/bot flags, and the native message UUID as id when available.
• Replies follow the YouTube, Twitch, and Kick DOM-source convention: unless reply prefixes are disabled, initial contains the replied-to user, reply preserves the unprefixed message, and chatmessage receives the visible reply prefix.
• Sparks-highlighted rows are captured even though XPSync renders them without the normal chat row class or message id; the visible amount is exposed through hasDonation as N Sparks.
• When event capture is enabled, rows containing “just followed” or “followed the channel” emit event: "new_follower".
• When viewer counts are enabled, the permanent chat dock emits event: "viewer_update" from the live-video count already loaded by the XPSync page and refreshes it from XPSync's live page updates. No separate SSN credentials are required.

Instagram – Live REST Capture and News Inbox

Implementation: sources/instagram.js and sources/instagramlive.js (identical copies)

• On live pages (/<user>/live/?broadcast_id=...), live chat comes from Instagram's own web API, polled same-origin with the session cookie: GET /api/v1/live/{broadcast_id}/get_comment/?last_comment_ts={ts} every ~2s, and POST /api/v1/live/{broadcast_id}/heartbeat_and_get_viewer_count/ every ~5s when viewer counts are enabled. After 3 consecutive failures (or when no broadcast_id is discoverable) the source falls back to parsing the rendered chat DOM.
• The account's own activity feed is polled via POST /api/v1/news/inbox/ every ~45s on any Instagram page. The first poll only seeds the dedupe set so backlog is never replayed; stories dedupe by tuuid.
• Required API headers (all static/derivable): X-IG-App-ID: 936619743392459, X-CSRFToken (from cookie), X-ASBD-ID: 359341, X-Requested-With: XMLHttpRequest, Content-Type: application/x-www-form-urlencoded.
• All activity-feed events use type: "instagram"; live chat stays type: "instagramlive". Like events use the normal background path: the background sends one copy to the dedicated Reactions Overlay, then includes them in the main chat/events feed only when capturelikeevent is enabled, matching TikTok and MeetMe. hideevents and the custom event filter block them everywhere. Because inbox events belong to the signed-in account, they are suppressed while watching someone else's live (both /<user>/live/ pages and lives in the stories viewer; ownership is resolved per profile and retried after lookup failures) and emitted on your own live and all non-live pages. One active Instagram tab polls the account inbox at a time, and polling only runs when logged in.

Facebook Live

Implementation: sources/facebook.js (DOM scraping) and optional Graph API bridge at sources/websocket/facebook.html

• DOM capture reads rendered Facebook comments; the managed-Page Graph API bridge reads video comments. Both use type: "facebook", the standard chat fields, and no event for ordinary comments. The API bridge also includes the optional platform: "facebook".
• The API bridge uses userid for the author ID when available, timestamp for a valid creation time in Unix milliseconds, and contentimg for an HTTP(S) attachment image supplied by the API. Image-only comments may have an empty chatmessage. textonly applies only to the message body: raw text when true, escaped HTML when false.
• API comment context uses meta.messageId (native comment ID), meta.permalink, meta.videoId, and meta.pageId. Earlier API builds used meta.commentId, duplicated author/time fields under meta, and passed raw attachments there. New builds use the standard author/time/media fields instead; this does not add delete-sync support.
• Viewer counts refresh only when enabled. The API bridge reads concurrent live_views; it does not substitute cumulative video views or invent a zero for an unavailable count. API capture does not infer Stars, memberships, highlights, or replies from ordinary comment text.
• Stars are captured from the rendered Live Chat DOM when Facebook shows the visible N sent marker; they populate hasDonation and donoValue at 100 Stars = $1 USD without setting data.event.
• For testing, add ssnreplay=1 to the Facebook Live URL to process chat rows already visible after refresh.

Online Church

Implementation: sources/onlinechurch.js

• Relies on DOM scraping of the public chat and media header.
• Viewer counts only refresh when Show viewer count or hype mode is enabled.

SharePlay.tv

Implementation: sources/shareplay.js

Desktop API implementation: ssn_app/resources/shareplay-client.js. The native SSApp source subscribes to the authorizing user's own channel using a staff-provisioned public OAuth client.

• Relies on DOM scraping of the live chat drawer on SharePlay channel pages.
• Only newly inserted chat rows and cards are emitted after the scraper attaches; the existing backlog is intentionally ignored.
• The desktop API source receives new EventSub events; disconnected messages are not replayed. Chat carries SharePlay's message ID in id and sender ID in userid, but no avatars or badges. Emotes respect textonly; replies populate the existing reply fields when the parent is in the 200-message session cache.
• The desktop API maps completed channel.blitz events to raid, chat shoutouts to shoutout, and stream.viewers to viewer_update when viewer counts or hype mode are enabled. API shoutouts contain the provided chat text without the DOM card's banner or button metadata. Synthetic chat/Blitz events preserve meta.is_synthetic: true; viewer updates retain integer meta.

Streamplace

Implementation: sources/streamplace.js

• Reads Streamplace's React-rendered live page and skips the visible chat backlog when attaching.
• Relay-style messages such as Name (Discord): message are normalized to the relayed sender name.

WorldsWave

Implementation: sources/worldswave.js

• Supports WorldsWave live pages and chat-only URLs such as https://worldswave.com/kn_livecmd.php?cmd=viewStream&streamId=STREAM_ID&chatonly=1.
• Uses the stable data-ww-*/ww-chat-* markup when available, while retaining the legacy kontackt selectors for chat-only pages and older layouts.
• Existing chat history is skipped when capture attaches; test with a new message.
• Viewer counts require Show viewer count or hype mode. Dedicated gift/tip events and send-back are not implemented. A rendered row may still provide a donation label through data-ww-donation.

FLEX TV

Implementation: sources/flextv.js

• Reads the rendered chat panel on https://www.flextv.co.kr/channels/*/live pages.
• The chat panel must be visible. Existing chat history is skipped when the source attaches, so test with a new chat row.
• No viewer count, donation, or send-back path is documented for this source yet.

Seal Team Sloth

Implementation: sources/sealteamsloth.js

• Reads the rendered pop-out chat on https://sealteamsloth.com/popout-chat/* pages.
• Viewer counts require Show viewer count or hype mode.

MeetMe - DOM and WebSocket Capture

Implementation: sources/meetme.js

• Reads MeetMe's rendered live chat DOM on app.meetme.com/live/view/... pages and inside the api.gateway.meetme-live.com/web-live/... iframe.
• When the iframe websocket is available, wss://video-live.meetme.com/ frames are parsed before the DOM fallback to capture richer live events.
• hideevents suppresses non-donation events; MeetMe gifts and diamond donations still populate donation fields. capturejoinedevent enables join/rejoin notices. Actor-specific liked events use the shared background routing controlled by capturelikeevent; aggregate reaction effects remain explicitly targeted to the Reactions Overlay.
• Viewer counts prefer the visible MeetMe header count, falling back to websocket totals only when the DOM count is unavailable. Counts emit on change and repeat the latest count about every 30 seconds while showviewercount/hypemode is enabled; follower totals are changed-only and rate-limited to roughly 60 seconds.

Velora

Implementation: sources/velora.js and sources/websocket/velora.js

• Standard mode reads the visible chat DOM; WebSocket mode uses the Velora Events API with OAuth.
• Supported Standard mode URLs include https://velora.tv/*, https://velora.tv/dashboard/stream/popout?panels=chat%2Cactivity&channel=CHANNEL&layout=vertical, and https://velora.tv/dashboard/stream/popout/CHANNEL/obs-chat.
• Volts and channel point style cards are emitted as event payloads when exposed by the DOM or Events API.

Parti - Profile / Popout Chat Capture

Implementation: sources/parti.js

• Supports profile URLs like https://parti.com/USERNAME and popout URLs like https://parti.com/popout-chat?id=USER_ID.
• Viewer counts use Parti's livestream heartbeat endpoint when viewer-count capture or hype mode is enabled.

CHZZK - Popout Chat Capture

Implementation: sources/chzzk.js

• Supports https://chzzk.naver.com/live/*/chat and https://chzzk.naver.com/iframe/live/*/chat.
• Viewer counts use CHZZK's live-status polling endpoint when viewer-count capture or hype mode is enabled.

Rumble - Standard DOM Capture

Implementation: sources/rumble.js

• Requires authenticated session cookies so the service.php viewer API responds.
• Rendered Rant rows provide hasDonation; incoming raid cards provide event: "raid". This DOM source does not emit the API bridge's subscriber/follower event feed.

Rumble - Websocket/API URL

Implementation: sources/websocket/rumble.js

• Requires the creator-owned Live Stream API URL from https://rumble.com/account/livestream-api. Rumble documents that this URL includes the live stream key, does not require separate authentication, and should only be shared with trusted third parties.
• Read-only transport. The public Rumble Live Stream API docs do not describe an official chat-send endpoint, so this source relays messages/events into Social Stream but does not send chat back to Rumble.
• livestreams[].chat only populates while the selected stream is live. Use ?streamId=... to pin a specific stream when the API exposes more than one; invalid IDs now fail instead of silently falling back to another stream.
• The page also resolves https://rumble.com/chat/popup/<livestreams[].id> so you can open the normal injected popup chat directly without first loading the broadcaster's /live page.

This transport is intended for channels you own or manage. Because the API URL contains a live stream key, do not expose it in overlays, logs, screenshots, or shared browser profiles. Chat avatars come from Rumble's SSE chat stream once the official API resolves the stream ID; this transport does not scrape Rumble pages for avatars.

YouNow - DOM Capture

Implementation: sources/younow.js

• Reads the rendered live chat DOM and emits standard chat payloads with type: "younow".
• Audience activity lines such as is watching, I became a fan!, and invited N fans to this broadcast. are flagged with event: true so event filters can route them.

Favorited Studio - DOM Capture

Implementation: sources/favorited.js

• Reads the rendered live chat DOM and emits standard chat payloads with type: "favorited".

BEAM - DOM Capture

Implementation: sources/beamstream.js

• Reads the rendered live chat DOM and emits standard chat payloads with type: "beamstream".

Starvios

Implementation: sources/starvios.js

• Captures new rendered chat rows on https://starvios.com/popout/chat/USERNAME with type: "starvios", plain sender names, name colors, and text or inline emotes according to textonly.
• Paid chat rows retain the displayed amount in hasDonation (for example, 100 Starvies). No USD conversion or donation event is supplied.
• Existing rows and rows rendered during the initial 1.5-second history settling period are skipped. Separate pinned cards, reply previews, and subscription/raid notices are excluded. The popout supplies no verified viewer count.
• Uses the standard focusChat reply hook when a visible, editable input is present. Authenticated sending remains unverified.

RobotStreamer

Open https://robotstreamer.com/chat.html?c=CHANNEL_ID and keep Stream Chat selected for channel-only capture. Each new message, including messages grouped beneath the same author, uses platform/type: "robotstreamer", plain-text chatname, userid, chatimg, chatbadges, and nameColor. Message bodies preserve safe inline images; textonlymode uses literal text and image labels. Initial history and system notices are excluded. RobotStreamer deletions are not forwarded; remove moderated messages in the SSN dock if needed.

Castyr - DOM Capture

Implementation: sources/castyr.js

• Reads new rendered chat rows from https://castyr.live/homebeta/popout-chat/* and emits standard chat payloads with type: "castyr".
• Existing chat history is skipped when the source attaches.