| 22 Apr 2024 |
 dkasak | In reply to @deepbluev7:neko.dev
As long as I can tell I prefer being able to read that information instead of having to ask the user to send it to me again. It is just frustrating to have an UTD and not being able to recover from it. Additionally, Synapse relies on the key reqests still to notice device lists being out of date, so without them some temporary faults are unrecoverable right now Got an issue ref for that bug? | 19:50:27 |
 Nico | I would need to look it up again, but there are several cases where device lists get out of sync | 19:50:58 |
| Nico | It is fairly obvious when debugging many of the UTDs | 19:51:28 |
| Nico | One such case for example is when one server purged a room, but the other server still thinks you share a room | 19:51:52 |
| Nico | You won't get device list updates then, when you think you should | 19:52:04 |
| Nico | Since on join the server doesn't send them | 19:52:12 |
| Nico | Since synapse doesn't follow the spec and sends no device list updates on join | 19:52:28 |
| Nico | There are also cases where that happens by accident, I hit those in prod a few times, but I don't know how :D | 19:53:01 |
| dkasak | In reply to @deepbluev7:neko.dev
I would need to look it up again, but there are several cases where device lists get out of sync Given there's currently a UTD reduction project going on at Element, there's interest in fixing any bugs that are a frequent source of UTDs. So it might be apt to have a reference | 19:54:18 |
| dkasak | Though I think the investigation so far has not pinpointed that as anywhere near one of the most important causes | 19:55:00 |
| Nico | There were already PRs to fix some of the causes, but they were closed, since people thought they would fix nothing | 19:55:00 |
| Nico | In reply to @dkasak:termina.org.uk
Though I think the investigation so far has not pinpointed that as anywhere near one of the most important causes It is the most regular cause of UTDs for me :D | 19:55:24 |
| Nico | Device list desyncs | 19:55:35 |
| Nico | And in some cases those are basically unrecoverable, since Synapse never really considers its own list out of date, if it doesn't get an update and the other server often decides not to send one ._. | 19:56:19 |
| Nico | The other frequent cause is device messages not arriving, but that is usually easy to fix, since that usually is a broken direct federation | 19:57:42 |
| Nico | I will probably change my synapse to bundle device list updates whenever there is an m.room.encrypted :D | 19:58:44 |
|  @edymarks05:matrix.org joined the room. | 20:59:37 |
| @edymarks05:matrix.org left the room. | 20:59:56 |
| 23 Apr 2024 |
|  Franziskus changed their display name from franziskus to Franziskus. | 14:21:28 |
|  Peter Markuson joined the room. | 18:35:42 |
| Peter Markuson | Hi. I have a question regarding the key storage to decrypt old messages. Let's say I have setup a passphrase to restore old messages which is working great. But then the passphrase it not safe anymore (e.g. leaked) and I would like to change/update it to a new one. How can I achieve this? I have only found a way to reset it and then provide a new one, but with this all old messages are lost. | 18:40:27 |
 Ricardo Duarte | In reply to @peter.markuson:matrix.org
Hi. I have a question regarding the key storage to decrypt old messages. Let's say I have setup a passphrase to restore old messages which is working great. But then the passphrase it not safe anymore (e.g. leaked) and I would like to change/update it to a new one. How can I achieve this? I have only found a way to reset it and then provide a new one, but with this all old messages are lost. What if.... you export all your keys, change the passphrase.. and re-import ? | 18:56:13 |
| Peter Markuson | In reply to @daedric:aguiarvieira.pt
What if.... you export all your keys, change the passphrase.. and re-import ? Thank you, that seems to work :) | 19:02:13 |
| 25 Apr 2024 |
|  Anthony21(On Holiday - back on 13/05/2024) changed their display name from Anthony21 to Anthony21(On Holiday - back on 13/05/2024). | 07:22:23 |
|  Denise [away] changed their display name from Denise to Denise [away]. | 16:26:00 |
|  xeld joined the room. | 18:40:16 |
| xeld set a profile picture. | 18:51:16 |
| xeld changed their profile picture. | 18:54:44 |
| xeld changed their profile picture. | 19:00:59 |
| xeld changed their profile picture. | 19:03:14 |
