Repository navigation
CrossChat 1.8.0
Highlights
- Signed Windows installer. Since 1.7.2,
CrossChat-Setup-<version>.exeis code-signed by Randy Northrup (Azure Artifact Signing), and the release workflow checks the signature before publishing. - Linux. A new download, tested with real OBS on Ubuntu 25.10 and, on every change, on Ubuntu 24.04 (OBS from the OBS Project's PPA and from Flathub).
- Mac, out of beta. Tested with real OBS 33.0.1 on Intel Macs (macOS 15.7) and, on every change, on an Apple-silicon Mac (macOS 26).
- Moderation tested live, with a second account in the chat (31 October 2026):
- Twitch: delete, timeout, ban and unban, also from the CrossChat dock inside OBS.
- YouTube: remove, 5-minute timeout and hide user; remove also from the dock.
- Kick: delete, timeout, ban and unban; timeout also from the dock.
- Facebook: delete a comment.
- Rumble: delete was tested on the streamer's own message in a real live; moderating another viewer isn't tested yet.
- Found and fixed by those live tests: YouTube moderation, Kick chat (it had stopped arriving) and Facebook comments (viewers' comments never reached CrossChat).
- Real OBS end to end on Windows, Mac and Linux on every change, plus CrossChat's windows placed and closed by its extension on every system.
Added
docs/COMPARISON.md: CrossChat next to Restream, Streamlabs, StreamElements, Social Stream Ninja, Casterlabs and Streamer.bot, each claim linked to that product's own page (checked 31 October to 1 November 2026).- Linux: a Linux download,
CrossChat-<version>-linux.tar.gz, installed withbash scripts/install.shinto~/.local/share/CrossChat(readable by your account only), with app-menu entries and an uninstaller. Checked on Ubuntu 25.10 with Ubuntu's OBS 30.2.3 and OBS 33.0.1 from Flathub, and on every change on Ubuntu 24.04 with OBS 32.2.0 from the OBS Project's PPA and 33.0.1 from Flathub (see the README's Linux section for exactly what, and what isn't checked yet).- Read-aloud uses the computer's own voices through speech-dispatcher. Google Chrome offers them only when it's started with
--enable-speech-dispatcher(without it, only Google's online voices, which CrossChat doesn't pick by itself). The installer says whether speech-dispatcher is there, and which packages add it. - Sign-ins are encrypted as on a Mac (AES-256 and HMAC-SHA256) under a key kept in your desktop keyring (Secret Service: GNOME Keyring, KWallet and others), through
secret-tool, which gets the key on its standard input, never on a command line. With no keyring, CrossChat keeps no sign-ins at all and says why: Twitch and Kick drop a sign-in they couldn't encrypt, and Rumble and Discord say the keyring's reason instead of "Could not save it". - OBS from Flathub works: the OBS script starts the hub outside OBS's sandbox with
flatpak-spawn, and the hub leaves when OBS does. The installer finds Ubuntu's (or any)obsand OBS from Flathub, switches on their WebSocket servers, and says when an OBS has no Browser Source (Ubuntu's and Debian's own package leaves it out, so the widgets need OBS from Flathub or the OBS Project's PPA). - The chat window opens in Chrome, Edge, Chromium or Brave, and the extension places, moves and closes it (see below), on X11 and on Wayland, where the desktop chooses the place and the extension sets the size. Without the extension it's done through X11, which on Wayland reaches the browser only when it runs through XWayland; otherwise the window opens where the desktop puts it, and "Open chat" doesn't open a second one.
- Tailscale for the companion away from home: only the address of Tailscale's own
tailscale0interface counts, while it's up. - The real-OBS check (
scripts/obs_e2e.py) runs on Linux with the installedobs(settings in a throwaway folder) or--obs flatpak, on an Xvfb display of its own when there's no desktop. On every change, GitHub's Ubuntu machines run the tests with a real keyring, real browser windows, an install and uninstall from the download, and OBS end to end from the OBS Project's PPA and from Flathub.
- Read-aloud uses the computer's own voices through speech-dispatcher. Google Chrome offers them only when it's started with
- The real-OBS check also starts OBS again 3 seconds after closing it, and checks its WebSocket server works and its script starts the hub again (every system).
- The CrossChat extension places, moves and closes CrossChat's own windows: the chat window, and the X, TikTok, Facebook, Instagram and Rumble pages it opens. It uses the browser's own window API, which needs no permission (the extension still asks for none), and touches only windows CrossChat opened: a bare
--appwindow with one tab at that window's own address, and for a page, the window CrossChat recorded or a new one at the exact address it opened. It never moves or closes a browser window of yours, even one with the chat open in a tab (SECURITY.md has the rules). The jobs come from the hub through the CrossChat window only, like replies. The system's own way stays for when the extension isn't there or can't. Reload the extension inchrome://extensionsafter updating.- macOS: it's the way that works when OBS starts the hub (macOS refuses AppleScript to programs OBS starts). Checked on macOS 15.7.4 (Intel Mac mini) with Chrome 156: the chat window and a page placed, the chat window moved by Open chat, both closed after the stream, with the Mac's own window server showing each window exactly there; and the same with OBS 33.0.1 starting the hub, which then left once OBS quit.
- Linux: checked on Ubuntu 25.10 with Chrome 153 on an X11 display (Xvfb), through KWin 6.4.5's XWayland (the X server showing each window exactly there), and on Wayland (KWin on a virtual screen, the browser as a Wayland program), where KWin chooses where a window goes (Wayland lets no program place one) and the extension sets its size (exactly, says KWin) and closes it. All at a display scale of 100 %.
- Windows: Windows' own way still places a window it can see, because the browser's window API counts Windows' invisible resize borders in: asked for 200,150 420x560, a browser window's visible frame was 207,150 406x553 on GitHub's Windows machines, while Windows' way puts the visible edges exactly in place. The extension closes the windows there, and places one Windows can't see; that part hasn't run on a real Windows desktop yet.
- A running browser opens a new window where it likes: Chrome takes
--window-positionand--window-sizeonly when it starts with that window (in the checks, every new window opened over the first one on macOS and Linux, and on Windows one asked for at 100,100 600x500 opened at 10,10 1004x700). So a chat window CrossChat opened is placed once it connects, and a page as soon as it shows. A window the desktop sizes again just after it opened (KWin on Wayland), or keeps maximized one way (KWin through XWayland, with a window that opened as tall as the screen), is placed again. scripts/window_e2e.pyis the real check: Chrome with a throwaway profile and the checkout's extension loaded over DevTools, the hub with a stand-in for OBS (or, on a Mac, OBS itself), decoy windows that must stay put, and where the desktop itself has the windows. The newwindow-controljob runs it on every change on GitHub's Ubuntu and macOS machines.
- Real OBS on Windows, on every change. The checks workflow's new
obs-windowsjob runsscripts/obs_e2e.pywith the portable OBS 33.0.1 from the OBS Project's release and ffmpeg 9.0.2 from gyan.dev, each download checked against the SHA-256 its maker publishes: all 27 checks pass on GitHub's Windows Server 2025, the three restart checks included. All three systems now run the same real-OBS check.
Fixed
-
A new window was looked for for 10 seconds only. A browser starting cold took 10 s to show its first window on GitHub's Ubuntu machines, where the real-window test failed once; such a window was left where the browser put it and wasn't closed after the stream. CrossChat now looks for up to 30 s, on every system.
-
Windows opening together could be taken for each other. TikTok's, Facebook's and Instagram's pages open together when the stream starts, and the system's way knows a new window by its not having been there before. They now open one at a time.
-
The hub stayed after OBS closed while a chat page was still open (the chat in a tab, or a chat window it couldn't close, as on a Mac), keeping its port: from Python 3.12.1, leaving the hub's server waits for every open connection, and a chat page's live feed never ends by itself. The hub now stops listening without waiting. Found while checking the windows; checked with OBS 33.0.1 on a Mac with the chat open in a tab.
-
Facebook comments showed in CrossChat with a stray "·" in front (the separator Facebook puts after the commenter's name).
-
Click here to retry in the CrossChat dock in OBS showed "not from another website" instead of the chat. When the dock loads before CrossChat answers, OBS shows its own error page, which has an origin of its own, so the hub took the retry for another website opening the chat window. The hub now opens the chat window for a click on a link to it in OBS's own browser (its User-Agent says
OBS/); anything else from another site is still refused (see SECURITY.md). Found with OBS 33.0.1 from Flathub on Linux, where the dock loaded before CrossChat answered in most starts. -
The real-OBS check's docked chat window was hidden on every system. The check wrote the dock into OBS's settings without a window layout, so OBS's first start ran Docks → Reset UI, which leaves Custom Browser Docks floating and hidden; the dock's page still loaded out of sight, so the check passed (on Linux it was skipped: the hidden dock often showed only OBS's error page). It now gives OBS a layout with the dock docked on the right, checks the layout OBS saves as it closes (it said "hidden, floating" before, on Windows, macOS and Linux), and presses Click here to retry when the dock opened too early. It runs on Linux too now.
-
Linux: the OBS script hands the hub only standard input, output and error. Without that, posix_spawn passes every file and socket OBS has open, as on a Mac (see below); on Linux it's closed with one file action (glibc 2.34 and newer), or one per open file on older systems.
-
The tests no longer close a real CrossChat window on the computer running them (the hub closes its chat window when OBS goes away, and some tests make OBS go away).
-
Mac: the hub no longer gets a copy of everything OBS has open. The OBS script started it with all of OBS's files and sockets, OBS's WebSocket server among them, so after OBS closed the hub kept OBS's WebSocket port taken (about 20 seconds in our tests), and an OBS opened again in that time couldn't start its WebSocket server (CrossChat then couldn't follow it). Found with OBS 33.0.1 on macOS 15.
-
Mac: the chat window's notice said "Start menu → CrossChat → Open chat"; on a Mac it now names Applications → CrossChat in the home folder. The Paired-devices hint about Windows' network question no longer shows on a Mac, and the Theme Studio's look button says "follows this device", not "follows Windows".
-
The chat window styled a first-time chatter's 1ST flag and line like the Settings "Set up your channels" note (a padded, bordered box), so the flag stood out of the line as a large pill and stretched the Q flag beside it. Seen in OBS's dock on a Mac; the same on Windows.
-
Mac: the README said macOS asks whether OBS may control your browser, so that CrossChat can move and close the chat window. It doesn't ask: macOS refuses Apple Events from programs OBS starts, because OBS 33 is signed without the entitlement for them (its log says
kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing). The README now says CrossChat can't move or close the chat window on a Mac; the window still opens where it should. -
Mac: the README and the installer say where the Applications → CrossChat folder is (the Applications folder in your home folder, not Finder's main one), and that
Install.commandhas to be started from Terminal: macOS 15 refuses to open it with a double-click, because the download isn't signed by Apple. -
Kick chat stopped arriving. Kick changed the key of its public chat feed, and Kick's server refused the one CrossChat had built in ("App key ... not in this cluster"), so Kick chat kept reconnecting and showed nothing. CrossChat now asks Kick for the current key the way Kick's own web chat does (signed out, with a random id), and falls back to the new one. When Kick's feed refuses a connection, the log says why.
-
YouTube moderation clicked the wrong button. YouTube now shows a top fan's "#1" rank inside the chat line, before the message's own menu, and CrossChat clicked that rank (opening the Top fans list) instead of the menu, so remove, timeout and hide user all failed with "YouTube did not offer that here". The extension now opens only the message's "Chat actions" menu. Reload the extension in
chrome://extensionsafter updating. -
YouTube moderation still couldn't work from the CrossChat window. YouTube offers the channel owner Remove, timeout and Hide user only on its own chat page; the chat embedded in the CrossChat window shows just "Go to channel" and "Pin message". The extension now moderates in YouTube's chat pop-out for the live, which it opens in a background tab of the browser (never in front; a minimized window only when no browser window is open). It keeps that one tab for the whole live, closes one left from an earlier live, reloads it if the extension was reloaded since, and the tab closes itself once the live is over or CrossChat has been unreachable twice in a row (half a minute apart). A pop-out you opened yourself is used but never closed.
-
YouTube timeouts weren't confirmed. YouTube now asks for the length in a "Timeout duration" dialog; CrossChat picks the length nearest the one asked for (5 minutes from the menu) and only reports the timeout done once Confirm has closed the dialog. The menu says "Timeout 5 minutes", and the window and the hub wait up to 75 seconds for a YouTube job, since the pop-out may have to load first.
-
Facebook comments stopped reaching CrossChat. Live Producer now puts a hidden avatar link to the comment before the commenter's name, so the name was read as empty and the comment was dropped. The name now comes from the first comment link with text.
Changed
- Linux is no longer a beta. On Ubuntu 25.10, on a virtual X11 display with Google Chrome 153: the OBS script and the hub following Ubuntu's OBS 30.2.3 and OBS 33.0.1 from Flathub, the widgets and the chat docked in OBS (Flathub), the installer and uninstaller, the desktop keyring, the extension (the chat window posts a test reply through it), read-aloud with speech-dispatcher's voices, and the phone companion (paired from a Windows PC, refused before pairing, with a wrong code, from another website and once removed). On every change, on Ubuntu 24.04, with OBS from the OBS Project's PPA and from Flathub. Not seen yet: a Linux desktop someone sits at, other distributions, and browsers other than Google Chrome. The README's Linux section lists exactly what.
- The Mac version is no longer a beta. CrossChat 1.7.1 and this version were run with OBS 33.0.1 on macOS 15.7.4 (Intel Mac mini) and 15.7.9 (Intel MacBook Pro): download and checksum, installer, the OBS script and the hub following OBS, the four widgets and the chat docked inside OBS, the login Keychain, the extension in Chrome 156, read-aloud with the Mac's voices, the phone companion (paired from a Windows PC and from the MacBook's Chrome), and the uninstaller. The README's Mac section lists exactly what.
- Real OBS on an Apple-silicon Mac, on every change. The checks workflow's new
obs-macjob installs OBS and ffmpeg from Homebrew on GitHub's Apple-silicon Mac (macOS 26), installs CrossChat from the Mac download and runsscripts/obs_e2e.pyagainst that OBS: all 24 checks pass with OBS 33.0.1. It can also be started by hand. - The real-OBS check (
scripts/obs_e2e.py) runs on a Mac too, with the installed OBS.app and a stand-in home folder, so your own OBS settings are never touched. It also checks that OBS's own browser shows the four widgets and the docked chat (with test chat in it), and that OBS's WebSocket port is free once OBS closes.--crosschattests an installed copy,--ffmpegnames the RTMP receiver, and the logs are kept when something fails. - The hub's start line in
crosschat.lognames the Python running it. - The README says what to do when the CrossChat dock in OBS says "Couldn't load that page!" (OBS opened it before CrossChat was ready: press "Click here to retry"), and that OBS on a Mac needs the Input Monitoring permission for hotkeys while another app is in front.
- README's Known limits say what moderation was checked live on 31 October 2026, with a second account in the chat, on both sides (the viewer's and the streamer's):
- Twitch delete, timeout, ban and unban work, from the CrossChat window in Chrome; timeout and unban also from the CrossChat dock inside OBS.
- YouTube remove, 5-minute timeout and hide user work from the CrossChat window (with the fixes above, in an unlisted live), and remove from the CrossChat dock inside OBS. In 1.7.1 all three had failed. The pop-out tab closed itself after CrossChat was closed.
- Kick delete, timeout, ban and unban work from the CrossChat window, and timeout from the CrossChat dock inside OBS.
- Facebook: deleting another commenter's comment (a Facebook Page's, on a short public test live) works from the CrossChat window.
- Rumble moderation of a viewer still hasn't been seen working: Rumble's sign-up for a test account stopped at Cloudflare's "Verify you are human" check ("Verification failed").
- A reply typed once in the CrossChat window reached Twitch, YouTube and Kick chat.
Code signing: the Windows setup program is signed with Azure Artifact Signing (publisher: Randy Northrup). Policy: see the README. Check any download with gh attestation verify <file> --repo RandyNorthrup/crosschat-obs.