wjs018 PieFedNot all instance blocks work
I did import blocks from my lemmy.world account, and the process did not carry over instance blocks. When I use the 'Block all posts from user's instance' it does show the instance on the block list, but only half or so of the blocks actually keeps posts from the instance from showing.
For example, I just don't have any interest in anything I have seen on ani.social. It is listed on my blocked instances, but posts from communities in that instance still show up and I have to block each community individually.
Since the only place I can find to block an instance is based on the user who posted, does than mean the instance block is blocking the users of the instance and not the communities on the instance?
If so, how can I block all the communities on an instance without needing to do each one as it comes through the feed?
Yes, I tried to read the piefed documentation and can't figure this out.
Thanks for letting us know about this. I've released v1.1.7 which fixes this issue.
Thank you!
Instance blocks should be working...at least I am not aware of them being broken. Here is how you can check:
If you want to kind of reset things, you could try removing the instance block and then re-adding it. Here is how you can go about doing that:
If you wanted to do this for ani.social for example, then you could go to the user page for the notorious @wjs018@ani.social and create the instance block from there.
If you are continuing to have problems with the blocks not working, feel free to let me know or make an issue on the Codeberg repo.
I've tried blocking ani.social multiple times by removing it and adding it back to the block list. The most recent was using the user you provided and that didn't seem to work either, although it looks like there might be a pattern where someone not on the instance posting to the instance is what is coming through as I don't see any posts from that instance by people on that instance.
Will look for some more consistency before posting to the repo. I also haven't seen anything from the ones I blocked in the last few hours to keep looking for more details.
For the ease of discussion, let's just continue using ani.social as the instance in question.
I see. So, is what you are seeing people from other instances creating posts in communities that are based on ani.social? Or, are you seeing people creating posts elsewhere that have an ani.social domain (like an image hosted on ani.social)?
If it is the second case, then you could add an ani.social domain block. That would filter out any posts that point to an ani.social domain.
If it is the first case, then that is a bug. The instance block should block posts/comments created by users from the blocked instance as well as any community based on that instance.
Not sure how to add an image, but the most recent one I see is user mental esge on sopuli.xyz posting to !militarymoe@ani.social
https://piefed.world/post/456002
Image is from a 3rd party used in communites I do want to see so I don't think blocking the domain would be a good idea.
Same user from a different instance with the other ones I'm seeing from a couple other instances, even when they don't have images. Don't see any where the user is a member of the instance when scrolling back a few hours, just users of other instances.
Alright, that sounds like a bug. I went ahead and made a codeberg issue for it. I haven't looked at the instance blocking portion of the code too much (other than doing some of the UI around it), but we will take a look.
Thank you!
Looks like rimu fixed the issue. The fix won't roll out generally until version 1.2 comes out in a week or two though. Thanks for reporting it!Edit: Nevermind, he backported the fix, so it should come out whenever piefed.world updates.
Have you tried domain block?
Domain block appears to block the domain the posts are linked to, like image hosts. It also wouldn't be consistent with the terminology.