| 2 Oct 2023 |
|  Ellenor Bjornsdottir changed their display name from Ellenor Bjornsdottir to ellenor2000. | 08:10:30 |
| Ellenor Bjornsdottir left the room. | 08:10:30 |
| Ellenor Bjornsdottir joined the room. | 08:10:31 |
|  Tom Black changed their profile picture. | 10:16:47 |
|  Denise [away] changed their display name from Denise to Denise [away]. | 11:40:16 |
 Marco Romano | Where can I find in the spec the meaning/usage of the fields other than content and type inside an event?
Stuff like room_id, user_id etc.
I mean, most of them are self explanatory but why do I see them only in some events whilst I don't in others? | 15:03:24 |
 Kévin Commaille | They are defined on the endpoints that accept/return them usually | 15:06:16 |
| Kévin Commaille | And the fields inside the content are defined where the event type is defined | 15:07:46 |
 dmr | In reply to @marcor:element.io
Where can I find in the spec the meaning/usage of the fields other than content and type inside an event?
Stuff like room_id, user_id etc.
I mean, most of them are self explanatory but why do I see them only in some events whilst I don't in others? https://spec.matrix.org/v1.8/rooms/v11/#event-format-1 might answer some of this. Note that:
- the fields on a PDU depend on its room's version
- events are presented differently to clients down /sync than elsewhere. Search for
ClientEventWithoutRoomID in https://spec.matrix.org/v1.8/client-server-api/#get_matrixclientv3sync
| 15:10:20 |
|  Blake Leonard changed their profile picture. | 16:34:33 |
| Ellenor Bjornsdottir changed their display name from Ellenor Bjornsdottir to ellenor2000. | 18:42:40 |
| Ellenor Bjornsdottir left the room. | 18:42:41 |
| Ellenor Bjornsdottir joined the room. | 18:42:42 |
| Ellenor Bjornsdottir changed their display name from Ellenor Bjornsdottir to ellenor2000. | 19:36:55 |
| Ellenor Bjornsdottir left the room. | 19:36:55 |
| Ellenor Bjornsdottir joined the room. | 19:36:56 |
| Ellenor Bjornsdottir changed their display name from Ellenor Bjornsdottir to ellenor2000. | 20:30:21 |
| Ellenor Bjornsdottir left the room. | 20:30:21 |
| Ellenor Bjornsdottir joined the room. | 20:30:22 |
| Ellenor Bjornsdottir changed their display name from Ellenor Bjornsdottir to ellenor2000. | 21:46:33 |
| Ellenor Bjornsdottir left the room. | 21:46:34 |
| Ellenor Bjornsdottir joined the room. | 21:46:35 |
|  @wreck:matrix.org removed their display name wreck. | 22:38:18 |
| 3 Oct 2023 |
| Marco Romano | In reply to @dmrobertson:matrix.org
https://spec.matrix.org/v1.8/rooms/v11/#event-format-1 might answer some of this. Note that:
- the fields on a PDU depend on its room's version
- events are presented differently to clients down /sync than elsewhere. Search for
ClientEventWithoutRoomID in https://spec.matrix.org/v1.8/client-server-api/#get_matrixclientv3sync
events are presented differently to clients down /sync than elsewhere. Search for ClientEventWithoutRoomID
Oh great, this helps, but then why do I still see the room_id field on a message when doing "View source" from within eleweb?
| 06:37:08 |
| Marco Romano | Another question: Is there a place in the spec where it explains how to decrypt an event? I don't mean how old/megolm works, I mean at a higher level: after we have decrypted the "cyphertext", where do we put that data? | 06:44:07 |
| Marco Romano | 
Download Screenshot 2023-10-03 at 08.32.17.png | 06:44:13 |
| Marco Romano | In other words: How do we go from the "original event source" in the pic to the "decrypted event source"?
And why the decrypted one is missing a lot of fields like event_id and origin_server_ts ? | 06:45:05 |
 richvdh | I think the bit of spec you're after is https://spec.matrix.org/v1.8/client-server-api/#mmegolmv1aes-sha2, but in short: if you un-base64 the ciphertext and feed it into megolm, then what you get is the "decrypted event source" | 07:22:25 |
| richvdh | you just get a json string out | 07:23:19 |
|  Kerry Archibald [UTC+13 🇳🇿] changed their display name from Kerry Archibald [UTC+13 🇳🇿][out] to Kerry Archibald [UTC+13 🇳🇿]. | 07:57:49 |
