Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(replies): fix replies from Status and to Status messages #18

Merged
merged 1 commit into from
Sep 14, 2024

Conversation

jrainville
Copy link
Member

Needed for status-im/status-desktop#16323

There were multiple problems.

  1. The ParentID was not set correctly when a message was sent from Status
  2. We didn't send back the ID of messages that we sent, so the gateway couldn't associate the new messages to the old ones
  3. Missing param in the toml config PreserveThreading
  4. Discord messages are weirdly formatted when a reply is send. It cannot use webhooks, so we need to pass the username directly in the message (it's ugly, but it works)

Finally, there was an issue on the status-go side. We tried to use the discord message ID to find the replies, but the bridge already converts it to the right ID, so we could just use it directly

How it looks in Status:
image

How it looks in Discord:
image

They all work now. The only sad thing is replies from Status look a bit ugly in Discord, but that's a limitation in the Discord API I think.

Needed for status-im/status-desktop#16323

There were multiple problems.

1. The ParentID was not set correctly when a message was sent from Status
2. We didn't send back the ID of messages that we sent, so the gateway couldn't associate the new messages to the old ones
3. Missing param in the toml config `PreserveThreading`
4. Discord messages are weirdly formatted when a reply is send. It cannot use webhooks, so we need to pass the username directly in the message (it's ugly, but it works)

Finally, there was an issue on the status-go side. We tried to use the discord message ID to find the replies, but the bridge already converts it to the right ID, so we could just use it directly
@jrainville
Copy link
Member Author

status-go PR status-im/status-go#5830

@siddarthkay
Copy link

nice @jrainville : once the status-go PR is merged and cherry picked on release 2.30 branch we could use this PR to update the status-go version as well.

@jrainville
Copy link
Member Author

nice @jrainville : once the status-go PR is merged and cherry picked on release 2.30 branch we could use this PR to update the status-go version as well.

Yeah we could. Though as far as I understand, the status-go changes are mostly useful for actual users receiving messages, so we'll need for 2.31 to have the real fix in the hands of users

@siddarthkay
Copy link

@jrainville : ah thanks for explaining!

@siddarthkay siddarthkay merged commit e11feb1 into wakuv2 Sep 14, 2024
4 checks passed
@siddarthkay siddarthkay deleted the fix/replies branch September 14, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants