@tulir any suggestions？

That user_id field in the logs is suspicious, did you modify the bridge somehow?

That user_id field in the logs is suspicious, did you modify the bridge somehow?

I didn't make any changes. I used the login interface in Provisioning.go, and I noticed that it includes the user interface_ The ID reading is obtained from the URL query parameter, which can be specified directly. I then specified and called the login interface.

The user ID parameter must be a mxid. You also can't log into the same meta account with multiple matrix users.

• 39748d31 Update proxy on reconnect

• 96b28b9d Add more protobufs
• b5d916d3 Extract protobufs from js

• 51258efe Undo replace in go.mod
• 03a71872 Move armadillo protobufs to whatsmeow

• 8113f790 Update whatsmeow

Could this be related to the E2E enabled on chats by default now? Ever since this feature was deployed, my Facebook bridge works only for group chats, I can't receive nor send messages to private chats that have E2E enabled.

No, this is some MQTT weirdness, only affects the new bridge, and hasn't been reported by anyone else than @NicolasDerumigny

You're right, the error message for E2E chats is "this thread is disabled".

I've had this MQTT weirdness happen sometimes on my bridge but it was just momentarily and as soon as it happened it fixed itself by sending another message.

• b0c31b1e Only enable e2ee on messenger for now
• 962f25e3 Move whatsmeow client management to bridge side
• a542cc46 Store whatsapp server for puppets and portals