pull down to refresh

mutenuke: never see 'reply from someone you muted' again github.com/ekzyis/mutenuke

A few days ago, I created a userscript to never see 'reply from someone you muted' again.

Due to the popular demand here of three other stackers, I decided it's worth making it easier to install and writing a post about it.

I still have to figure out if there's a way to run this in the PWA, too.

mutenukemutenuke

Never see 'reply from someone you muted' on Stacker News again.

Installation via userscript extensionInstallation via userscript extension

Install a userscript extension like Tampermonkey
Go to the mutenuke page on GreasyFork
Click "Install this script"

Installation via Brave ShieldsInstallation via Brave Shields

On Brave, you don't need a userscript extension. You can run custom scriptlets within Shields as mentioned here!

Go to brave://settings/shields/filters
Enable developer mode
Save this as a new custom scriptlet named 'mutenuke':

window.addEventListener('DOMContentLoaded', () => {
    function mutenuke() {
        document.querySelectorAll('div[class*="comment_collapsed"]')
            .forEach(node => {
                if (node.textContent.startsWith("reply from someone you muted")) node.remove()
            }
        )
    }

    // Run on initial page load
    mutenuke();

    // Watch for dynamically loaded content
    const observer = new MutationObserver(mutenuke);
    observer.observe(document.body, { childList: true, subtree: true });
})

Save this as a new custom filter:

stacker.news##+js(user-mutenuke.js)

Done!

_{Installation via Brave Shields will cause}_{React hydration errors}_{, but as far as I know, it doesn't impact the functionality of the site.}

view all related items

597 sats \ 9 replies \ @optimism 7h

Fixes courtesy of:

runAfterHydration: GPT, Claude, Gemini and GLM (all said the same, lol)
node.style = "visibility: hidden" instead of node.remove(): Opti, because the removal gave me errors on comment.

window.addEventListener('load', () => {
  function runAfterHydration(callback) {
    requestAnimationFrame(() => {
      requestAnimationFrame(callback);
    });
  }

  runAfterHydration(() => {
    function removeCollapsedComments() {
      document
        .querySelectorAll('div[class*="comment_collapsed"]')
        .forEach(node => {
          if (node.textContent.startsWith("reply from someone you muted")) {
            node.style = "visibility: hidden";
          }
        });
    }

    removeCollapsedComments();

    const observer = new MutationObserver(removeCollapsedComments);
    observer.observe(document.body, { childList: true, subtree: true });
  });
});

112 sats \ 8 replies \ @ek OP 7h

Ohh, nice fix! Also nice edit within the 10-minute timer, haha

112 sats \ 7 replies \ @optimism 7h

It was the ultimate pressure cooking exercise in javascript debugging because I wrote "verified works" and then I hit post and it died 😂

101 sats \ 6 replies \ @ek OP 6h

Mhh, node.style = "visibility: hidden" leaves empty space behind.

But node.style = "display: none" should work! The node is still there for React without taking up any space in the DOM.

101 sats \ 5 replies \ @optimism 6h

confirmed. This why you don't let old people code for the browser 😂

101 sats \ 4 replies \ @ek OP 6h

With node.style = "display: none", you can also keep running it after the slightly faster DOMContentLoaded event and don't need requestAnimationFrame. The load event will also wait until images are loaded.

Thank you!!

101 sats \ 3 replies \ @optimism 6h

Wait! Are you saying that my noob code reimplemented by you, and not the trillion dollar training of the 4 most expensive databases that have ever existed, fixed the bug?

Take that, silicon brains. lol

101 sats \ 2 replies \ @ek OP 6h

You probably told it to run after hydration, and that’s what it did, haha

But when we don’t remove the node, we don’t interfere with hydration, so we don’t need to run it after hydration.

Edit: But sounded like it was still broken after the first prompt, so you prompted it again, and that contained the actual, inspiring fix via CSS haha

view all 2 replies

667 sats \ 2 replies \ @Solomonsatoshi 8h

Op @ek why don't you attach and show attached LN wallets?
Clearly you are capable but maybe you dont believe in verifying you are on board with and maximising your use of and support of LN here on SNs?
Genuinely mystified why you would not attach or deliberately conceal your LN wallet attached status.

151 sats \ 1 reply \ @ek OP 7h

I don't need to virtue-signal about lightning, my work speaks for itself

668 sats \ 0 replies \ @Solomonsatoshi 7h

You do not believe content consumers here who ultimately must fund the entire platform if it is to be viable have a right to know which content providers have made the effort to attach LN wallets and thereby maximise their use of and support for the LN?

There are a number content providers who write a lot about LN development and potential who 'virtue signalling' that they are 'living on the Bitcoin Standard' but who have never bothered to attach both sending and receiving LN wallets. I see that as hypocrisy and do not want to spend my sats on them.

Showing attached wallets verifies to content consumers that a content provider is NOT just virtue signalling but is walking the talk.

44 sats \ 9 replies \ @Fenix 5h

Does your script hide the comments from muted users that stay collapsed until you click on them? It could be a toggle in the SN settings, and the name is really good.

144 sats \ 3 replies \ @optimism 4h

It removes the entire thread underneath your mute too, so you won't be bothered by it.

The only flaw is that if you're subscribed to a post, then you will see replies from others to it in your notifications, but not under the post itself.

101 sats \ 1 reply \ @Fenix 4h

this is enough for me but completely understandable when you hae a lot of muted nym to pollute a good post.

Where in SN settings @k00b?

162 sats \ 0 replies \ @k00b 4h

the problem with making this a feature, as is, is that the comment counts won't represent the removed comments and cause confusion. why that is is kind of technical, but i could probably come up with a solution to it

70 sats \ 0 replies \ @ek OP 4h

And when you click on them, you also won't get scrolled to them

201 sats \ 3 replies \ @ek OP 4h

Does your script hide the comments from muted users that stay collapsed until you click on them?

Yes!

It could be a toggle in the SN settings

This has been suggested before, but iirc it's hard to get all the details right. I don't remember the details, though.

This script can be simple, because, as something not officially part of SN, it doesn't have to meet the same quality standards.

For example, with this script, if you happen to click on a link to a reply to someone you've muted, you won't be scrolled to the reply, because the script removes the muted thread (as mentioned by @optimism in #1439671). The "official code" would have uncollapsed the muted thread.

I hope stackers don't run this and then report bugs caused by it to @k00b or @sox 😅

101 sats \ 0 replies \ @Fenix 4h

I saw that it's really easy to use without having to bother the SN devs; however, for me, since I use the PWA version most of the time and don't use Brave, it's still out of reach. It's good to know there are good coders like you to count on when I want to suggest something that's not feasible to implement across the entire platform.