meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
digital:server:matrixsynapsemisc [2018/12/06 10:57] natrius |
digital:server:matrixsynapsemisc [2022/05/18 13:08] (current) natrius [Tombstone Event] |
||
---|---|---|---|
Line 3: | Line 3: | ||
Different things, sometimes advanced and some things that just did not fit in the regular guide. | Different things, sometimes advanced and some things that just did not fit in the regular guide. | ||
- | ## .well-known section | + | ## Matrix tips they don't tell you |
- | Mathijs | + | https://wordsmith.social/cos/matrix-tips-they-dont-tell-you |
- | it's a little early, but you could also add a section about .well-known | + | |
- | which just means you have nginx serve a json file on example.com/.well-known/matrix/client | + | |
- | I did it for apache, but it's probably fairly easy for nginx as well | + | |
- | Mathijs | + | ## Interesting projects |
- | https:// | + | |
- | if you like reading spec :) | + | Moved to [[digital: |
+ | |||
+ | ## Synpase maintenance tools | ||
+ | |||
+ | * https:// | ||
+ | |||
+ | ## Show the public rooms on the server | ||
+ | |||
+ | * '' | ||
## Coturn | ## Coturn | ||
Line 23: | Line 28: | ||
opening ports | opening ports | ||
+ | ## Installing Bots | ||
- | ## Add an SRV Record | + | Matrix Synapse currently does not have a concept of bots, a bot is just a normal user. Usally there is a config and a '' |
- | To use the domain '' | + | Install python3 |
- | After the A record is set up, create a SRV Record that looks like | + | < |
- | < | + | then install pip |
- | So, for example use | + | < |
- | < | + | then matrix-bot-api from pyp |
- | and when creating the Synapse server use '' | + | < |
- | Stefan | + | and finally fill out the config and start it |
- | So, when I'm using the domain matrix.example.com and want to use exmpale.com for the registration and so on, i should use SRV. | + | < |
- | If i'm using example.com and making the redirect with nginx, there is no need for a SRV record? | + | |
- | kythyria | + | ## Exclude a server from a channel |
- | The SRV record is how other servers | + | Info von https:// |
- | Mathijs | + | - Chat `/devtools` |
- | the relevant url is where the federated servers can connect to you | + | - `Send Custom Event` |
+ | - Rechts unten roten Button `Event` drücken | ||
+ | - Event Type: `m.room.server_acl` | ||
+ | - State Key: leer lassen | ||
+ | - Event Content: | ||
- | kythyria | + | ``` |
+ | { | ||
+ | " | ||
+ | " | ||
+ | ], | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | ] | ||
+ | } | ||
+ | ``` | ||
- | It's so your server_name (what' | + | - `Send` |
+ | - Bestätigung im Chat `[CURRENT USER] set the server ACLs for this room.` | ||
- | ## Optional Adminshell | + | ## Send custom reactions to messages (Powerlevel 1) |
- | If you forgot to write '' | + | - Chat `/ |
+ | - `Send Custom Event` | ||
+ | - Event Type: `m.reaction` | ||
+ | - Event Content: | ||
- | There is another way but you should **not** work like that all the time because its not secure. There is a reason you have to write '' | + | ``` |
+ | { | ||
+ | "m.relates_to": | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | } | ||
+ | ``` | ||
- | ## Synpase maintenance tools | + | ## Send custom reactions to messages (Powerlevel >=50) |
- | https:// | + | - Chat `/devtools` |
+ | - `Send Custom Event` | ||
+ | - Rechts unten roten Button `Event` drücken | ||
+ | - Event Type: `m.reaction` | ||
+ | - State Key: leer lassen | ||
+ | - Event Content: | ||
- | ## Installing Bots | + | ``` |
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | } | ||
+ | ``` | ||
- | Matrix Synapse currently does not have a concept of bots, a bot is just a normal user. Usally there is a config and a '' | + | - `Send` |
- | + | ||
- | Install python3 | + | |
- | + | ||
- | < | + | |
- | + | ||
- | then install pip | + | |
- | + | ||
- | < | + | |
- | + | ||
- | then matrix-bot-api from pyp | + | |
- | + | ||
- | < | + | |
- | + | ||
- | and finally fill out the config and start it | + | |
- | + | ||
- | < | + | |
- | ## deactivate presence | + | ## Tombstone Event |
- | * https://github.com/matrix-org/synapse/issues/3971 | + | https://spec.matrix.org/latest/client-server-api/#events-17 |
- | ## How calls work | + | - Chat `/ |
+ | - `Send Custom Event` | ||
+ | - Rechts unten roten Button `Event` drücken | ||
+ | - Event Type: `m.room.tombstone` | ||
+ | - State Key: leer lassen | ||
+ | - Event Content: | ||
- | more or less like this? https:// | + | ``` |
+ | { | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | ``` | ||
- | more or less, but you can also host your own jitsi server if you want, jitsi is still FOSS and self-hostable | + | - `Send` |
- | also, it's a bit nitpicky, but if you use turn, you may want to add a turn-server on the left side, because it's not synapse that does the webrtc relay | + | ## Inactive room blocking address |
- | jitsi is its own thing, riot just allows integrating jitsi in riot | + | IIRC you can request release of alias at support@matrix.org |
- | note that you can self-host jitsi, but if you want riot to use your selfhosted jitsi by default when opening conference calls you'll also want to host an integrations server (ie dimension) | ||
- | everybody assumes it works like this, but it doesn' |