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 article tags, 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 block article.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.
I had an issue blocking a certain community (on kbin) and was then able to block the domain. I did not really want to block the whole domain but since it was erring on the magazine and I found that one particularly annoying I finally blocked the domain.
Domain block supposedly doesn’t work that way. Or at least not properly. I don’t remember why - it might be that “domain” refers to the link and not the community, as on Reddit. Instance level blocking is supposed to be the “proper” fix here - when it arrives.
yeah honestly im not sure if domain blocking is working. I was blocking many non english ones because I lack linguistic skills and many times the magazine would still show. it sorta stopped but that is when the language option was added.
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?
deleted by creator
I had an issue blocking a certain community (on kbin) and was then able to block the domain. I did not really want to block the whole domain but since it was erring on the magazine and I found that one particularly annoying I finally blocked the domain.
Domain block supposedly doesn’t work that way. Or at least not properly. I don’t remember why - it might be that “domain” refers to the link and not the community, as on Reddit. Instance level blocking is supposed to be the “proper” fix here - when it arrives.
yeah honestly im not sure if domain blocking is working. I was blocking many non english ones because I lack linguistic skills and many times the magazine would still show. it sorta stopped but that is when the language option was added.