

I am sure it depends on what interface you’re using for the content. Like, what app or web UI, and even what are the settings for that UI. For example, I use Voyager on mobile, and there was one build where I blocked a person and could still see and reply to all of their comments. Obviously that was a bug, but it shows that blocking behavior depends on the UI.
At any rate, I double-checked. I used a private window and went to lemmy.ml to find a post there where the OP for that post had also commented, and when I went to that post through piefed’s interface, I was still able to see the post, but it had a message at the top about me blocking the instance, but I was not able to see the comment from the OP under their own post. (Edit: But I could see the other comments, even the one that the OP had responded to.)
So, I can say that, from what I can see, at least in that situation, piefed.social was blocking comments from a person who I didn’t specifically block as an individual, but was a member of an instance that I had blocked.


It was a lemmy.ml community. I could only see anything because I specifically looked up the user who posted it.
You can try it yourself. If you don’t like the way Lemmy acts, then try making an account on a Piefed instance and see how it’s different. I had heard Piefed was better, so I tried out an account, and decided I liked it better.
When you mentioned this behavior, I actually expected that Piefed would probably handle it in a way that I’d prefer.
And besides, the original Lemmy devs are the ones who run lemmy.ml.