this post was submitted on 14 Nov 2023
34 points (78.3% liked)
New to Lemmy
292 readers
1 users here now
Did you just join Lemmy? This community is for you!
Do you want to help new users around? Then this community is for also you!
Thank you all for being here, it makes a big difference
FAQ
- You don't have to post here, but it's fun!
- You don't have to post right away, come back later if you want
- You can post as many times as you want
I don't know what to post
- Share what you're looking for, or what you want to do. We'll help you find it
- Ask questions! The Fediverse is new to most people. If you're unsure about something, others are unsure as well.
- Just smile and wave, maybe someone will wave back ๐
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Until proper support arrives (Lemmy 0.19 and... whenever it's meant to appear on kbin, which currently even errors trying to block a certain hexbear community), I just made a few filters. Unfortunately they are on my other machine. Fortunately they are plain old uBlock Origin selectors, and not that hard to make. The rough points:
On kbin, posts on the front page, magazine (community) pages etc are
articletags, containing links to the user and community. That link will always end with /u/@someone@someplace or /m/somewhere@someplace. As a result you can do stuff like blockarticle.entry:has(a.user-inline[href$="@hexbear.net"])(posts by all hexbear denizens)article.entry:has(a.magazine-inline[href$="@hexbear.net"])(posts by anyone to hexbear communities) - this is untested off the top of my dome, syntax might be broken.I don't know how it works in Lemmy, presumably not that differently.
Doesn't work sadly. Anyone smarter than me can fix this?