-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Spam messages shouldn't be sent to clients #3649
Comments
I've tagged it as a feature even though it is not really (more a change from current expected behaviour) - agreed that blocking all makes most sense UX wise |
I'm a bit surprised this is still the case. The comment is still present at https://github.com/matrix-org/synapse/blob/0171fa5/synapse/events/spamcheck.py#L248 implying it is, though. |
Looking at the code starting here synapse/synapse/federation/federation_base.py Line 101 in 0326888
|
it is an implementation detail, somewhat surprisingly. Spec has this to say:
|
Pretty sure that the implementation in synapse does not pass on soft-failed events. The thing is, that's always been the case, so I wonder what has changed, if anything, between the time that comment was written and now. It's possible that we didn't soft-fail incoming spam events at the time? |
Well it looks like up until about 8 months ago Synapse just redacted the events and sent them on. The code to soft-fail the spammy events was added 8 months ago (by Rich, I might add 🙂 ). Either way the comment is definitely wrong and I can fix it, and I think that means we can close this issue as well? |
hurrah, sounds great! do you have a link to that change, out of interest? |
I think this is what you are asking for? https://github.com/matrix-org/synapse/pull/10263/files. |
yes it is, thank you! |
This is apparently desired behaviour according to the following, however that feels like a mistake. It should probably just not send it to users/appservices.
synapse/synapse/events/spamcheck.py
Lines 34 to 36 in f009df2
The text was updated successfully, but these errors were encountered: