Unsubscriby for Rumble

An easy way to unsubscribe all your Rumble Channels

What is Unsubscriby for Rumble?

Unsubscriby for Rumble is a Chrome extension that allows you to easily unsubscribe from all your Rumble channels. Simply install the extension, click on the Rumble icon, and start the unsubscribe process. It navigates to your subs list, confirms the action, and unsubscribes everything for you. It's quick, convenient, and saves you time.

Download

Extension stats

By: https://limbuscode.com

View on Chrome Web Store

Users: 24

Rating: 5.00 (1)

Version: 0.0.1 (Last updated: 2024-01-06)

Creation date: 2022-05-12

Risk impact: Moderate risk impact

Risk likelihood: Low risk likelihood

Manifest version: 3

Permissions:

tabs
storage
scripting

Host permissions:

https://www.rumble.com/account/channel/subscriptions
https://rumble.com/account/channel/subscriptions

Size: 1.73M

Email: li*****@gmail.com

URLs: Website

Ranking

# 104319 ▼ 536

Other rankings

#34535 in Workflow & Planning ▼ 40 #256 in stop keyword 12 ▼ 7

Other platforms

Not available on Firefox

Not available on Edge

Want to check extension ranking and stats more quickly for other Chrome extensions? Install Chrome-Stats extension to view Chrome-Stats data as you browse the Chrome Web Store.

Extension summary

Analyze keywords

How it works:

First, install this extension.
Next, click on the gray rumble icon next to your URL bar. Don't see the icon? Click on the puzzle piece, and then click on the pin to move it to your URL bar.
Click on "Unsubscribe!" buton to start the process.
The extension will navigate to your subs list, click "OK" to the popup message to confirm and start to unsubscribe. (If the popup doesn't show up, please refresh the tab until it does).
Wait until it finishes.
If you are using Free Version, when it finishes, just refresh the page to continue.
If you want to stop the process while it is running, click on the gray rumble icon next to your URL bar, then click on "Stop!" button.

Not working? Comment or email me so that I can address the issue.

Changelog:

v.0.0.1: