-
-
Save angeld23/b01dd2ef14cd53fc3735fa88f68b7aef to your computer and use it in GitHub Desktop.
// ==UserScript== | |
// @name Remove Twitter Blue Promotions | |
// @namespace https://d23.dev/ | |
// @version 1.1 | |
// @description Removes the "Get Verified" box on the Home page and the "Verified" button on the sidebar | |
// @author angeld23 | |
// @match *://*.twitter.com/* | |
// @icon https://www.google.com/s2/favicons?sz=64&domain=twitter.com | |
// @grant none | |
// ==/UserScript== | |
"use strict"; | |
(() => { | |
/** | |
* Calls the provided callback when the document is loaded | |
*/ | |
function onReady(fn) { | |
if (document.readyState != "loading") { | |
fn(); | |
} | |
else { | |
document.addEventListener("DOMContentLoaded", fn); | |
} | |
} | |
/** | |
* Waits for Element added as a descendant of `parent` that matches `selector`. | |
*/ | |
function waitForElement(parent, selector, callback, runOnce = true) { | |
const elementNow = parent.querySelector(selector); | |
if (elementNow) { | |
callback(elementNow); | |
if (runOnce) { | |
return; | |
} | |
} | |
const observer = new MutationObserver((records) => { | |
records.forEach((record) => { | |
record.addedNodes.forEach((parentElement) => { | |
if (parentElement instanceof Element) { | |
parentElement.querySelectorAll(selector).forEach((element) => { | |
if (runOnce) { | |
observer.disconnect(); | |
} | |
callback(element); | |
}); | |
} | |
}); | |
}); | |
}); | |
observer.observe(parent, { | |
childList: true, | |
subtree: true, | |
}); | |
} | |
onReady(() => { | |
waitForElement(document, "aside[aria-label='Get Verified']", (element) => { | |
setTimeout(() => { | |
element.parentElement?.remove(); | |
}, 100); | |
}, false); | |
waitForElement(document, "a[aria-label='Verified'][href='/i/verified-choose']", (element) => { | |
setTimeout(() => { | |
element.remove(); | |
}, 100); | |
}, false); | |
}); | |
})(); |
yeah twitter doesn't load when using this extension
The userscript prevents the site from loading, however when I disable the userscript, then load Twitter, then reenable the userscript, Twitter stays up even when browsing through the site, and the userscript still works.
EDIT: nevermind it doesn't work like this for me anymore
/**
* Calls the provided callback when the document is loaded
*/
function onReady(fn) {
if (document.readyState != "loading") {
fn();
}
else {
document.addEventListener("DOMContentLoaded", fn);
}
}
/**
* Waits for Element added as a descendant of `parent` that matches `selector`.
*/
function waitForElement(parent, selector, callback, runOnce = true) {
const elementNow = parent.querySelector(selector);
if (elementNow) {
callback(elementNow);
if (runOnce) {
return;
}
}
const observer = new MutationObserver((records) => {
records.forEach((record) => {
record.addedNodes.forEach((parentElement) => {
if (parentElement instanceof Element) {
parentElement.querySelectorAll(selector).forEach((element) => {
if (runOnce) {
observer.disconnect();
}
callback(element);
});
}
});
});
});
observer.observe(parent, {
childList: true,
subtree: true,
});
}
onReady(() => {
waitForElement(document, "a[href='/i/verified-choose']", (element) => {
setTimeout(()=> {
if (element.parentNode && element.parentNode.nodeName.toLowerCase() === 'nav') {
element.remove();
} else if (element.parentNode && element.parentNode.parentNode) {
element.parentNode.parentNode.remove();
}
}, 2000);
}, false);
});
I finally got the new twitter. It seems like they are detecting if the divs are missing and are starting a infinite loop that lags the page and crashes it.
Anyway, I just added a timeout before removing the element and also, made the script load on document-end instead of document-start
I went ahead and added a 100ms delay before the element removal which seems to bypass that page-crashing infinite loop some mouthbreather at Twitter added. Let's hope the little lord boy Musky Elon doesn't demand they patch it again
Seems they did patch it again, hasn't been working since last night.
Well, it's buffered forever again.
It is still not working any longer. 🔢
I think they might have added a check that blocks the loading of content if the Twitter blue ads aren't there, somewhere in the lifecycle of the website. I got it working again by adding a 400ms timeout before removing the elements. Not ideal but it's better than nothing. It's the only solution I found.