| 27 Apr 2025 |
nhnn | i'm on conduwuit :( | 16:53:36 |
K900 | !admin delete-remote-media in the admin room should do it | 16:53:45 |
@emma:rory.gay | if you have no other users... use this instead | 16:53:49 |
liv <3 | Redacted or Malformed Event | 16:53:50 |
liv <3 | oh... | 16:53:55 |
liv <3 | Should I remove the /var/lib/matrix-synapse/media_store/remote_thumbnail folder? | 16:54:12 |
nhnn | I know, but not seeing invites at all would be better :) | 16:54:13 |
nhnn | No, you should remove remote media via API | 16:54:24 |
@emma:rory.gay | NO | 16:54:24 |
K900 | Oh sorry wrong person | 16:54:27 |
@emma:rory.gay | MADS was written specifically for single-user usecases, especially on those not running their own homeserver, and using ie. matrix.org instead | 16:54:42 |
liv <3 | ah okay, will look into that | 16:55:27 |
@emma:rory.gay | it even logs the invites in a room for you incase one happens to have gotten yeeted by mistake | 16:55:28 |
@emma:rory.gay | MADS uses the same banlists as moderation bots do :) | 16:55:59 |
| @palasso:matrix.org left the room. | 16:56:15 |
@emma:rory.gay | so you can have it automatically reject invites as soon as they get banned from these rooms | 16:56:19 |
liv <3 | wait so using MADS is "better" than using synapse-http-antispam when you're on a single-user-instance? | 16:57:31 |
liv <3 | or at least does the same thing? | 16:57:37 |
| Winter joined the room. | 16:57:40 |
@emma:rory.gay | depends on what the integrations do with the antispam modules | 16:58:00 |
@emma:rory.gay | * depends on what the integrations do with the antispam module | 16:58:10 |
@emma:rory.gay | but the entire point of MADS is to work regardless of homeserver implementation, and regardless of admin access to the server | 16:58:40 |
@emma:rory.gay | aka theres not a single reason it wouldnt work on matrix.org, even | 16:59:04 |
@jh-devv:matrix.org | In reply to @emma:rory.gay but the entire point of MADS is to work regardless of homeserver implementation, and regardless of admin access to the server HOW? | 16:59:13 |
@emma:rory.gay | its single user | 16:59:28 |
@emma:rory.gay | it just uses the regular client/server API, the same one your client uses ;) | 16:59:42 |
nhnn | it acts like a matrix client | 16:59:45 |
@emma:rory.gay | yep, it essentially is just a tiny client minus all the client parts | 17:00:14 |
@emma:rory.gay | just like every other non-appservice matrix bot | 17:00:25 |
@emma:rory.gay | all it does is listen for invites, and listen for banlist events, correlates the 2 and rejects invites based on that | 17:00:51 |