Stacker Saloon \ stacker news

pull down to refresh

Howdy there, partner! Welcome on into the Stacker Saloon.

Saddle on up to a stool and spill the beans about your day, fire away with them questions, or let loose and give us the lowdown on your wild and woolly life. We're all ears, so don't hold back!

We're open round the clock, so mosey on in whenever you please!

1 sat \ 0 replies \ @SHA256man 8m

#1266468

101 sats \ 1 reply \ @sox 1h

I think that the problem with WYSIWYG is that it's always going to be such a chore to do power stuff that we can do in Markdown.

But then Markdown is not WYSIWYG so it might feel more "difficult" to use.
But then WYSIWYG is frustrating to the not-power user, because yes what they'll see is what they'll get but what they'll see might not be what they want.

Where's WYWASIWYG _{what you want and see is what you get}?

101 sats \ 0 replies \ @optimism 1h

Where's WYWASIWYG _{what you want and see is what you get}?

Elon has it: Hey @Grok undress.

201 sats \ 0 replies \ @carlosfandango 1h

Man stopped me in the street this morning and asked why I was carrying an eight foot book?

I said: ‘It's a long story’…

242 sats \ 13 replies \ @CindyKate 1h

Yesterday we first-hand witnessed that resisting censorship on SN is much like resisting censorship in Russia: it paints an enormous target on one's back. Our own syndication post was the top downzapped post. If we'd be resisting a nation state though, our disobedience would have landed us in the gulag awaiting poisoning with polonium, Novichok and/or epibatidine, but luckily we are finding ourselves in a relative benign position where we just have to resist little authoritarians with barely any real power, not big ones.

Additionally, because we despise "devs do something" and we strongly believe that the power of SN is the community, not the money, we act from a baseline conviction that the community can just do things. And we intend to just do things. Of course, we've foreseen a counter reaction and already have developed a series of mitigations to potential attempts to disrupt our resistance.

The first trick from our resistance handbook is a simple one: we will only post reports of downzapped posts, so if you're interested to learn about content that you may have missed, of any nature, you can subscribe to our posts, as subscriptions always deliver. If you don't want to see our posts because you dislike things that were downzapped, you can simply mute us. To do either, go to our profile, tap the ... next to our nym and use the "subscribe to posts" or "mute CindyKate" option as you desire.

Enjoy your day.

70 sats \ 0 replies \ @ek 44m

Thank you for your service

120 sats \ 8 replies \ @optimism 1h

@ek's absomute script is also interesting: #1438661

170 sats \ 7 replies \ @ek 36m

Are you running it? Maybe I should make a post about it and upload it as a GitHub Gist for easy installation

It doesn't solve the downzap problem though

I also need to figure out how to run this on iOS, if there's a way at all

70 sats \ 0 replies \ @optimism 27m

Yes and it works. I needed to get rid of the urge to click these.

101 sats \ 5 replies \ @CindyKate 34m

I have it slated for testing but I won't run it in production because I don't run extensions outside of the built-in brave "shields" thing. Still it's something I would like to have.

170 sats \ 4 replies \ @ek 18m

I just learned that Shield allows you to run custom scriplets!

So if you save this as a custom scriptlet at brave://settings/shields/filters:

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

    // Run on initial page load
    removeCollapsedComments();

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

and then save this custom filter: