Malte E
Malte E
Since leaving the Telegram chat caused inconsistencies, I think that the solution should be to bridge the leave from Telegram to matrix (via double puppeting). Alternatively, the relaybot could re-invite...
I can't reproduce this with latest mautrix-signal
Leaving a room should be bridged to signal, so I would consider this fixed
This would break with multiple platform bridged to the same room.
I can confirm that this bug affects the pgfplotsx backend as well
I have no intention to implement that, but if anyone else does, checking the protobuf part: https://github.com/mautrix/signal/blob/main/pkg/signalmeow/protobuf/SignalService.proto#L52 and looking for where this one is referenced: https://github.com/signalapp/Signal-Android/blob/main/libsignal-service/src/main/java/org/whispersystems/signalservice/api/messages/SignalServiceStoryMessage.java is probably a good...
I suppose it would be fine to not overwrite a `restricted` join rule if the signal group allows join by invite link without admin approval, as well as `knock_restricted` if...
This is probably unrelated to the bridge and should be filed with Signal-cli
Formatting works with this
depends on https://github.com/mautrix/go/pull/208