We need to do this because they will be impossible to obtain once the
room has been blocked on the server.
We also need to make sure we now include the server the room was
created on, and the creator in the room hash store.
I want to change the APIs a little bit so that we can get a takedown
reporter like the audit log but for message rendering and testing.
I also want to make the BetterSqliteStore concrete not depend
on where the database came from so that we can use in memory
databases for unit testing stores.
There are a couple other FIXME's littered around so be sure to check
those before merging.
Make appservice datapath example consistent with docker image.
Make the appservice config schema check the admin room properly.
We now parse the room id/alias/or permalink.
Make sure to parse the config from cli.ts
* Set up state store if configured in d4all mode
Signed-off-by: MTRNord <mtrnord1@gmail.com>
* Ensure the dataPath is set in both the example and harness appservice config
Signed-off-by: MTRNord <mtrnord1@gmail.com>
* Move the SqliteRoomStateBackingStore creation to a static method instead
Signed-off-by: MTRNord <mtrnord1@gmail.com>
* Make the storage path canonicalization less confusing
---------
Signed-off-by: MTRNord <mtrnord1@gmail.com>
Explicitly set the `temp_store` pragma to `file` instead of `memory`
after deciding to place temporary files in `/data` to keep RAM usage
down while addressing #746.
Added a helper function to automatically "flatten" transactions
when you don't need SAVEPOINTs to avoid unnecessary temporary files.
Signed-off-by: Bea <20361868+enbea@users.noreply.github.com>
We no longer want to accept an argument for the list. We will just
find all appropriate policies and remove them, like we do with the
unban prompt (which we still might want to update to use the new
`--no-confirm` prompt later).
We fix the bugs where the unban command was inviting users regardless
of whether the `--invite` option was provided.
The unban command now uses a preview which shows all the policies that
will have to be removed to unban a user, all the rooms they will need
to be unbanned from, and any rooms that they will be invited to if the
`--invite` option is used.
* Set renderers and glue for new simulated capabilities.
https://github.com/the-draupnir-project/planning/issues/2.
* Distinguish simulated capability messages when rendering.
* Update for MPS 2.10.0
* Add `!protections capability reset <protection name>` command.
This will allow you to use the default capabilities for a protection.
* Update CHANGELOG for simulated capabilities.
This shows all the rules that are matching members in the protected
rooms set, but probably cannot be actioned either due to permission
limitations or ACL leakage.
This simplifies anything to do with the way policy rooms are watched.
There was a lot of weird glue code around finding policy rooms and
revisions that has just been whipped out into the WatchedPolicyRooms
abstraction.
gnuxie