I’m a little out of the loop on how reddit’s been. Is blocking links to X officially no longer allowed there?

Is there confirmation that he actually specifically wanted that image off reddit? Or is this just someone making assumptions after the recent story about him interfering with moderation at reddit?

old.lemmy.world##div.post:has(div.rank):has-text(/Trump|Elon|Musk|nazi|maga/i)

Here’s a comparison of part of my homepage with (left) and without (right) the filter active

I’m in firefox + uBlock on lemmy.world too, and it works fine for me - I can see on my current front page 2 posts are being blocked and the rest are showing up. Do you have any other uBlock filters going on? Are you on some page other than the lemmy.world homepage? Are you using the default UI or one of the alternate UIs?

What an insightful post 🙂

The only one of these I’ve updated since the original is the one for Ars Technica, which is now this:

arstechnica.com##:not(:not(head>title:has-text(/Serving the Technologist/))) article:has-text(/Trump|Elon|Musk|nazi|doge|maga/i)

The reason being that ‘Ars Technica’ now appears in the title of articles, while it didn’t originally, which caused the original filter to block out entire articles. ‘Serving the Technologist’ only appears on the homepage so this updated filter will still filter the homepage but display the contents of articles that contain blacklisted words.

Or averages, it seems to be absolute counts each day

Hash tables are often used behind the scenes. dicts and sets in python both utilize hash tables internally, for example.

Firefox now includes safeguards to prevent sites from abusing the history API by generating excessive history entries, which can make navigating with the back and forward buttons difficult by cluttering the history. This intervention ensures that such entries, unless interacted with by the user, are skipped when using the back and forward buttons.

Nice

Hello again 🙂 I have a good feeling about this one.

infosec.pub##:not(head>title:has-text(/leopard/i)) article.row:has-text(/Trump|Elon|Musk|nazi/i):not(:has-text(/leopard/i))

It’s doing basically the same thing as the last one but now instead of targeting an <a> tag with the community-link attribute, which was basically just the first way I was able to find of identifying a community last time, it targets the title of the page itself, which seems like it should be a lot more reliable. This does mean using the literal leopardsatemyface-type filter won’t work since the title of the page is the community’s user-friendly name: “Leopards Ate My Face” in this case.

So as before it should block any posts which contain words from the blacklist, unless they also contain words from the whitelist - and now if the title of the page has any words from the whitelist (indicating we’re on an allowed community page), it will block nothing at all. The blacklist and whitelist will apply to the post title, community name, and even the submitter’s name - anything you can read and even some things you can’t read.

I think I may see why. I didn’t actually bother to check the main feed before, but it seems like it does have the a.community-link tag the new filter targets in every post - so if a post from leopardsatemyface ever shows up in the main feed, then the filter will think it’s on that community page and fail to block any posts. But the filter should work fine so long as no posts from that community are currently on the main feed. This should be the case regardless of which regex is used - if it wasn’t just a coincidence earlier I’ll have to test around to figure out what happened with that.

It’s a process making a good filter, I guess - I may look into a more reliable and narrower way to achieve the desired effect later on

What happened with .*?leopard.*?? It was still filtering Trump posts even from the community page? My own testing showed that variant working - I never actually even tested the leopardsatemyface variant

To be clear, this filter should allow for Trump posts that mention leopards or come from that community to show up on your main feed - that’s what’s desired here, right?

It also occurs to me that the ? on the .*? isn’t necessary - even just .*leopard.* should work as expected

Hey! I’m pretty sure this one will work:

infosec.pub##:not(a.community-link:matches-attr(title=/.*?leopard.*?/i)) article.row:has-text(/Trump|Elon|Musk|nazi/i):not(:has-text(/leopard/i))

Where now we have three filters. If the community name matches the first regex, then nothing at all will be filtered out - and then the other two work the same as before. So any post that matches the blacklist regex will be filtered out unless it also matches the whitelist regex.

I chose to make the first regex /.*?leopard.*?/i because my thinking is you may want to just copy/paste the other whitelist filter there for simplicity, but it might make more sense to do it like the others, like /leopardsatemyface|second community|third community|etc/i. The “title” of a community for the purpose of this filter should be whatever appears after /c/ in the URL, not counting the @lemmy.world (or whatever instance) part.

Actually it seems to be a difference based on our instances - if I look at the community from infosec.pub then the bit of HTML I quoted above with the mod option isn’t present, and there’s no ‘leopard’, hidden or explicit, for the whitelist filter to find.

As a note, the (s)? on your leopard isn’t needed - just ‘leopard’ will already match the ‘leopard’ part of ‘leopards’

I don’t know how to fix this currently, but I’ll test out a bit more later to see if I can find anything that works well

I’m not sure I follow - the filter seems to work as-is to me. It allows posts on both the front page and the !leopardsatemyface@lemmy.world to bypass the filter for me.

To be clear, it’s not only applying to the title row - the article tag it targets contains the entire post as it appears in the post feed, including the title, community name, the person who submitted it, the timestamp, etc. So if anything there contains a filtered or whitelisted word it should trigger the filter.

I wouldn’t have necessarily expected the whitelist filter to work directly on the leopards community page, since posts on community feeds don’t include the community name, but it works anyways because, it seems, there’s a hidden mod option in the HTML with the community name in it: <div class="modal-body text-center align-middle text-body">Are you sure you want to transfer leopardsatemyface@lemmy.world to TheBat@lemmy.world?</div>

lemmy.world##article.row:has-text(/word1|word2|word3/i):not(:has-text(/word4|word5|word6/i))

or

lemmy.world##article.row:has-text(/maga/i):not(:has-text(/leopard/i))

will do what you want - it’ll block any posts which contain words from the first regex, unless it also has some words from the second regex

At one point I had the very similar filter lemmy.world##.post-listing:has-text(/trump/i), but I wasn’t happy with it because it would also remove post content on actual post pages, not just the post feed. That was the whole reason I swapped to the article.row solution instead - posts in the feed have the row class while posts on their own page don’t. But it looks like you found an alternate solution to achieve essentially the same thing. Neat!

I have no real interest in filtering out comments, but it’s nice to have that option there for people who do.

Where? I see the option to block users, instances, and communities, but not words.

And regardless, I think this method has value because it can be applied to pretty much any website with a bit of tinkering, and it can be turned on and off with a couple of clicks. I actually started out with the ars filter before making one for Lemmy.

Hey thanks. I just made $2.86! And my mom is owed $1.44!

A “live-man’s switch” might be a better idea. If you’re in such a high profile situation and you’re scared enough that you think you need a dead man’s switch, make frequent unprompted public declarations that you’re healthy and not suicidal, and that should anything happen to you, you blame the company.