|
|
|
@ -400,25 +400,3 @@ in their content to provide a way for Matrix clients to link into the 'native'
|
|
|
|
|
client from which the event originated. For instance, this could contain the
|
|
|
|
|
message-ID for emails/nntp posts, or a link to a blog comment when gatewaying
|
|
|
|
|
blog comment traffic in & out of matrix
|
|
|
|
|
|
|
|
|
|
Active Application Services
|
|
|
|
|
----------------------------
|
|
|
|
|
.. NOTE::
|
|
|
|
|
This section is a work in progress.
|
|
|
|
|
|
|
|
|
|
.. TODO-spec
|
|
|
|
|
API that provides hooks into the server so that you can intercept and
|
|
|
|
|
manipulate events, and/or insert virtual users & rooms into the server.
|
|
|
|
|
|
|
|
|
|
Policy Servers
|
|
|
|
|
==============
|
|
|
|
|
.. NOTE::
|
|
|
|
|
This section is a work in progress.
|
|
|
|
|
|
|
|
|
|
.. TODO-spec
|
|
|
|
|
We should mention them in the Architecture section at least: how they fit
|
|
|
|
|
into the picture.
|
|
|
|
|
|
|
|
|
|
Enforcing policies
|
|
|
|
|
------------------
|
|
|
|
|
|
|
|
|
|