| 19 Aug 2025 |
 Gnuxie 💜🐝 | which is what would happen if it was a mandated part of homeserver impleemntations | 16:41:36 |
| Gnuxie 💜🐝 | it allows the "community management" implementation to be separate to the homeserver. Which is important because homeserver implementations are already very complicated and they would all be providing something that is subpar | 16:43:44 |
| Gnuxie 💜🐝 | it's also quite annoying when people think that "moderation" is just something trivial that can be hacked up and included by homeserver implementors in like two minutes | 16:45:43 |
 @aloisw:julia0815.de | It needs to actually do that. However it seems I misunderstood you and thought you were only talking about the user list but that was an earlier discussion. | 16:46:26 |
 emily | FWIW my assumption was that a homeserver-that-is-authoritative-for-a-room would delegate to a moderation bot implementation via a protocol of some kind (maybe even just reusing the existing Matrix one, letting the bot see state changes "early" and decide what to do about them before they get published) | 16:47:31 |
| emily | rather than implementing that stuff itself | 16:47:41 |
| emily | (well, sure. presumably homeserver implementations would all need to change to support this new room type with totally different ("no") state resolution logic, anyway) | 16:48:12 |
| @aloisw:julia0815.de | That was my assumption too, the "moderation interface" does not need to mean that the moderation policy needs to be implemented in the homeserver, but there should be some privileged interface providing a reasonable mechanism. | 16:49:14 |
| @aloisw:julia0815.de | Homeservers actually implementing it is pretty much a hard requirement for actually having a new room type in practice, yes. | 16:50:43 |
| 20 Aug 2025 |
|  @federicodschonborn:matrix.org changed their profile picture. | 01:06:53 |
 @emma:rory.gay | you can already achieve this with policy servers, minus the availability thing | 10:41:41 |
| @emma:rory.gay | this is the entire point of a policy server, but currently they dont scale very well as every server needs to ask the policy server whether an event is allowed (and this only result in soft failure) | 10:44:14 |
| emily | the availability is kinda the whole point | 10:44:28 |
| @emma:rory.gay | fwiw, there's work from Element's side to make policy servers be able to be authoritative in a future room version | 10:45:06 |
| @emma:rory.gay | so we can get rid of the "fail open" semantics they currently have (the current idea being that the origin server has to get a signature from the room's policy server to even commit the event to the DAG) | 10:46:16 |
|  jopejoe1 (4094@39c3) changed their display name from jopejoe1 (4094@GPN23) to jopejoe1. | 18:50:58 |
| 21 Aug 2025 |
|  dtpy joined the room. | 21:34:58 |
| 22 Aug 2025 |
|  elikoga changed their profile picture. | 17:27:58 |
| 23 Aug 2025 |
|  spectabilis joined the room. | 09:03:53 |
|  ➡️@amadaluzia:unredacted.org changed their profile picture. | 10:12:22 |
| 25 Aug 2025 |
| @federicodschonborn:matrix.org changed their display name from Cat McFishface 🏳️🌈 (he/they) to Mr. Bones (he/they). | 13:37:28 |
|  Jhmorenof joined the room. | 18:53:18 |
| 27 Aug 2025 |
|  Asai Neko changed their profile picture. | 07:27:54 |
| ➡️@amadaluzia:unredacted.org changed their profile picture. | 11:31:02 |
|  zolkenn joined the room. | 19:47:10 |
|  D. Ebling changed their display name from Denilson Ebling to D. Ebling. | 20:50:28 |
| 28 Aug 2025 |
|  @drupol:matrix.org left the room. | 08:14:41 |
|  Registry9108 joined the room. | 15:37:41 |
|  Charles changed their profile picture. | 17:59:24 |
| 29 Aug 2025 |
|  DontBlameMe changed their profile picture. | 10:01:15 |
