mirror of
https://git.envs.net/envs/matrix-doc.git
synced 2024-10-01 11:55:35 +00:00
Merge pull request 'master' (#6) from cblte/matrix-doc:master into master
Reviewed-on: https://git.envs.net/envs/matrix-doc/pulls/6
This commit is contained in:
creme
commit
bddcabd222
BIN
docs/images/notification-rooms.png
Normal file
BIN
docs/images/notification-rooms.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 90 KiB |
BIN
docs/images/notifications2.png
Normal file
BIN
docs/images/notifications2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 172 KiB |
@ -23,10 +23,10 @@ Here experiences must be made if necessary, which help with the estimate, which
|
||||
|
||||
See [recommendations for first steps after first login](/settings/#other_important_settings)
|
||||
|
||||
|
||||
|
||||
|
||||
### Roomwise settings
|
||||
|
||||
When the mouse is moved over individual rooms in the room list, 3 grey dots appear on the right-hand edge for each room. After clicking on them, you can set up the notifications for each room individually.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ date: 2021-08-03T20:30:00+02:00
|
||||
Conversations are organized in matrix in rooms. 1:1 conversations are also rooms, but for now with only two people. In this
|
||||
Category is about
|
||||
|
||||
1. [Create rooms](/rooms/create/)
|
||||
2. [Find rooms](/rooms/find/)
|
||||
3. [Delete rooms](/rooms/delete/)
|
||||
4. [Share rooms](/rooms/sharing/)
|
||||
- [Create rooms](/rooms/create/)
|
||||
- [Find rooms](/rooms/find/)
|
||||
- [Delete rooms](/rooms/delete/)
|
||||
- [Share rooms](/rooms/sharing/)
|
||||
|
||||
@ -7,14 +7,14 @@ date: 2021-08-03T20:30:00+02:00
|
||||
|
||||
New rooms are created using the + in the left bar in the category Rooms.
|
||||
|
||||
|
||||
Then the room name must be assigned. You can also optionally assign a theme (which can be adapted more often later). Optionally, the room can be made publicly accessible (this is not the default setting). With an additional click on "Show more settings" it can be prevented that Matrix users from outside the TU Dresden home server (Homeserver) can enter the room. By default, all new rooms (just like all new 1:1 calls) have [end-to-end encryption](/encryption/) set up. If this is not desired (e.g. because verification of the participants becomes very impractical in very large rooms) you can use the slider before creating the room to not activate end-to-end encryption.
|
||||
|
||||
Then the room name must be assigned. You can also optionally assign a theme (which can be adapted more often later). Optionally, the room can be made publicly accessible (this is not the default setting). With an additional click on "Show more settings" it can be prevented that Matrix users from outside the `envs.net` home server (Homeserver) can enter the room. By default, all new rooms (just like all new 1:1 calls) have [end-to-end encryption](/encryption/) set up. If this is not desired (e.g. because verification of the participants becomes very impractical in very large rooms) you can use the slider before creating the room to not activate end-to-end encryption.
|
||||
|
||||
|
||||
|
||||
|
||||
The room is now created and gets any colored icon color. By clicking on the i in the upper right corner and then the gear wheel "room settings" you can access exactly those room settings:
|
||||
|
||||
|
||||
|
||||
|
||||
Here you can upload a room-specific image/icon in the **General** tab. An important feature is the assignment of a local room address. This address is easier to read by humans than the cryptic room address, which is always present in parallel (you can see it in the tab Advanced). The assigned local room address can then easily be distributed in public or to the target group and has the following structure:
|
||||
|
||||
@ -22,11 +22,11 @@ Here you can upload a room-specific image/icon in the **General** tab. An import
|
||||
|
||||
Another important setting here is whether the room should appear in the room directory of envs.net. You can also activate the URL preview for the room here.
|
||||
|
||||
|
||||
|
||||
|
||||
In the **Security & Privacy** tab, room administrators have to make important decisions: Should the room be encrypted? Who is allowed access? And who can read the chat history?
|
||||
|
||||
|
||||
|
||||
|
||||
**To explain the room access options:**
|
||||
|
||||
@ -42,9 +42,8 @@ A "call waiting" to closed rooms is not yet possible. The closest workaround is
|
||||
!!! warning
|
||||
As the room administrator, you have **responsibility** for the content shared in the room (e.g. false messages, hate mail, etc.). Include other people in this responsibility by assigning roles in the right bar (after clicking on the person icon) via the "Permission Level" drop-down menu, e.g. Administrator:inside or Moderator:inside.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
You can also use the admin tools to react to any misbehavior (mute, kick, ban, delete recent messages).
|
||||
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ date: 2021-08-03T20:30:00+02:00
|
||||
|
||||
When leaving rooms, they no longer appear in the room list (left column). If the last person in the room leaves the room, the room is still in the archive for 7 days, but is then permanently deleted.
|
||||
|
||||
|
||||
|
||||
|
||||
As administrator:in, all room members should first be "kicked" (removed from the room), then the person is the last to leave the room and thus initiates the later deletion by the server.
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ date: 2021-08-03T20:30:00+02:00
|
||||
|
||||
The room directory, in which the publicly accessible rooms are presented, can be reached via the button "Discover / Explore" in the upper left corner under the own display name. Here you can immediately search for a room on envs.net.
|
||||
|
||||
|
||||
|
||||
|
||||
!!! note
|
||||
The global federation is currently in test operation. It is possible that the Federation will be restricted again at a later date.
|
||||
|
||||
@ -3,7 +3,7 @@ title: "Share rooms"
|
||||
date: 2021-08-03T20:30:00+02:00
|
||||
---
|
||||
|
||||
# Share rooms and make them public
|
||||
## Share rooms and make them public
|
||||
|
||||
!!! note
|
||||
The share icon in the upper right corner of each room also provides a link, a QR code and various social networks. The link, however, leads to [https://matrix.to/](https://matrix.to/) from where you can access the room via an Element web app from [https://element.io](https://element.io). In order to share a room within envs.net please use the methode explained in this artice.
|
||||
@ -21,15 +21,15 @@ Room addresses can either be globally published addresses (findable by users in
|
||||
|
||||
For the more common case of the desired local address, click on "Show more" under Local Addresses in the room settings under the General tab:
|
||||
|
||||
|
||||
|
||||
|
||||
Afterwards a recognizable name of this room link can be assigned in the "Room alias" line (no spaces are allowed!):
|
||||
|
||||
|
||||
|
||||
|
||||
You can also assign different addresses. If the room address should be published in the room directory of the matrix home server of the TU Dresden, this can be done by the following.
|
||||
You can also assign different addresses. If the room address should be published in the room directory of the matrix home server of the `envs.net`, this can be done by the following.
|
||||
|
||||
|
||||
|
||||
|
||||
The room address then has the following structure
|
||||
|
||||
@ -45,18 +45,16 @@ into the chat line. If you are a member of that room, you can confirm the auto-c
|
||||
|
||||
**Suggestion Nr. 2 for sharing a room address:**
|
||||
|
||||
The share icon at the top right of each room also offers a matrix.to-link, as well as a QR code and various social networks. The matrix.to-link leads to a page where you can select how the link should be opened. For example, the installed client Element Desktop can be used, or it can be selected via which home server the room is to be entered.
|
||||
The share icon at the top right of each room also offers a `matrix.to`-link, as well as a QR code and various social networks. The `matrix.to`-link leads to a page where you can select how the link should be opened. For example, the installed client Element Desktop can be used, or it can be selected via which home server the room is to be entered.
|
||||
|
||||
|
||||
|
||||
|
||||
```
|
||||
https://matrix.to/#/#room-address-name:envs.net?via=envs.net
|
||||
```
|
||||
`https://matrix.to/#/#room-address-name:envs.net?via=envs.net`
|
||||
|
||||
**Suggestion Nr. 3 for sharing a room address:**
|
||||
|
||||
Furthermore, you also can create a hyperlink to the room, which you have to construct in this way:
|
||||
|
||||
https://matrix.envs.net/#/room/#roomaddress:envs.net
|
||||
`https://matrix.envs.net/#/room/#roomaddress:envs.net`
|
||||
|
||||
resulting in an internet address (URL) which can be easily distributed to the public or target group. BUT, **this link opens only an Element Web in the browser** of the people, not in an installed Element Desktop. More universal (espc. for the large group of people with Element Desktop), and more advised by the Matrix-Admin-Team, is the above mentioned method with the matrix.to-Link.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user