| 31 Mar 2020 |
| 18:37:45 |  hpd | thanks for the pointers, upthumbed! |
| 18:41:45 | hpd | I seem to recall that there was some script somewhere to extract one room from a file with exported keys. But that's also quite hacky and crude of course |
| 18:42:14 | hpd | * I seem to recall that there was some script somewhere to extract one room from a file with exported keys. But that's also quite hacky and crude of course |
| 1 Apr 2020 |
| 03:55:46 | |  @lizaxxx:matrix.org joined the room. |
| 03:55:51 | @lizaxxx:matrix.org | Redacted or Malformed Event |
| 08:58:00 | |  Abuse Managementbanned@lizaxxx:matrix.org (spam). |
| 12:42:22 | |  Niklas Zender invited  Lukas Lihotzki. |
| 12:42:31 | | Lukas Lihotzki joined the room. |
| 2 Apr 2020 |
| 20:46:45 |  Julian Sparber | What's actually encrypted via the m.room.encrypted event? I saw that riot doesn't encrypt some events e.g. typing. |
| 20:47:50 | Julian Sparber | are only room events encrypted? https://matrix.org/docs/spec/client_server/r0.6.0#room-events |
| 20:50:09 | Julian Sparber | checking the traffic of riot also m.room.name isn't encrypted ether |
| 20:50:54 | Julian Sparber | so is it just m.room.message? |
| 20:54:54 |  uhoreg | State events (such as room name, avatar, topic, membership), ephemeral events (e.g. typing, read receipts) are not encrypted. Reactions are not encrypted yet. Messages, files, etc. are encrypted. |
| 20:56:18 | uhoreg | Some state events (e.g. room name) might be encrypted in the future. Some state events (e.g. membership, power levels) will never be encrypted because the server needs to be able to read them in order to enforce permissions. |
| 20:56:17 | Julian Sparber | In reply to @hubert:uhoreg.ca
State events (such as room name, avatar, topic, membership), ephemeral events (e.g. typing, read receipts) are not encrypted. Reactions are not encrypted yet. Messages, files, etc. are encrypted. what other then Messages and files are encrypted? |
| 20:57:45 | Julian Sparber | sure i didn't try to say that they should be encrypted, i was just wondering since the guide https://matrix.org/docs/guides/end-to-end-encryption-implementation-guide isn't really clear on what is encrypted |
| 20:57:48 | uhoreg | Mainly things that fall under m.room.message. |
| 20:57:52 | Julian Sparber | * sure i didn't try to say that they should be encrypted, i was just wondering since the guide https://matrix.org/docs/guides/end-to-end-encryption-implementation-guide isn't really clear on what is encrypted |
| 20:58:16 | Julian Sparber | makes sense |
| 20:58:53 | Julian Sparber | at least for me it wasn't super clear |
| 20:58:58 | Julian Sparber | * at least for me it wasn't super clear |
| 20:59:08 | uhoreg | I think reactions are the only things that aren't state events and not ephemeral events that aren't encrypted. |
| 20:59:18 | uhoreg | (yet) |
| 22:12:23 | |  homulilly joined the room. |
| 3 Apr 2020 |
| 14:10:58 | hpd | Hm, with stuff like https://github.com/vector-im/riotX-android/pull/1198 and the push to turn on e2e by default for DMs: I'd love to have that, but seeing new people evaluating matrix as a selfhosted team-chat solution:
E2E is - with it's current usability - quickly regarded as a major hassle that should only be used when absolutely necessary. At least this doesn't affect the perception of other features.
But s much as cross-signing is going to improve things, a naggy password prompt after account creation for people who don't intend to use encryption, would probably result in an immediate negative impression |
| 14:12:43 | hpd | ⬅︎ no UX professional; ⬆︎ just my impression; ➡︎ grains of salt apply |
| 18:12:10 | |  infdeg joined the room. |
| 20:39:49 | |  Swedneck changed their display name from swedneck to Swedneck. |
| 4 Apr 2020 |
| 04:58:28 | |  glassfiredna00 joined the room. |
| 05:08:18 | |  angelfish joined the room. |
