| 28 Apr 2025 |
|  Ciprian Arsenie joined the room. | 10:14:28 |
|  floflobel joined the room. | 13:31:03 |
|  Mathias joined the room. | 17:07:12 |
| Mathias | Why does the Signal bridge create rooms for 1:1 chats while whatsapp create persons for 1:1 chats? | 17:12:03 |
 tulir | https://docs.mau.fi/bridges/general/troubleshooting.html#why-are-direct-messages-showing-up-under-rooms-instead-of-people | 17:12:16 |
| Mathias | tulir: It's always a pleasure to get an answer from you 🙂 | 17:13:26 |
| Mathias | and is there any possiblity to sync the user photos directly? IIR sync was a command somehwhere in the past | 17:15:42 |
| Mathias | And should I from time to time regenerate the config.yaml file? Mine exists since 2022 | 17:33:21 |
| tulir | no, configs are updated automatically | 17:33:30 |
| Mathias | Ahh that’s a great approach! I am missing that for synapse | 17:34:15 |
| 29 Apr 2025 |
|  Jacob joined the room. | 00:25:41 |
 GitHub | [mautrix/signal] hifi pushed
1 commit
to
fix/websocket-close-race (new branch): -
7f9264b8
signalwebsocket: Close and wait for main loop when socket is closed
| 10:17:43 |
| GitHub | [mautrix/signal] hifi opened
pull request
#597: signalwebsocket: Close and wait for main loop when socket is closed
| 10:17:52 |
| GitHub | [mautrix/signal] hifi force pushed
1 commit
to
fix/websocket-close-race: -
8365c811
signalwebsocket: Close and wait for main loop when socket is closed
| 10:23:00 |
| GitHub | [mautrix/signal] hifi requested a review from tulir for
pull request
#597: signalwebsocket: Close and wait for main loop when socket is closed
| 10:25:00 |
| GitHub | [mautrix/signal] hifi force pushed
1 commit
to
fix/websocket-close-race: -
1dca367f
signalwebsocket: Close and wait for main loop when socket is closed
| 10:38:51 |
| GitHub | [mautrix/signal] hifi force pushed
1 commit
to
fix/websocket-close-race: -
798e021b
signalwebsocket: Close and wait for main loop when socket is closed
| 10:43:06 |
| GitHub | [mautrix/signal] hifi force pushed
1 commit
to
fix/websocket-close-race: -
605c9829
signalwebsocket: Close and wait for main loop when socket is closed
| 10:44:47 |
| GitHub | [mautrix/signal] hifi force pushed
1 commit
to
fix/websocket-close-race: -
15a8b80c
signalwebsocket: Close and wait for main loop when socket is closed
| 11:09:12 |
| GitHub | [mautrix/signal] tulir approved
pull request
#597: signalwebsocket: Close and wait for main loop when socket is closed | 11:09:59 |
| GitHub | [mautrix/signal] hifi merged
pull request
#597: signalwebsocket: Close and wait for main loop when socket is closed
| 11:12:10 |
| GitHub | [mautrix/signal] hifi pushed
1 commit
to
main: -
5e72e4da
signalwebsocket: Close and wait for main loop when socket is closed (#59…
| 11:12:10 |
| GitHub | [mautrix/signal] hifi deleted branch fix/websocket-close-race | 11:12:10 |
 Peter-Paul | hey all - perhaps a question which comes by a lot - i have a chat with a few people on signal which should have a room in matrix as well / created / initiated by synapse | 12:16:08 |
| Peter-Paul | however the situation now is that the invites from matrix (for joining a new or existing room are not working anymore | 12:16:39 |
| Peter-Paul | it mentions "you already have a conversation" and when joining that room it says "no servers are present in the room"
what did i do -> checked manually all the rooms via synapse admin and via psql and cleaned up verything | 12:17:19 |
| Peter-Paul | but im still receiving this message for a room which doesnt exist / rsyncing contacts / clearing caches - none seems to work ...
Anyone a suggestion? :-) | 12:17:58 |
 Mathijs | This sounds like a question for matrix support, not the signal bridge | 13:49:15 |
| Mathijs | Probably #synapse:matrix.org ? | 13:49:31 |
| Mathijs | Maybe I got that wrong, though | 13:50:08 |
