Skip to content

Commit 1b195e5

Browse files
authored
Update CHANGELOG for current changes. (#784)
* Update CHANGELOG for current changes.
1 parent 64de514 commit 1b195e5

1 file changed

Lines changed: 75 additions & 0 deletions

File tree

CHANGELOG.md

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,81 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
1212
and this project adheres to
1313
[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
1414

15+
## [Unreleased]
16+
17+
### Added
18+
19+
- New server administrative features have been added to Draupnir. For an
20+
overview see
21+
[homeserver administration](https://the-draupnir-project.github.io/draupnir-documentation/bot/homeserver-administration)
22+
in our documentation.
23+
24+
- A new
25+
[_Room Takedown Protection_](https://the-draupnir-project.github.io/draupnir-documentation/protections/room-takedown-protection)
26+
has been added to assist homeserver administrators in managing the rooms their
27+
server is joined to. This includes a room discovery utility where Draupnir
28+
will notify the management room with details of rooms it has discovered on the
29+
homeserver (configurable with a threshold for joined members). The intent of
30+
this protection is to keep rooms with intolerable or illegal content off of
31+
the homeserver, including invitations to these rooms. Room takedown is backed
32+
up by policy list support. Added by @Gnuxie and @enbea.
33+
34+
- A new
35+
[_Block invitations on server protection_](https://the-draupnir-project.github.io/draupnir-documentation/protections/block-invitations-on-server-protection)
36+
to assist homeserver administrators in preemptively blocking invitations from
37+
users or rooms listed in Draupnir's watched policy rooms. This replaces the
38+
functionality in the legacy Mjolnir antispam module and is compatible with
39+
Synapse workers.
40+
41+
- A new `takedown` command has been added as an alternative to the ban command.
42+
`takedown` marks users, rooms, or servers with a policy that means any content
43+
associated with the entity should be removed and takendown. This is a much
44+
stronger consequence than `ban` and is reserved for illegal or intolerable
45+
content. See
46+
[MSC4204](https://github.com/matrix-org/matrix-spec-proposals/pull/4204) for
47+
details. This command works in conjunction with the new
48+
[_Room Takedown Protection_](https://the-draupnir-project.github.io/draupnir-documentation/protections/room-takedown-protection)
49+
50+
- Support has been added for
51+
[MSC4205: Hashed moderation policy entities](https://github.com/matrix-org/matrix-spec-proposals/pull/4205).
52+
Currently we only support revealing hashed entities for rooms. Except from in
53+
the
54+
[_Block invitations on server protection_](https://the-draupnir-project.github.io/draupnir-documentation/protections/block-invitations-on-server-protection).
55+
The `takedown` command will hash entities by default. These policies require
56+
your Draupnir (or homeserver) to have encountered a user, room, or server
57+
before it can reveal the moderation policy. This stops policy rooms from
58+
becoming an address book for abuse.
59+
60+
- Support for [synapse-http-antispam](https://github.com/maunium/synapse-http-)
61+
antispam has been added to Draupnir and protections. Thanks to @tulir.
62+
63+
- Room state backing store can now be used in the appservice deployment mode.
64+
Contributed by @MTRNord in
65+
[#753](https://github.com/the-draupnir-project/Draupnir/pull/753).
66+
67+
- An experimental protection to stop excess membership changes. This protection
68+
will send a warning before kicking users that are changing their membership
69+
event frequently. All of which can be configured.
70+
71+
- A schema has been added to the appservice config file to prevent simple
72+
mistakes.
73+
74+
### Fixed
75+
76+
- An issue with the `RoomStateBackingStore` for users on docker with read-only
77+
containers where SQLite temporary files couldn't be created. Reported by
78+
@cdesnoai and @TheArcaneBrony in
79+
[#746](https://github.com/the-draupnir-project/Draupnir/issues/746). Fixed by
80+
@enbea.
81+
82+
- An issue where errors from appservice startup would not propagate to the top
83+
level.
84+
85+
- Old config properties have been removed from default.yaml thanks to
86+
@ll-SKY-ll.
87+
88+
- Typo in BasicFloodingProtection thanks to @Mikaela.
89+
1590
## [v2.2.0] - 2025-03-03
1691

1792
### Changed

0 commit comments

Comments
 (0)