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
If you communicate with someone, and they block you, your own posts are not visible in your own replies. The only time you can see your own post is if a third party in the thread likes it from their notifications as that shows up in your own notifications.
To Reproduce
1: Post a reply.
2: Other party blocks you.
3: Your posts disappear from your replies. (issue 1)
4: Third party in thread likes your post from their notifications after block and that shows up in your notifications. (issue 2)
Expected behavior
Issue 1: Your own posts should be visible in your replies
Issue 2: If replies to a user that blocks you are supposed to be visible in the thread, then this issue is gone. If not, nobody should be able to like from their notifications or even see your reply.
Screenshots
Details
Platform: Desktop Chrome, Android app
Platform version:1.59
App version: 1.59
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
If you communicate with someone, and they block you, your own posts are not visible in your own replies. The only time you can see your own post is if a third party in the thread likes it from their notifications as that shows up in your own notifications.
To Reproduce
1: Post a reply.
2: Other party blocks you.
3: Your posts disappear from your replies. (issue 1)
4: Third party in thread likes your post from their notifications after block and that shows up in your notifications. (issue 2)
Expected behavior
Issue 1: Your own posts should be visible in your replies
Issue 2: If replies to a user that blocks you are supposed to be visible in the thread, then this issue is gone. If not, nobody should be able to like from their notifications or even see your reply.
Screenshots
Details
Additional context
The text was updated successfully, but these errors were encountered: