RumbleX is a comprehensive browser script that supercharges your Rumble.com experience. It injects a powerful suite of tools directly into the Rumble interface, giving you unparalleled control over everything from layout and privacy to video playback and downloading.
Repo SysAdminDoc/RumbleX, read from GitHub 1 d ago. SysAdminDoc has not joined Take My Repo.
SysAdminDoc/RumbleX is a public repo on GitHub by SysAdminDoc. RumbleX is a comprehensive browser script that supercharges your Rumble.com experience. It injects a powerful suite of tools directly into the Rumble interface, giving you unparalleled control over everything from layout and privacy to video playback and downloading. It declares the MIT license on GitHub. It is written mainly in JavaScript, has 5 stars and last changed on 2026-09-25. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-21.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
Rumble, rebuilt around the way you watch. RumbleX is an open-source control layer for Rumble with cleaner pages, serious download tools, a better player, and local-first privacy. Pick only the features you want. Leave the rest off.
Get the latest release | Installation guide | See every change

| What you get | What changes |
|---|---|
| A calmer site | Remove ads, premium prompts, Shorts, noisy feed rows, overlays, and 50 more pieces of page clutter. |
| A player built for long sessions | Use Theater Split, persistent speed and volume, chapters, SponsorBlock, transcripts, a mini player, and per-channel preferences. |
| Downloads that explain themselves | Save direct MP4, convert HLS, export clips, batch a feed, or queue a channel. When something fails, RumbleX names the failed stage and gives you a useful next step. |
| Your own visual system | Choose from seven complete themes, three density levels, an optional ambient player, and layouts that hold up from a narrow side panel to a wide display. |
| Better live chat and comments | Keep paid messages, block noisy users, remove repeated spam, highlight keywords, sort comments, and export the conversation. |
| Privacy you can inspect | No telemetry, remote configuration, or RumbleX account. Settings, watch activity, bookmarks, diagnostics, and undo snapshots stay in your browser. |
| Control center | Full settings editor |
|---|---|
![]() |
![]() |
| Built-in privacy report | Quick controls on Rumble |
|---|---|
![]() |
![]() |
All builds use the same checked page-feature core. Release checks verify that the extension and generated userscripts have not drifted apart.
This release is a full reliability and interface pass across the extension, userscripts, Options, popup, Theater, chat, downloads, backups, and release tooling.
This release expands the visual system while keeping the watch page focused.
The extension controls and Theater panel have had a complete visual and accessibility pass.
This pass finishes the visual work around watch pages and keeps secondary tools from crowding the native video details.
Theater Split's side panel now behaves like one workspace instead of several stacked widgets.
The main Rumble surfaces get another visual refinement pass after the larger v3.51 rebuild.
This release finishes the current roadmap and hardens the shared runtime underneath the website overhaul.
This release is a visual rebuild of the Rumble website itself.
Downloads, captions and creator numbers, plus a notifier that had quietly stopped working.
Live chat got the things every other chat platform already has, and rants became something you can total up.
@ and RumbleX offers the people who have actually spoken this session, ranked so prefix matches come first. Arrow keys and Escape work the way you expect..info.json, a Jellyfin/Kodi .nfo and the thumbnail can be saved alongside a video, named to match so a media server pairs them.!!! while leaving ordinary titles and acronyms alone.discordWebhookUrl reached an outbound request without any URL validation, so a crafted backup, snapshot, or encrypted-Gist restore could silently install an arbitrary destination for followed-channel activity. Only HTTPS Discord webhook endpoints are accepted now, the destination is re-checked before every POST, and a configured webhook is listed in the local Privacy Report.article.video-item search results now work with quick-save, batch download, progress, filters, title/thumbnail controls, and health checks. Bulk Unsubscribe recognizes /followed-channels and /account/recurring-subs, and Wallet Tip recognizes the current QR endpoint.RxErrorLog.record() carried a readiness guard left over from when capture consulted a setting; it threw away the one window a user cannot retry, so the diagnostics export was empty for exactly the failures worth reporting.locator.count() racing an asynchronous render.AutoMaxQuality always pinned the highest rendition, which is the worst possible answer to buffering. It now honours a quality ceiling and floor, and qualityMode. which shipped with four documented values and no runtime consumer at all. Three stalls inside 30 seconds drops one rendition and says why./playlists/<id> is a route RumbleX understands. Batch Download mounts and multi-selects there, and Channel Archive can enqueue a whole playlist. This also fixed the archive parser, which only matched relative card hrefs and so would have found nothing on a playlist page.content.js had zero i18n calls, so four locales covered the extension's own pages while every string on rumble.com stayed English. 313 keys are wired: every toast, the download panel, and the whole settings modal including all 137 feature labels and 124 descriptions, in German, Spanish and Brazilian Portuguese. Feature search indexes the translated text, so searching in German finds German.<div>/<span> elements. All 22 injected surfaces now get a per-surface axe WCAG 2.2 AA scan, which also caught secondary text failing contrast at 3.35:1 and four buttons under the 24x24 target-size minimum.destroy() detached the panel but kept the reference, and the mount guard reads that reference. Found by the new per-surface scan, which could not mount three of them for exactly this reason.Settings.init() replaced the whole cache and reset its pending-write set, so any save that landed while it was still reading storage vanished while reporting success. This was also the root cause of an intermittent test failure that had been reproducing roughly one run in three.<div>/<span> elements. Both are real buttons now, and twelve injected panels that carried zero aria attributes have roles and accessible names.<video> instead of leaving it decoding audio.encryptedGistSync, privacyReport), two dead duplicates were removed with a schema migration, and the remaining 38 are labelled "Not implemented yet" with a stated reason and disabled inputs. A guard fails in both directions so the list cannot rot.a-delivery.rmbl.ws is blocked. It is a CNAME alias of the already-blocked ad host, and hostname matching never follows CNAMEs, so it had been passing through every runtime. All three hand-synced host lists are now machine-checked against each other.RumbleX.lite.user.js. a Greasy Fork-compliant build with the same shared runtime, minus the bundled transmuxers.aria-live announcer for all in-page feedback, replacing three implementations of which only one was announced to assistive tech.Large HLS without tab-sized buffering. supported Chromium desktops can stream a selected HLS quality directly into a user-chosen .ts file, one response chunk at a time. Cancellation aborts the network reader and staged file write; MP4 remuxing remains safely capped at 512 MiB.
Visible drift detection. the local Privacy Report now identifies critical route selectors as healthy, fallback, or broken, and a missing high-value anchor produces a one-time in-page warning instead of silently disabling features.
Proven Firefox MV2 runtime. a repeatable Firefox temporary-addon smoke covers content injection, storage, deletion, response messaging, and bundled media assets. Shield UI now distinguishes Chromium DNR, Firefox webRequest, and manager-dependent userscripts.
One shared feature core. Chrome MV3, Firefox MV2, Tampermonkey, and Violentmonkey now execute the same canonical page-feature code. A build-time guard rejects stale userscripts, version drift, missing settings/modules, direct chrome.* use, and remote code loading.
Current Rumble support. Public <rum-video-thumbnail> cards, signed-in <rum-card-video> feeds, SPA watch-route changes, the floating related grid, visible action anchors, and every current embed HLS response shape are covered by committed fixtures and loaded-extension tests.
Safer downloads and imports. downloads are cancellable and bounded before large media can exhaust tab memory; imported settings, snapshots, queue URLs, and compressed backups are size- and schema-validated.
Complete local media bundle. the userscript embeds the pinned mux.js and Mediabunny workers/libraries. It never fetches or evaluates executable code from a CDN.
Request-level ad shield. Chrome/Edge/Brave use a Rumble-scoped MV3 ruleset and Firefox uses a scoped MV2 blocking listener for the verified ad-delivery/measurement surface; Ad Nuker remains the DOM cleanup layer for sponsored cards, overlays, and reserved space.
Desktop settings redesign. the options control center, complete settings editor, popup, and in-page modal now share an OLED-black/Rumble-green system with clearer discovery, network-shield state, save/reset feedback, and verified 1440×900 and 1920×1080 layouts.
:has()hugh.cdn.rumble.cloud for quality variants the embed API did not surface, with live progress, per-row copy-link buttons, and TAR live-replay support..m4a exactly as Rumble serves it, with no conversion. Videos that don't publish one say so rather than handing you a video file. Set Audio Extraction to external to copy the track's link for a download tool instead, or to off to hide the control.innerHTML round-trip)Driven by the RX_CSS_TOGGLES registry. each toggle is a proper feature module with its own setting key, hot-reload support, and options-page card:
| Group | Count | Sample toggles |
|---|---|---|
| Main Page Layout | 25 | widenSearchBar, hideUploadIcon, hideHeaderAd, hideFeaturedBanner, hideForYouRow, hideGamingRow, hideFinanceRow, hideNewsRow, hideSportsRow, hideFooter, … |
| Video Page Layout | 5 | hideRelatedOnLive, hideRelatedSidebar, widenContent, hideVideoDescription, hidePausedVideoAds |
| Player Controls | 9 | hideRewindButton, hideCCButton, hideAutoplayButton, hideTheaterButton, hidePipButton, hideFullscreenButton, hidePlayerRumbleLogo, hidePlayerGradient, … |
| Video Buttons | 8 | hideLikeDislikeButton, hideShareButton, hideRepostButton, hideEmbedButton, hideSaveButton, hideCommentButton, hideReportButton, hidePremiumJoinButtons |
| Comments | 2 | moveReplyButton, hideCommentReportLink |
| Chat | 1 | cleanLiveChat |
Click the extension icon → gear button to open the dedicated options page. Modelled on Astra-Deck's settings workspace:
rx_settings AND your activity (watch progress, watch/search history, bookmarks, volume memory, rant archives), plus the cross-video rant summary. Export format: exportVersion: 3. Files from versions 1 and 2 still import. Imports are allowlisted by key so a crafted file cannot smuggle arbitrary localStorage keys onto rumble.com.clearLocalData to every open Rumble tab and reports the honest "Cleared N per-site keys across M tabs" countchrome.storage.onChangedClick the visible RumbleX settings gear on any Rumble page (or shift-click the extension popup gear) to open the in-page settings modal with:
Click the extension icon for quick toggles, grouped by category with enabled-count badges:
pagehide flush. rapid toggles coalesce into one writeInstall instructions for every browser, plus the checksum and signature commands, also live on the project page at https://sysadmindoc.github.io/RumbleX/. That page and this repository are the only official sources.
RumbleX-chrome.zip from Releaseschrome://extensions and enable Developer modeEach release also includes RumbleX-chrome.crx, signed with the project's local self-host key. It is a secondary package for managed or policy-enabled browsers. Standard Chrome, Edge and Brave installs outside their stores can reject direct CRX installation, so the ZIP and Load unpacked remain the dependable path.
Chromium 111 is the minimum because RumbleX uses color-mix() for themed translucent controls and the modern abort timeout API for bounded network work. Current Chrome, Edge, and Brave releases meet that floor. RumbleX still detects either the chrome or browser extension namespace so the shared page-feature core remains browser neutral.
RumbleX-firefox-amo-unsigned.zip from Releases and extract itabout:debugging#/runtime/this-firefoxmanifest.json inside the extracted folderFirefox 121 is the minimum because RumbleX uses :has() selectors and color-mix() across its cleanup rules and seven themes.
That ZIP is the reproducible AMO submission and a temporary testing package. It is not a permanently installable add-on. An installable RumbleX-firefox.xpi is published only after Mozilla returns a signed package and the artifact check confirms its signature entries.
Install RumbleX.user.js directly. It is generated from the byte-identical shared page-feature core and embeds the pinned mux.js and Mediabunny media workers.
The userscript supports settings, themes, page cleanup, selectors/routes, screenshots, direct/HLS/clip/audio/batch downloads, diagnostics, and local backup data. Browser-extension-only capabilities that require a persistent privileged background remain intentionally unavailable: the channel archive queue/recovery service, alarms, native notifications, context menus, side panel, and tab grouping.
Its metadata also requests early ad cancellation through the userscript-manager @webRequest facility. Manager/browser support is not uniform: current Chromium MV3 Tampermonkey does not expose that request hook, so the userscript UI and Privacy Report mark the shield as manager-dependent and do not claim extension-level network blocking there. Ad Nuker still performs document-start and reinsertion cleanup.
Direct downloads save by name through the manager's GM_download, which Tampermonkey and Violentmonkey both provide. A manager without it can't hand a file on Rumble's media server to the browser under a name of RumbleX's choosing, so RumbleX fetches the file through GM_xmlhttpRequest and saves that copy instead. The whole file sits in the tab until it's saved, so that route stops at 512 MB and tells you. Anything bigger needs Tampermonkey, Violentmonkey or the extension.
On Chromium browsers a correctly installed userscript can sit there doing nothing until you grant the manager permission to run user scripts. Nothing warns you on the page, so this looks exactly like RumbleX being broken.
Chrome 138 and newer: open chrome://extensions/?id=<your manager's ID> (or right-click the Tampermonkey icon and pick Manage extension) and turn on Allow User Scripts. It is a per-extension toggle and it is off by default on a new install. Chrome 137 and older use the global Developer mode switch at the top of chrome://extensions instead.
Edge: Edge builds have not shipped the per-extension toggle. Users still report it missing as recently as Edge 143, so the working answer there is the Developer mode switch at the top of edge://extensions.
Once it is on, reload the Rumble tab. If the RumbleX button still does not appear, see the next section before assuming a match failure.
Both faults look identical from the page: no RumbleX button, no toast, no console error. They need opposite fixes, and there is a way to tell them apart.
Open any rumble.com page, open DevTools, and run:
Object.keys(localStorage).filter((k) => k.startsWith('rx_'))
@match rules are fine and the script is reaching the page. What changed is permission or state: check the Allow User Scripts toggle above, then check the script is still enabled in the manager dashboard.The extension builds are not affected by any of this. They have no userscript manager in the path.
Every release ships SHA256SUMS.txt covering the Chrome ZIP and signed CRX3, the unsigned Firefox AMO submission, its source archive, and both userscripts. Check what you downloaded against it:
sha256sum -c SHA256SUMS.txt --ignore-missing
That proves the file arrived intact. It does not prove who built it. A release can also carry SHA256SUMS.txt.sig after the project publishes an SSH signing identity in allowed_signers. When both files are present, verify the origin too:
ssh-keygen -Y verify -f allowed_signers -I release@rumblex -n file \
-s SHA256SUMS.txt.sig < SHA256SUMS.txt
A Good "file" signature result means the checksums came from the key published in this repository. If either check fails, do not install the files. The only official sources are this repository's Releases page and the raw userscript URLs above; copies elsewhere are not ours.
v3.61.0 is unsigned because the project does not yet have a published release signing identity. Use SHA256SUMS.txt to verify download integrity, and treat the lack of a signature as an explicit limit on provenance.
| Runtime | Early request layer | Reported state |
|---|---|---|
| Chrome / Edge / Brave extension (MV3) | 7 scoped Declarative Net Request rules | chromium-dnr, runtime-enforced |
| Firefox extension (MV2) | 7 scoped blocking webRequest checks |
firefox-webrequest, runtime-enforced; Firefox 137 temporary-addon smoke covered |
| Tampermonkey / Violentmonkey userscript | Static 7-host @webRequest request, where the manager exposes it |
userscript-manager-dependent; DOM cleanup guaranteed, early cancellation not claimed |
All three copies of the blocked-host list are machine-checked against each other by npm run test:ad-blocking, so a host cannot be added to one runtime and forgotten in another. One difference is structural and intentional: @webRequest selectors are globs, so the first-party affiliate rule (a regex over rumble.com/l/...?af=) exists in the DNR ruleset and the Firefox listener but cannot be expressed in the userscript at all. Every blocked host is present in all three.
Last verified against production Rumble: 2026-09-25. A cold-load audit of the home and watch surfaces recorded no completed ad responses and no visible ad DOM (RUMBLEX_AD_NETWORK_AUDIT=1 npx playwright test tests/e2e/ad-network-live.spec.js). That audit only observes hosts it already knows about, so it is a regression check rather than a discovery tool. Re-date this claim on every release rather than treating it as permanent.
RumbleX intentionally does not request Declarative Net Request feedback/debug permission for per-rule history. The settings and Privacy Report expose the enforcement mode and declared rule count without retaining request URLs or browsing history.
chrome.storage.local (extensions) or GM_*Value (userscript) for settings persistencelocalStorage. Existing installs move it over once, on the first Rumble page after updating, keeping a copy of what was there to roll back to.AbortController + generation-counter guards for cancellable async workdocument_startrumble.com, 1a-1791.com, rumble.cloud) enforced in the background workerflowchart LR
Site[Rumble page] --> Core[Routing + selectors + cards + media]
Extension[Chrome / Firefox adapter] --> Core
Userscript[Tampermonkey / Violentmonkey adapter] --> Core
Core --> Content[content.js feature modules]
Content <--> Worker[worker.js / mediabunny-worker.js]
Content <--> Background[background.js service worker]
Popup[Popup / Options / Side panel] <--> Background
Content <--> Storage[chrome.storage.local, or site localStorage in userscripts]
Background <--> Storage
Background --> Downloads[chrome.downloads]
Background <--> Offscreen[offscreen document]
Userscript --> Embedded[Embedded pinned media workers]
settings-schema.js owns defaults, migration, and validation for every runtime. activity-store.js owns activity merge rules and the snapshot key registry. Four core-*.js files own routing, selector health, card adaptation, and media/probe helpers. content.js holds the injected feature modules. The browser extension and generated userscripts load those sources in the same order, with a hash guard that catches drift. extension/platform.js and userscript/platform.js adapt storage, downloads, network requests, assets, localization, and capabilities. background.js remains the extension-only privileged boundary for serialized durable writes, persistent downloads, context menus, notifications, tab operations, queue alarms, and offscreen work. Popup, options, and side-panel pages edit the same validated settings catalog in chrome.storage.local. Browser-extension activity such as history and bookmarks also lives in extension storage. Userscripts keep that activity on the Rumble origin because they have no extension store.
const ExampleFeature = {
id: 'exampleFeature',
name: 'Example Feature',
_control: null,
_routerUnsub: null,
_mount() {
const anchor = Selectors.find('watch.share');
if (!anchor || this._control) return;
this._control = document.createElement('button');
this._control.type = 'button';
this._control.textContent = 'Example';
anchor.after(this._control);
},
init() {
if (!Settings.get(this.id)) return;
this._mount();
this._routerUnsub ||= Router.onChange(({ changed }) => {
if (!changed) return;
this._control?.remove();
this._control = null;
this._mount();
});
},
destroy() {
this._routerUnsub?.();
this._routerUnsub = null;
this._control?.remove();
this._control = null;
},
};
Add the module to features, put new DOM contracts in Selectors._map, and keep its setting/default metadata synchronized across content, popup, and options catalogs. destroy() must remove every node, style, observer, listener, timer, and route subscription created by init().
chrome.downloads.LiveChatEnhance uses a TreeWalker on Text nodes only. Rumble's chat markup is never re-parsed through innerHTML.setLocalData rejects any key outside the RX_LOCAL_STORAGE_KEYS list + rx_rants_ prefix, so a crafted file cannot write arbitrary keys to rumble.com's origin.Run the mandatory local gate from the repository root:
npm run verify
This runs every non-live source guard, the selector contracts, the headless Firefox smoke, and the full Playwright suite before it writes a package. It then builds the Chrome package, unsigned Firefox submission, AMO source archive, and userscripts before checking the archived files.
Create a clean local release with the same gate:
npm run release:local
The release command first refuses a dirty Git tree, then removes known old package outputs, runs npm run verify, rebuilds the final files, and checks the archive bytes again. Browser packages and the AMO source bundle only copy Git-tracked files, so an ignored browser file or a local scratch file cannot leak into an archive. A failed guard stops before packaging. Requires zip; on Windows without zip, the build uses the Windows-bundled bsdtar so ZIP entries keep browser-safe forward-slash paths.
The selector tests use checked-in, synthetic desktop captures. Private MHTML captures in Sample Pages/ are optional local evidence and never enter release packages: test_selectors.py reports their absence and carries on. Live-site checks remain opt-in because network and account state are not deterministic release inputs.
Five specs need a page rich enough for every injected surface to mount, so they use tests/fixtures/platform/offline-watch.html, a reduced capture that is committed. npm run verify therefore runs on a clean clone with nothing but npm ci and npm run test:e2e:install.
The fixture keeps the real structure and replaces everything that identifies a person, a session, or the capturing browser: channel and account names wherever they appear including visible text, the follow list's slug, title and id attributes, numeric ids inside hx-vals JSON, chat usernames and message ids, the video's own title, description, canonical URL, slug and embed id, server-minted data-epk and event blobs, CDN path segments, every asset URL, and Dark Reader's attributes and inline properties. Each identity hashes to one synthetic value, so a name that appears in five places still reads as the same person. tests/e2e/secret-policy.spec.js asserts every one of those classes on the committed bytes.
Regenerate it from a local capture rather than hand-editing. npm run test:offline-fixture compares the file against the generator where a capture exists, and against offline-watch.sha256 everywhere else, so a hand-edited fixture fails even in a clone:
npm run build:offline-fixture -- path/to/capture.html
Release builds can sign the checksums after a public identity exists. Point RUMBLEX_SIGNING_KEY at the matching private key and the build writes SHA256SUMS.txt.sig, then verifies it against allowed_signers before finishing:
RUMBLEX_SIGNING_KEY=~/.ssh/rumblex_release npm run release:local
A signature that does not verify against the published key fails the build rather than shipping. Builds without the variable set are unsigned and say so. Unsigned public releases must state that on the release page.
Each build produces RumbleX-firefox-amo-unsigned.zip as the unsigned AMO submission and RumbleX-source.zip as the source bundle AMO review asks for, since the package ships two minified libraries. It never renames the unsigned ZIP to .xpi. Run npm run build-for-amo from the repository root to reproduce the Firefox submission bytes, then run npm run test:firefox-artifacts to verify the artifact boundary. If RumbleX-firefox.xpi exists, that check requires a complete Mozilla JAR or COSE signature entry set.
The Chromium build also creates RumbleX-chrome.crx from the exact files in RumbleX-chrome.zip. It reuses the gitignored RumbleX-selfhost.pem key, creating it on the first local build. The package guard verifies the embedded ID and RSA-SHA256 proof, rejects a changed signed payload, then compares every CRX3 file with the ZIP before release.
Provenance for the vendored libraries is recorded in extension/lib/VENDOR.json: package, version, npm tarball URL, SHA-256, and the command that reproduces the exact bytes. npm run test:vendor-manifest checks that record against the files on disk and against the hashes pinned in build.sh, so the three cannot drift apart.
docs/updates.json is the Firefox update feed for self-distributed signed builds, served from GitHub Pages. Regenerate it when a signed XPI exists:
npm run build:update-manifest -- --xpi path/to/rumblex-<version>-signed.xpi
npm run test:update-manifest
MIT
SysAdminDoc/RumbleX is a public repo on GitHub by SysAdminDoc. RumbleX is a comprehensive browser script that supercharges your Rumble.com experience. It injects a powerful suite of tools directly into the Rumble interface, giving you unparalleled control over everything from layout and privacy to video playback and downloading.
It declares the MIT license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-09-25. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Morphe privacy patches for Twitch, Kick and Rumble. Watch the stream, skip the tracking.
一个基于 JavaScript 的网盘文件下载地址获取工具。基于【网盘直链下载助手】修改 ,支持 百度网盘 / 阿里云盘 / 中国移动云盘 / 天翼云盘 / 迅雷云盘 / 夸克网盘 / UC网盘 / 123云盘 八大网盘

Hushfacebook Morphe patches for Facebook. Hide ads, suggested posts, save videos and photos, tune playback and Reels, and use a focused Marketplace mode, and much more.
HushGram v0.0.21: Morphe patches for Instagram that hide ads, suggested posts and much more. 186 patches for Instagram 456.0.0.53.78.
Morphe patches for Facebook Messenger. Privacy switches and fewer promotions.

Local-first, open-source Android automation with readable rules, honest permission gates, and no account or cloud runtime.

Inspect, debloat, back up, freeze, and control Android apps from one open-source package manager. Works without root, with Shizuku, ADB, or root when needed.
Take My Repo has not tested this on your machine. Requirements come from the project's own documentation.