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.

And it’s so annoying to hear the excuse “BEcaUsE tHe sWITCh iS aN UNDErpOWeRed SYsTEm” when the Switch’s launch title was Breath of the Wild.

Good to know that’s the default. I do definitely see prompts that have “Reject all”, plus some banners that only have “Accept all” and “Cookie settings”, with “Reject all” or “Necessary cookies only” only visible in the cookie settings. Thanks.

I tried out the 8B deepseek and found it pretty underwhelming - the responses were borderline unrelated to the prompts at times. The smallest I had any respectable output with was the 12B model - which I was able to run, at a somewhat usable speed even.

Fair, I didn’t realize that. My GPU is a 1060 6 GB so I won’t be running any significant LLMs on it. This PC is pretty old at this point.

I have 16 GB of RAM and recently tried running local LLM models. Turns out my RAM is a bigger limiting factor than my GPU.

And, yeah, docker’s always taking up 3-4 GB.

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

15 is the percent of the tip, not the percent increase in tip income over the last decade. If the tip percentage stays constant, then the tip amount rises in direct proportion to the food cost. The fair comparison is rent increase vs. restaurant food price increase. The data I found indicates rent’s gone up at an average of 4% per year in the last decade, and that restaurant food prices have risen by a similar amount - anywhere from 3-7% depending on the industry.

Everyone is struggling. It is not unique to servers. And I do tip - just a reasonable 15%. If a server is struggling to get by on 15% tips, they should harass their boss and their senator, not their customers who are likely struggling as well.

I’m punishing them by giving them what was until 10 years ago considered an excellent and standard tip?

Not to mention that servers are, as a general group, extremely opposed to dismantling the tip system as a whole. My complaint wasn’t about raised food prices, which the owner would be in control of - it was about raised tipping percentage expectations. I refuse to contribute to the steadily rising expectation of how much a tip should be, and regret my past contributions to that trend.

Back when 15% was considered standard I liked tipping closer to 30%, but as a direct result of the push to try to make 15% seem low I no longer tip more than 15%.

Not really, if something is inspiring rage then it’s too hardcore for this community. The sidebar even explicitly says “not enraging”!

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