mirror of
https://git.envs.net/envs/matrix-doc.git
synced 2024-09-30 11:25:41 +00:00
Add alt text to images
This commit is contained in:
cblte
parent
3dcac340cc
commit
610c80692c
@ -11,7 +11,7 @@ The recommended client for using Matrix is called Element and can be used on dif
|
||||
- **Element Desktop:** [Downloads for Linux/Windows/Mac](#element_desktop)
|
||||
- **Element mobile:** [Android/iOS](#element_mobile)
|
||||
|
||||
|
||||
|
||||
|
||||
## Element Web
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ Currently envs.net does not pay for the use of the source code. The Matrix-Admin
|
||||
|
||||
Matrix is an open standard, the details of interoperable communication using the matrix set of HTTP-APIs are freely published. Matrix is also open source, which means that the source code of the reference servers, clients and services has been released to the public under the Apache v2 license to encourage everyone to run their own servers and clients.
|
||||
|
||||
|
||||
|
||||
|
||||
Since it is free software, improvement requests can be converted into direct programming jobs.
|
||||
|
||||
|
||||
@ -9,31 +9,31 @@ date: 2021-08-03T20:30:00+02:00
|
||||
|
||||
The decision whether a created room should be encrypted in this way must be well thought out and cannot be undone. If the room is large or public, checking all keys of all interlocutors could take a lot of time. But this manual check can be done later on occasion and end-to-end encrypted conversations can be started directly with blind trust for the time being.
|
||||
|
||||
|
||||
|
||||
|
||||
If you want end-to-end encryption (E2EE) to interlocutor:inside in an unencrypted room, you can achieve this by clicking on the settings of the desired room. (or in the room via "Room info" > "Room settings" in the upper right corner):
|
||||
|
||||
|
||||
|
||||
|
||||
To do this, move the Encrypted slider on the Security & Privacy tab:
|
||||
|
||||
|
||||
|
||||
|
||||
This can be confirmed with OK. From now on the messages can only be read by those involved in the conversation. If you have not set up a key protection in the settings before, you should do this now (see [Important settings](/settings/)) to be able to read earlier and in absence received messages.
|
||||
|
||||
Now the encrypted exchange can begin. If you want to verify the correctness of the keys and to document this trustworthiness digitally, you first have to unfold the sidebar by clicking on the person symbol in the upper right corner:
|
||||
|
||||
|
||||
|
||||
|
||||
The contact person can now be clicked on in the opening bar of the participants in the conversation:
|
||||
|
||||
|
||||
|
||||
|
||||
The bar now shows the conversation person in detail. Here a key verification can be initiated by clicking on "Verify". By clicking on "Start Verification" the other side is notified and after confirmation (see next picture) the "Verification by Emojis" can start.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
This verification should be done with the contact person by comparison (e.g. verbally via telephone, in the same room or other medium). Since this is not always easy, the trust can also be expressed first of all (otherwise you will be asked again and again to carry out the verification) and carried out on occasion (e.g. at the next meeting).
|
||||
|
||||
@ -41,22 +41,22 @@ A detailed description of the topic can be found [in this Matrix blog article](h
|
||||
|
||||
The adjustment itself is done via emoji images or QR codes, which can look different depending on the device and icon pack. Also the translation of all interface elements into German is not 100% available.
|
||||
|
||||
|
||||
|
||||
|
||||
This is done analogously in rooms with several participants, each one individually.
|
||||
|
||||
|
||||
|
||||
|
||||
In the respective room rows the following symbols indicate the status of the encryption and the corresponding verification:
|
||||
|
||||
|
||||
|
||||
|
||||
At least one person in the room has not yet been verified.
|
||||
|
||||
|
||||
|
||||
|
||||
There is at least one person in the room who has already been verified, but who in turn has opened further unverified sessions.
|
||||
|
||||
|
||||
|
||||
|
||||
All persons in the room were verified.
|
||||
|
||||
@ -14,15 +14,15 @@ Downloads for: [:fontawesome-solid-download: Windows](https://packages.riot.im/d
|
||||
|
||||
After a desktop installation, make sure to use the existing account. Here the example of Element:
|
||||
|
||||
|
||||
|
||||
|
||||
This is done by clicking on **Change**. Then you will not accidentally end up on the wrong server...
|
||||
|
||||
|
||||
|
||||
|
||||
Now you can manually specify the home server: `matrix.envs.net`
|
||||
|
||||
|
||||
|
||||
|
||||
Afterwards the login with username and password must be carried out:
|
||||
|
||||
@ -42,7 +42,7 @@ Analogous to e-mail addresses, this results in matrix addresses with the followi
|
||||
|
||||
`@username:envs.net`
|
||||
|
||||
|
||||
|
||||
|
||||
## Convenient use of end-to-end encryption (E2EE)
|
||||
|
||||
@ -51,29 +51,31 @@ Matrix not only encrypts transports to and from the home server of envs.net but
|
||||
!!! danger
|
||||
It is highly recommended to use this key backup (with a secure security phrase which is **NOT** your login password)!
|
||||
|
||||
|
||||
|
||||
Alternatively, instead of the security phrase, you can also have a security key generated that serves the same purpose as the security phrase. Furthermore, the security key is generated in addition to the security phrase and should be kept safe and retrievable as an emergency key (e.g. save it as .txt file AND print it out)
|
||||
|
||||
|
||||
|
||||
|
||||
Alternatively, instead of the security phrase, you can also have a security key generated that serves the same purpose as the security phrase. Furthermore, the security key is generated in addition to the security phrase and should be kept safe and retrievable as an emergency key (e.g. save it as .txt file AND print it out)
|
||||
|
||||
|
||||
|
||||
[Other important settings](/settings/) may improve your Matrix experience!
|
||||
|
||||
|
||||
## Requests to setup the key backup
|
||||
|
||||
|
||||
|
||||
|
||||
If you skipped the request to setup the key backup, the next screen would look like this:
|
||||
|
||||
|
||||
|
||||
|
||||
Key protection is highly recommended for worry-free end-to-end encryption. For this reason, a smaller tooltip will prompt you to set up the encryption even after you skip further:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
If you omit this here as well, you will get a last warning if you log off consciously. If no key backup is set up at the latest, encrypted calls that may have already taken place cannot be accessed later. If the tab is closed, this also corresponds to a logout.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Avoid this situation by setting up a key backup!
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ date: 2021-08-03T20:30:00+02:00
|
||||
|
||||
Integrations/Widgets can be managed via the room information in the upper right corner.
|
||||
|
||||
|
||||
|
||||
|
||||
Here, for example, an etherpad, a jitsi video conference, an RSS bot, etc. can be integrated, i.e. services that are located and run on other servers. Therefore, when using integrations, the JavaScript activity of vector.im (for the integration manager) and other servers (e.g. in the Firefox addon NoScript) must be allowed. Since the widgets are often too small to use the services in their full functionality, widgets can often be opened large in new browser tabs.
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ date: 2021-08-03T20:30:00+02:00
|
||||
|
||||
To write to individual persons and thus create a 1:1 chat, first click on the + in the category "Direct messages":
|
||||
|
||||
|
||||
|
||||
|
||||
Now type in the search field and start typing the email address of the person you want to find:
|
||||
|
||||
@ -26,7 +26,7 @@ An invitation e-mail is not sent by Matrix.
|
||||
|
||||
In the search result, click on the target person and then on Go:
|
||||
|
||||
|
||||
|
||||
|
||||
The conversation opens, which can begin after the connected person accepts the invitation [end-to-end encrypted](/encryption/) (meanwhile standard). The connection to the server at envs.net is of course also transport-encrypted. If you explicitly do not want end-to-end encryption for a special reason, an unencrypted room and invite the conversation partners to it.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -14,35 +14,35 @@ Matrix not only encrypts transports to and from the home server of envs.net but
|
||||
!!! 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)!
|
||||
|
||||
|
||||
|
||||
|
||||
If you skip this now, the next screen would look like this:
|
||||
|
||||
|
||||
|
||||
|
||||
Key protection is highly recommended for worry-free end-to-end encryption. For this reason, a smaller tooltip will prompt you to set up the encryption even after you skip further:
|
||||
|
||||
|
||||
|
||||
|
||||
If you omit this here as well, you will get a last warning if you log off consciously. If no key backup is set up at the latest, encrypted calls that may have already taken place cannot be accessed later. If the tab is closed, this also corresponds to a logout.
|
||||
|
||||
|
||||
|
||||
|
||||
## Other important settings
|
||||
|
||||
After successfully setting up the key backup, you now activate the desktop notifications:
|
||||
|
||||
|
||||
|
||||
|
||||
This can be undone later and especially individual "conversations" can be set in their notification authority
|
||||
|
||||
Adjust settings in the Settings menu: to do this, click on the line of the e-mail address and the downward pointing triangle and then on the line "All settings":
|
||||
|
||||
|
||||
|
||||
|
||||
In the settings you can change your display name ("First Name Last Name") in the **General** tab if necessary and upload a profile picture (select profile picture <5MB):
|
||||
|
||||
|
||||
|
||||
|
||||
The e-mail address field is not necessarily to be filled in, since an e-mail address is stored via your envs.net login. Theoretically you can add more addresses here, e.g. to have notifications about missed messages sent to another e-mail address.
|
||||
|
||||
@ -50,11 +50,11 @@ On the same page you can also change the design theme from light to dark.
|
||||
|
||||
In the **Notifications** tab you can activate e-mail notifications (to be informed about missed messages) as well as acoustic notifications and set them granularly for individual activities of others. For more information see the [notifications](/notifications/).
|
||||
|
||||
|
||||
|
||||
|
||||
In the **Voice & Video** tab, you can authorize the Matrix client element to use your media (camera + microphone), allow direct voice/video calls via peer-to-peer connections, and in the case of video calls, to see yourself in a small picture:
|
||||
|
||||
|
||||
|
||||
|
||||
Fortunately, 1:1 calls start end-to-end encrypted by default. To really trust this encryption with a good feeling, users:inside can perform the key comparison with interlocutor:inside. To ensure that this also applies to all devices of these conversational partners, Matrix users must in turn verify the keys of all their devices with each other (technical term: cross-signing). If you follow the instructions below, this can be done very conveniently.
|
||||
|
||||
@ -64,7 +64,7 @@ In the **Security & Privacy** tab you will find all your devices that have been
|
||||
|
||||
* Remove any sessions that are no longer in use by marking the square box at the end of the line and clicking on the red button that appears.
|
||||
|
||||
|
||||
|
||||
|
||||
* The device names also give you an overview when comparing keys between your devices.
|
||||
|
||||
@ -72,16 +72,16 @@ In the **Security & Privacy** tab you will find all your devices that have been
|
||||
|
||||
* 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!
|
||||
|
||||
|
||||
|
||||
|
||||
## Secure Backup
|
||||
|
||||
If not set up after initial registration: The **Secure Backup** is a valuable achievement, as it enables the keys of all end-to-end encrypted calls to be centrally secured on the envs.net server with a password. This allows convenient use of multiple devices or matrix clients. To do so, click on "Start using key backup" and choose a strong security phrase (but not the envs.net password). This security phrase will always have to be entered if keys are to be synchronized with the key backup.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Alternatively, instead of the security phrase, you can also have a security key generated that serves the same purpose as the security phrase. Furthermore, the security key is generated in addition to the security phrase and should be kept safe and retrievable as an emergency key (e.g. save it as .txt file or print it out)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ Spaces can only be created for yourself or for others (if you invite them into a
|
||||
|
||||
Existing rooms can be assigned to a space in the space settings.
|
||||
|
||||
|
||||
|
||||
|
||||
A space created with the + button can be drag'n'dropped from the spaces avatar (little picture) onto the sidebar.
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user