fix typo's
This commit is contained in:
creme
parent
c8c62427df
commit
035d4cf8ee
|
|
@ -30,14 +30,14 @@ Analogous to e-mail addresses, this results in matrix addresses with the followi
|
|||
`@username:envs.net`
|
||||
|
||||
!!! note
|
||||
If you want to start immediately with a [Matrix Client](/clients/) instead of the above mentioned website (Element Web-App hosted on envs.net), it is important to change the home server from the usually default `matrix.org to` [`https://matrix.envs.net`](https://matrix.envs.net) (shown in the following three screenshots)
|
||||
If you want to start immediately with a [Matrix Client](/clients/) instead of the above mentioned website (Element Web-App hosted on envs.net), it is important to change the homeserver from the usually default `matrix.org` to `matrix.envs.net` (shown in the following three screenshots)
|
||||
|
||||
|
||||
|
||||
1. click on change
|
||||
|
||||
2. mark the preset home server address and remove it
|
||||
3. entry of the matrix home server address of envs.net
|
||||
|
||||
2. mark the preset homeserver address and remove it
|
||||
3. entry of the matrix homeserver address of envs.net
|
||||
|
||||
## Browser settings
|
||||
|
||||
|
|
|
|||
|
|
@ -15,9 +15,9 @@ This is done by clicking on **Edit**. Then you will not accidentally end up on t
|
|||
|
||||
|
||||
|
||||
Now you can manually specify the home server: `matrix.envs.net`
|
||||
Now you can manually specify the homeserver: `matrix.envs.net`
|
||||
|
||||
|
||||
|
||||
|
||||
Afterwards the one-time login with Username and Password must be carried out:
|
||||
|
||||
|
|
|
|||
|
|
@ -20,9 +20,9 @@ This is done by clicking on **Change**. Then you will not accidentally end up on
|
|||
|
||||
|
||||
|
||||
Now you can manually specify the home server: `matrix.envs.net`
|
||||
Now you can manually specify the homeserver: `matrix.envs.net`
|
||||
|
||||
|
||||
|
||||
|
||||
Afterwards the login with username and password must be carried out:
|
||||
|
||||
|
|
@ -46,7 +46,7 @@ Analogous to e-mail addresses, this results in matrix addresses with the followi
|
|||
|
||||
## Convenient use of end-to-end encryption (E2EE)
|
||||
|
||||
Matrix not only encrypts transports to and from the home server of envs.net but also allows the use of end-to-end encryption (E2EE). For this, cryptographic keys have to be exchanged between all devices that want to write end-to-end encrypted. This technical necessity sounds and is complicated, but in the meantime it has become very convenient for the users. The many cryptographic keys created by the client are stored on the respective device. If this is a tab in a browser, for example, there is a risk that this tab will be closed unintentionally. Then all encrypted contents are no longer readable. To prevent this from happening, a key protection is offered on the home server of the envs.net, on which (protected with a security phrase (or security key that can be calculated from it) all cryptographic keys are stored encrypted.
|
||||
Matrix not only encrypts transports to and from the homeserver of envs.net but also allows the use of end-to-end encryption (E2EE). For this, cryptographic keys have to be exchanged between all devices that want to write end-to-end encrypted. This technical necessity sounds and is complicated, but in the meantime it has become very convenient for the users. The many cryptographic keys created by the client are stored on the respective device. If this is a tab in a browser, for example, there is a risk that this tab will be closed unintentionally. Then all encrypted contents are no longer readable. To prevent this from happening, a key protection is offered on the homeserver of the envs.net, on which (protected with a security phrase (or security key that can be calculated from it) all cryptographic keys are stored encrypted.
|
||||
|
||||
!!! danger
|
||||
It is highly recommended to use this key backup (with a secure security phrase which is **NOT** your login password)!
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ 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 `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.
|
||||
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` 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.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Every room has a so-called room-address, which can be found in the room settings
|
|||
|
||||
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 envs.net) or local addresses, which is only valid within the matrix home server at envs.net.
|
||||
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 homeserver at envs.net.
|
||||
|
||||
!!! 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!**
|
||||
|
|
@ -27,7 +27,7 @@ Afterwards a recognizable name of this room link can be assigned in the "Room al
|
|||
|
||||
|
||||
|
||||
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.
|
||||
You can also assign different addresses. If the room address should be published in the room directory of the matrix homeserver of the `envs.net`, this can be done by the following.
|
||||
|
||||
|
||||
|
||||
|
|
@ -45,7 +45,7 @@ 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 homeserver the room is to be entered.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ authors:
|
|||
|
||||
## Convenient use of end-to-end encryption (E2EE)
|
||||
|
||||
Matrix not only encrypts transports to and from the home server of envs.net but also allows the use of end-to-end encryption (E2EE). For this, cryptographic keys have to be exchanged between all devices that want to write end-to-end encrypted. This technical necessity sounds and is complicated, but in the meantime it has become very convenient for the users. The many cryptographic keys created by the client are stored on the respective device. If this is a tab in a browser, for example, there is a risk that this tab will be closed unintentionally. Then all encrypted contents are no longer readable. To prevent this from happening, a key protection is offered on the home server of the envs.net, on which (protected with a security phrase (or security key that can be calculated from it) all cryptographic keys are stored encrypted.
|
||||
Matrix not only encrypts transports to and from the homeserver of envs.net but also allows the use of end-to-end encryption (E2EE). For this, cryptographic keys have to be exchanged between all devices that want to write end-to-end encrypted. This technical necessity sounds and is complicated, but in the meantime it has become very convenient for the users. The many cryptographic keys created by the client are stored on the respective device. If this is a tab in a browser, for example, there is a risk that this tab will be closed unintentionally. Then all encrypted contents are no longer readable. To prevent this from happening, a key protection is offered on the homeserver of the envs.net, on which (protected with a security phrase (or security key that can be calculated from it) all cryptographic keys are stored encrypted.
|
||||
|
||||
!!! danger
|
||||
It is highly recommended to use this key backup (with a secure security phrase which is **NOT** your login password) and read on at [Other important settings](#other_important_settings)!
|
||||
|
|
@ -70,7 +70,7 @@ In the **Security & Privacy** tab you will find all your devices that have been
|
|||
|
||||
* The public names of your devices which can be assigned here (by clicking on them with the mouse) can also be viewed by your conversation partner:inside. This helps if they want to compare the cryptographic keys of your devices (e.g. laptop + cell phone) and can easily identify the device names.
|
||||
|
||||
* The many cryptographic keys are stored on the respective device. If this is e.g. a tab in a browser, there is a risk that this tab will be closed unintentionally. Then all encrypted contents are no longer readable. To prevent this from happening, a key protection is offered on the home server of envs.net, on which (protected by a passphrase) all cryptographic keys are stored encrypted. It is strongly recommended to use this key backup!
|
||||
* The many cryptographic keys are stored on the respective device. If this is e.g. a tab in a browser, there is a risk that this tab will be closed unintentionally. Then all encrypted contents are no longer readable. To prevent this from happening, a key protection is offered on the homeserver of envs.net, on which (protected by a passphrase) all cryptographic keys are stored encrypted. It is strongly recommended to use this key backup!
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue