search

mautrix / slack

A Matrix-Slack puppeting bridge
GNU Affero General Public License v3.0
61 stars 17 forks source link

working backfill for channels, thread messages working but relations … #49

Closed pinnymz closed 2 months ago

pinnymz commented 4 months ago

…need some work

pinnymz commented 4 months ago

WIP, for collaboration

niebloomj commented 4 months ago

What do you mean by "relations" need work? Also for those not following the related conversation about this, here is an issue we currently have with this code. https://matrix.to/#/!mautrix-slack-v9:maunium.net/$H6vxIcoyST_PtucRZD7QlOftC2-pbx7jL_L3GqQgFX4?via=maunium.net&via=matrix.org&via=beeper.com

pinnymz commented 4 months ago

The threaded messages seem to be related properly to the original message in the mautrix-slack DB, but I'm not confident they are being related properly within dendrite DB. It's possible the payload when submitting the event needs to be refined further.

niebloomj commented 4 months ago

Linking the issue we are trying to solve here https://github.com/mautrix/slack/issues/47

pinnymz commented 4 months ago

IM messages are still failing with a 403 when attempting to have a user (logged-in user? bot-user?) invite/join the room so that the message can be sent on their behalf. Specifically, this error is being triggered in the intent EnsureJoined() method: https://github.com/mautrix/go/blob/master/appservice/intent.go#L118

        if inviteErr != nil {
            return fmt.Errorf("failed to invite in ensure joined: %w", inviteErr)
        }
pinnymz commented 4 months ago

It would help if there were some reference that explained the flow and modeling for the role of the bridge with IM rooms.

niebloomj commented 4 months ago

I pulled this into my production env and it worked incredibly well!

tulir commented 2 months ago

Backfilling will be redone in the refactor