Today's Pet Peeve:
LOUD music intended to be "background" music but is so d@mn loud that you have to "raise your voice" to talk to somebody sitting TWO FEET AWAY.
Today's lunch was at Outback Steakhouse.
A place I have avoided in the past ON ACCOUNT OF "loud background music".
Today was actually so PERFECT that I requested the manager to visit our table.
I complimented him on the volume setting of the BACKGROUND music.
He went on to probably tell the whole table more than he was quote-unquote "supposed to".
He's been managing for only a week and informed us that the background music system has TWO settings.
One nice and quiet and soft for the LUNCH (noon) crowd and one a bit louder for EVENING when there are 50/80 people dining instead of 10/20.
And told us that the previous manager was "let go" because she kept it at the EVENING setting ALL THE TIME.
Even the wait staff was complaining that they were getting orders wrong because they couldn't hear over the D@MN "background" music.
Due to server slowness, downtime, and other issues, guests can no longer search the forum or view user accounts. At some point in the future Eclipse will be moving to a more stable and efficient platform that should result in much better stability and the lifting of these restrictions. There is no timeline for this yet, just want you to know what's happening with all the downtime and I have a plan to fix it.
Today's Pet Peeve
-
The-10-Pen
- Posts: 632
- Joined: 16 Feb 2025, 08:43
- OS: Win10 2016 LTSB
- Has thanked: 9 times
- Been thanked: 101 times

-
The-10-Pen
- Posts: 632
- Joined: 16 Feb 2025, 08:43
- OS: Win10 2016 LTSB
- Has thanked: 9 times
- Been thanked: 101 times

-
The-10-Pen
- Posts: 632
- Joined: 16 Feb 2025, 08:43
- OS: Win10 2016 LTSB
- Has thanked: 9 times
- Been thanked: 101 times

Today's Pet Peeve
Today's Outrage -- cookie banner notifications.
What a nuisance!
One of the most annoying "mandates" to ever come out of the EU.
Adopted in 2002, amended in 2009, enacted in 2011/2012.
Enough already! It's 14/15 **YEARS** later and we are still being PUNCHED IN THE FACE by these D@MN *nuisances*!
uBO's filters lists DO NOT block ALL of them !!!
I Still Don't Care About Cookies extension does NOT block ALL of them !!!
Everything I have tried in the past 14/15 years seems to do okay for the most part, but you still encounter these PIECES OF SH#T.
Enough already!
So it's time for a more generic approach and one FULLY controlled and editable by me, no more waiting for uBO filter lists not catching these to be updated but never updated to catch them ALL, no more waiting for extensions to be updated but never updated to catch them ALL.
Working so far!
// ==UserScript==
// @name - Auto Hide Cookie Banners
// @version 1.0.1
// @match *://*/*
// @grant none
// @run-at document-idle
// ==/UserScript==
(function () {
'use strict';
// Common CSS selectors for cookie banners and consent popups
const selectors = [
'[id*="cookie"]',
'[class*="cookie"]',
'[id*="consent"]',
'[class*="consent"]',
'[aria-label*="cookie"]',
'[aria-label*="consent"]',
'div[role="dialog"]'
];
// Try to click reject/decline buttons if found
const rejectButtonTexts = [
'reject', 'decline', 'no thanks', 'opt out', 'refuse'
];
function removeCookieBanners() {
selectors.forEach(sel => {
document.querySelectorAll(sel).forEach(el => {
// Try to find and click reject buttons inside the banner
const btn = Array.from(el.querySelectorAll('button, a'))
.find(b => rejectButtonTexts.some(txt =>
b.textContent.trim().toLowerCase().includes(txt)
));
if (btn) {
btn.click();
console.log('[CookieBlocker] Clicked reject button:', btn.textContent.trim());
}
// Remove the banner from DOM
el.remove();
console.log('[CookieBlocker] Removed element:', sel);
});
});
}
// Run immediately and also observe for dynamically loaded banners
removeCookieBanners();
const observer = new MutationObserver(removeCookieBanners);
observer.observe(document.body, { childList: true, subtree: true });
})();
What a nuisance!
One of the most annoying "mandates" to ever come out of the EU.
Adopted in 2002, amended in 2009, enacted in 2011/2012.
Enough already! It's 14/15 **YEARS** later and we are still being PUNCHED IN THE FACE by these D@MN *nuisances*!
uBO's filters lists DO NOT block ALL of them !!!
I Still Don't Care About Cookies extension does NOT block ALL of them !!!
Everything I have tried in the past 14/15 years seems to do okay for the most part, but you still encounter these PIECES OF SH#T.
Enough already!
So it's time for a more generic approach and one FULLY controlled and editable by me, no more waiting for uBO filter lists not catching these to be updated but never updated to catch them ALL, no more waiting for extensions to be updated but never updated to catch them ALL.
Working so far!
// ==UserScript==
// @name - Auto Hide Cookie Banners
// @version 1.0.1
// @match *://*/*
// @grant none
// @run-at document-idle
// ==/UserScript==
(function () {
'use strict';
// Common CSS selectors for cookie banners and consent popups
const selectors = [
'[id*="cookie"]',
'[class*="cookie"]',
'[id*="consent"]',
'[class*="consent"]',
'[aria-label*="cookie"]',
'[aria-label*="consent"]',
'div[role="dialog"]'
];
// Try to click reject/decline buttons if found
const rejectButtonTexts = [
'reject', 'decline', 'no thanks', 'opt out', 'refuse'
];
function removeCookieBanners() {
selectors.forEach(sel => {
document.querySelectorAll(sel).forEach(el => {
// Try to find and click reject buttons inside the banner
const btn = Array.from(el.querySelectorAll('button, a'))
.find(b => rejectButtonTexts.some(txt =>
b.textContent.trim().toLowerCase().includes(txt)
));
if (btn) {
btn.click();
console.log('[CookieBlocker] Clicked reject button:', btn.textContent.trim());
}
// Remove the banner from DOM
el.remove();
console.log('[CookieBlocker] Removed element:', sel);
});
});
}
// Run immediately and also observe for dynamically loaded banners
removeCookieBanners();
const observer = new MutationObserver(removeCookieBanners);
observer.observe(document.body, { childList: true, subtree: true });
})();
- Duke
- Full Moderator
- Posts: 753
- Joined: 16 Mar 2024, 13:32
- OS: Windows 8.1 x64
- Has thanked: 113 times
- Been thanked: 227 times
Today's Pet Peeve
In Firefox and forks (R3dfox, LibreWolf, etc) you can set:
Automatically refuse cookie banners disabled:
cookiebanners.service.mode = 0
cookiebanners.service.mode.privateBrowsing = 0
Automatically refuse cookie banners set to reject all:
cookiebanners.service.mode = 1
cookiebanners.service.mode.privateBrowsing = 1
A value of 2 means reject all or fallback to accept all. This is stupid, don't use 2.
-
The-10-Pen
- Posts: 632
- Joined: 16 Feb 2025, 08:43
- OS: Win10 2016 LTSB
- Has thanked: 9 times
- Been thanked: 101 times

Today's Pet Peeve
Agreed.
But as you already know, that is not enough for me to revert to Firefox and forks.
I *do* still hope that day will arrive, but it's simply not here yet.
But as you already know, that is not enough for me to revert to Firefox and forks.
I *do* still hope that day will arrive, but it's simply not here yet.