Block sender

[jcabannes]

Related to https://ci.linagora.com/publicgroup/oss/twake/tom-server/-/issues/9

[jcabannes]

@guimard I have several questions about this ticket. I think just most of them concern advanced features for this ticket but to keep a trace I think it is good thing to write them here:

1 - Should we implement an unblock endpoint?
2 - Should we block the sender only in one room or in all room he is member of?
3 - Should we prevent him to join public rooms?
4 - Should we prevent him to send direct message to other users?
5 - Should we prevent him to create new rooms?
6 - Should we prevent him to invite users in rooms?
7 - Should he still appear in search results when we are searching for a user or a message?

[guimard]

@guimard I have several questions about this ticket. I think just most of them concern advanced features for this ticket but to keep a trace I think it is good thing to write them here:

1 - Should we implement an unblock endpoint?
Hi,

we need a way to manipulate the list. Maybe a table in Pg, maybe an API

2 - Should we block the sender only in one room or in all room he is member of?

All

3 - Should we prevent him to join public rooms?

Yes, it's a global ban (it's for external Matrix address. For internal, just to remove account and ban IP

4 - Should we prevent him to send direct message to other users?

Yes, global ban

5 - Should we prevent him to create new rooms?

Yes

6 - Should we prevent him to invite users in rooms?

Yes

7 - Should he still appear in search results when we are searching for a user or a message?

Not related to the issue: it's for external Matrix addresses

[pm-McFly]

This is a client side concern: https://spec.matrix.org/v1.17/client-server-api/#ignoring-users
Already implemented in twake-on-matrix:

• TW-2496: Implement unblock user and block users in settings twake-on-matrix#2497
• TW-2491: Implement block and unblock user functionality twake-on-matrix#2492