This is a pretty bold piece of work and it's a shame to remove it for
now.
We would like to bring it back, possibly as a protection.
However, there isn't the time while we move over to the new MPS backend.
Much like the joins command, this needs rewriting to use
`SetMembership` from MPS and there isn't the time to do that
right now.
These commands didn't seem to work as intended anyway.
In reality this sets a default shortcode,
and for the moment we aren't able to work with shortcodes.
I don't know if it makes sense to bring this command back
in future because we would like to instead have
the ban propagation protection have a setting
for a list to fill client bans directly into.
This should be managed from the client, and the idea
that being a Synapse admin makes a difference is unfounded.
It wasn't even connected to the command handler anyway.
* Update D4A Documentation and add Config Example For Child Bots
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
* Move AS Inherited config into Docs instead of having example file.
* Integrate Review Feedback.
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
* Fix spelling mistake and a few its vs it´s style cases.
* Integrate Second Round of Review Feedback
* Update docs/appservice.md
yeah just wack it in Cat
Co-authored-by: Catalan Lover <48515417+FSG-Cat@users.noreply.github.com>
---------
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Gnuxie <50846879+Gnuxie@users.noreply.github.com>
This stores create database files all over the cwd that use nedb
which shouldn't really be used by the appservice library at this
point.
These files are problematic because they are undocumented to
server admins trying to setup the appservice, and need to be
explicitly accounted for to make permissions work.
The stores enable something called the `BridgeContext` to be
given alongside the event within the `onEvent` handler.
Which we don't use, and it's unclear how it should be used.
The primary motivation for removing the stores is to simplify
work making the appservice available to matrix-docker-ansible-deploy.
We expect to have follow up prs to improve documentation.
