You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I constantly see posts from blocked profiles on my feed, and receive notifications when I'm tagged in a post by a profile I have blocked.
I'm also not able to reference posts of profiles that I have blocked. A blocked profile is able to tag me in their posts, and I'll see it everywhere I go, but I cannot respond to it in a comment or quote.
None of this makes sense, tbh.
The text was updated successfully, but these errors were encountered:
There is no notion of "tagging someone" at the protocol level, notifications are not present at protocol level neither.
What you are describing is a app/client level issue (or API issue in case it returns publications from blocked profiles when you query your feed).
Blocking at protocol level helps to signaling it in a global and shared way. It has consequences on-chain, like you cannot act, follow, comment, quote, etc., eachother. But then it requires apps to take the block status into account on app level features like you mentioned (notifications, tagging, recommended publications, etc).
There's really no proper place to report API issues, so I raised here. Issues in the API Examples repo are mostly ignored, it seems (I have one there from December without a response).
I'm a bit confused as to why am I unable to interact with publications from a profile that I block? I understand the other way, but wonder if two-way makes sense. For example, I believe I should be able to defend myself, in context, if someone I blocked is posting about me.
I constantly see posts from blocked profiles on my feed, and receive notifications when I'm tagged in a post by a profile I have blocked.
I'm also not able to reference posts of profiles that I have blocked. A blocked profile is able to tag me in their posts, and I'll see it everywhere I go, but I cannot respond to it in a comment or quote.
None of this makes sense, tbh.
The text was updated successfully, but these errors were encountered: