Problems With Blocking

A lot of this is Pleroma backend issues, but I want to track the on-going problems we are having with blocking and the proposed intended behavior:

1. Users should not be able to see posts from others who have them blocked ❌

Preventing another user from seeing or interacting on your posts is the most basic feature of blocking, however, it is missing from Pleroma.

A user I have blocked should not be able to:

  • Follow me ✔
  • See my posts in public timelines ❌
  • See my posts in their home timeline when boosted by someone they follow ❌
  • See my posts or media on my profile ❌
  • Interact with my posts, including replying or reacting ❌

I think the way that Twitter handles viewing a profile you are blocked from is good:

Screenshot_from_2020-08-28_12.46.49

2. Notifications from blocked users should not go into counter ❌

Currently, ['notifications', 'pleroma', 'unread_count'] counts notifications from blocked users. Ideally, a blocked user should not be able to even create a notification for you. But, since they currently can, those notifications should not be counted in any relevant counters.

This is especially bad because users have no way to clear these notifications since they can not see them. So, no matter how many times you refresh the page, notifications from blocked users keep coming back to haunt your notification counter.

3. User should not see content from accounts they have blocked ✔

This is the only aspect of blocking that is currently working as expected. Users can not see posts from accounts they have blocked (works similar to a mute). This should stay the same.

Edited by Mary Kate