update room pages

This commit is contained in:
creme 2021-08-05 17:28:22 +02:00
parent 1862d8f515
commit be7f10d3fc
No known key found for this signature in database
GPG Key ID: C147C3B7FBDF08D0
5 changed files with 39 additions and 52 deletions

View File

@ -1,15 +1,14 @@
---
title: "Rooms"
date: 2020-07-02T21:23:14+02:00
chapter: true
draft: false
weight: 35
date: 2021-08-03T20:30:00+02:00
---
# Rooms
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]({{< relref "rooms/create" >}})
2. [find rooms]({{< relref "rooms/find" >}})
3. [delete rooms]({{< relref "rooms/delete" >}})
4. [share rooms]({{< relref "rooms/sharing" >}})
1. [create rooms](/rooms/create/)
2. [find rooms]({/rooms/find/)
3. [delete rooms](/rooms/delete/)
4. [share rooms](/rooms/sharing/)

View File

@ -1,16 +1,14 @@
---
title: "Create rooms"
date: 2020-07-02T21:23:14+02:00
chapter: true
draft: false
weight: 10
date: 2021-08-03T20:30:00+02:00
---
## Create rooms and take responsibility
New rooms are created using the + in the left bar in the category Rooms.
![Marking of the room add button](/images/01_Rooms_en.png)
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]({{< relref "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 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.
![Input menu for the room name](/images/02_Rooms_en.png)
@ -20,9 +18,9 @@ The room is now created and gets any colored icon color. By clicking on the i in
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:
#roomaddress:tu-dresden.de
`#roomaddress:envs.net`
Another important setting here is whether the room should appear in the room directory of the TU Dresden. You can also activate the URL preview for the room here.
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.
![Room settings](/images/04_Rooms_en.png)
@ -38,12 +36,11 @@ In the **Security & Privacy** tab, room administrators have to make important de
A "call waiting" to closed rooms is not yet possible. The closest workaround is to send a direct message to the room administrator, who will then invite you.
{{% notice note %}}
The end-to-end encryption of large or public spaces is critical in terms of the difficult verification for many people. See [Use end-to-end encryption]({{< relref "encryption" >}}).
{{% /notice %}}
{{% notice 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.
{{% /notice %}}
!!! note
The end-to-end encryption of large or public spaces is critical in terms of the difficult verification for many people. See [Use end-to-end encryption](/encryption/).
!!! 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.
![Drop-down menu for the assignment of rights for room participants (image row 1)](/images/06_Users-Permissions-1_en.png)
![Drop-down menu for the assignment of rights for room participants (image series 2)](/images/06_Users-Permissions-2_en.png)

View File

@ -1,12 +1,9 @@
---
title: "Delete rooms"
date: 2020-07-02T21:23:14+02:00
chapter: true
draft: false
weight: 30
date: 2021-08-03T20:30:00+02:00
---
## Delete rooms and leave rooms
## Delete rooms and leave rooms
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.
@ -14,4 +11,4 @@ When leaving rooms, they no longer appear in the room list (left column). If the
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.
An export of the room history e.g. into a .txt or .html file is not yet possible: https://github.com/vector-im/element-web/issues/2630
An export of the room history e.g. into a .txt or .html file is not yet possible: [https://github.com/vector-im/element-web/issues/2630](https://github.com/vector-im/element-web/issues/2630)

View File

@ -1,16 +1,13 @@
---
title: "find rooms"
date: 2020-07-02T21:23:14+02:00
chapter: true
draft: false
weight: 20
date: 2021-08-03T20:30:00+02:00
---
## Find rooms
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 the TUD-Matrix.
![Menu to find public rooms](/images/01_Find_en.png)
{{% notice note %}}
The global federation is currently in test operation. It is possible that the Federation will be restricted again at a later date.
{{% /notice %}}
!!! note
The global federation is currently in test operation. It is possible that the Federation will be restricted again at a later date.

View File

@ -1,25 +1,23 @@
---
title: "Share rooms"
date: 2020-07-02T21:23:14+02:00
chapter: true
draft: false
weight: 40
date: 2021-08-03T20:30:00+02:00
---
# Share rooms and make them public
{{% notice warning %}}
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/ from where you can access the room via an Element web app from https://element.io. In order to share a room within TU Dresden please use the methode explained in this artice.
{{% /notice %}}
!!! 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.
Every room has a so-called room-address, which can be found in the room settings under the sub-menu Advanced. A room address looks like this:
!aen6iekahv8Pi0zohf:tu-dresden.de
`!FHhQNJRAdNkLNiWgKu:envs.net`
Because this cryptic address can not be read easily by humans, custom room addresses can be assigned. This is only necessary for rooms, which you want to make public and reference in other places.
Room addresses can either be globally published addresses (findable by users in other servers - useful for topics beyond the TU Dresden) or local addresses, which is only valid within the matrix home server at the TU Dresden.
Room addresses can either be globally published addresses (findable by users in other servers - useful for topics beyond envs.net) or local addresses, which is only valid within the matrix home server at envs.net.
{{% notice note %}}
To publish a global address, you have to create a local address first. **It is necessary to create a local address in both cases!**
{{% /notice %}}
!!! note
To publish a global address, you have to create a local address first. **It is necessary to create a local address in both cases!**
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:
@ -35,16 +33,15 @@ You can also assign different addresses. If the room address should be published
The room address then has the following structure
#Room-address-name:tu-dresden.de
`#room-address-name:envs.net`
**Suggestion Nr. 1 for sharing a room address:**
When you want to share a room within matrix, you can use the internal link feature by typing (the first characters of) the local address
```
#room_address:tu-dresden.de
```
into the chat line. If you are a member of that room, you can confirm the auto-completion with a mouse click. This is a special link for a usage within matrix, which will open directly in the client of the receiver (with a mouse click).
`#room_address:envs.net`
into the chat line. If you are a member of that room, you can confirm the auto-completion with a mouse click. This is a special link for a usage within matrix, which will open directly in the client of the receiver (with a mouse click).
**Suggestion Nr. 2 for sharing a room address:**
@ -60,6 +57,6 @@ https://matrix.to/#/#Room-address-name:tu-dresden.de?via=tu-dresden.de
Furthermore, you also can create a hyperlink to the room, which you have to construct in this way:
https://matrix.tu-dresden.de/#/room/#roomaddress:tu-dresden.de
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.