TODO:
- Needs description adding into the detail rather than the summary
- needs rich text
- needs markdown detail/summary to not just be the HTML tags, unacceptable since it's supposed to be fallback
- More commands
Still neeed to do alias commands. I think that requires a dedicated
alias and resolved room type and room reference is some kind of union type
that can resolve to a concrete room id.
`details` and `summary` being put into html in markdown is unacceptable
regardless of whether popular implementations support it.
Plain text client will not lol.
What's being asked for is detail/summary on category of commands.
That can only really happen once Synapse admin commands are all grouped
together into one table.
* Experimental Protection to propagate room level bans to policies.
- Needs an automated option
- I really want this to be enabled by default
- It needs to be easily configurable and very visible because it's a really useful feature.
- Need to check that they are not already banned on a policy list.
- Allow possibility to rely last message like a report behind spoiler text.
* Use MatrixDataManager for enabled protections.
This will allow us to create "enabled by default" protections
via a schema migration.
* Enable BanPropagationProtection by default
* BanPropagation: only prompt when user is not already banned.
* Test for BanPropagationProtection.
* clearTimeout for prompt reactions if we got a reaction.
* Allow renderMatrixAndSend to not need a reply.
* document getFirstEventMatching
This broke presentation renderers since `any` doesn't have a renderer
and it would match every presentation type. So anything that needed
rendering would try to be rendered as `any` which sucks.
Not sure what the semantics would be yet but we don't have to worry
for now.
The `.gitattributes` configuration requires everything that is detected as text to have `lf` line endings even when checked out.
The [`.editorconfig` configures capable text editors](https://editorconfig.org/#pre-installed) to
* use `lf` line endings
* remove trailing whitespace (with the exception of markdown files where it's valid way to end a paragraph?)
* insert a newline at end of file
* use the utf-8 charset
* use 4 spaces for indenting (instead of tabs)
while within this repository.
Signed-off-by: Aminda Suomalainen
Signed-off-by: Aminda Suomalainen <suomalainen+git@mikaela.info>
gnuxie