| 24 Apr 2025 |
 GitHub | [mautrix/signal] jannis3005 edited
issue
#596: Unable to Upload Keys with Next-Gen Auth
| 06:42:17 |
| GitHub | [mautrix/signal] jannis3005 edited
issue
#596: Unable to Upload Keys with Next-Gen Auth
| 06:42:53 |
| GitHub | [mautrix/signal] tulir closed
issue
#596: Unable to Upload Keys with Next-Gen Auth
| 08:27:36 |
|  Jannis Göing joined the room. | 08:55:27 |
| GitHub | [mautrix/signal] tulir commented on
issue
#596: Unable to Upload Keys with Next-Gen Auth:
https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html#use-with-next-gen-auth-mas-msc4190
| 09:04:07 |
| GitHub | [mautrix/signal] jannis3005 commented on
issue
#596: Unable to Upload Keys with Next-Gen Auth:
I'm really sorry, I missed that. Thanks for pointing me to the right place in the docs.
| 09:17:53 |
| Jannis Göing left the room. | 09:17:58 |
|  Alexa Runa joined the room. | 12:04:10 |
| GitHub | [mautrix/signal] tulir pushed
2 commits
to
main: -
6e62a683
signalmeow/protobuf: rebuild without embed-raw
-
408cfbd9
signalmeow/store: fix reading last message ID
| 16:18:11 |
|  Ich Eben joined the room. | 20:10:09 |
|  Sami Olmari joined the room. | 20:50:07 |
|  Amy joined the room. | 23:07:55 |
| 25 Apr 2025 |
|  Jim Killock joined the room. | 08:39:56 |
|  DrRac27 joined the room. | 11:45:11 |
|  pantek joined the room. | 12:24:30 |
|  vaw joined the room. | 12:59:03 |
|  Joker 🇩🇪 joined the room. | 14:35:41 |
 wreck | if i want to enable appservice double-puppeting for a server that my bridge is not running on, i need to add the doublepuppet.yaml AS file to that server... but should the users regex be for the server of the bridge-bot, or the server of the users? | 16:33:45 |
 tulir | the other server | 16:34:06 |
| wreck | where the bridge is actually running, and creating puppet accounts | 16:34:19 |
| tulir | double puppeting isn't related to ghost accounts | 16:34:37 |
| wreck | mmm | 16:35:06 |
| wreck | when you say "the other server", which one are you referring to? i'm unclear on the context. | 16:35:23 |
| wreck | if the bridge is running on serverA, and i want to allow users on serverB to use it... the user regex should match serverA, right? | 16:36:07 |
| tulir | registration namespaces specify which users the appservice is allowed to control | 16:37:49 |
| wreck | ah... so, if the doublepuppet appservice is controlling the user's matrix account, it should match the server that the user's account is on | 16:38:44 |
| wreck | i'll be honest, the idea of double-puppetting is still very fuzzy to me | 16:39:07 |
| wreck | perhaps because i've not used many non-puppeting bridges, so i don't really know what the alternative is like, or can't remember anyway | 16:39:32 |
| vaw | Double-puppeting means that the server is using your account for messages you sent instead of a generated account. I think it only matters if you send messages from a signal client. Without double-puppeting, the bridge would create a ghost user for you and send the message from that account in the matrix chat. With double-puppeting the bridge logs into your matrix account and sends the message from there. In this case the message appears to be sent from your account on both platforms. | 17:09:15 |
| wreck | ah, so without double puppetting, if you send a message from another signal app you're logged into, the matrix version of the room makes it look like that's another participant | 17:12:02 |
