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

Create bridge from Telegram to Discord #770

Open
yaroslavyaroslav opened this issue Feb 9, 2023 · 0 comments
Open

Create bridge from Telegram to Discord #770

yaroslavyaroslav opened this issue Feb 9, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@yaroslavyaroslav
Copy link
Collaborator

What context is your feature request related to?

Currently there's two places where ppl can get support for Web3Swift. It's Discord and it's Telegram. So the latter is actually pretty dead yet, as none of active maintainers are there, but some users are suddenly coming there and trying to reach a help.

What solution would you like?

As long as the option to close Telegram channel is unavailable for us, it's worth to add some message bridging bot from Telegram to Discord.

The flow is:

  1. Some one publish a message in tlg
  2. Bot repeats it in Discord in let's say support channel.
  3. Someone answers that message (by selecting it and pressing answer) in Discord
  4. Bot repeats that message in tlg as an answer for the original message, so user asked it got notified about the answer.

Any additional context?

There's such Opensource project as rizin that is in the same situation as we are. It has 2 channels of providing support: Mattermost and Telegram. And they have a message bridging from tlg to matter back and forth. I think this is a good example how this work around could be managed.

@yaroslavyaroslav yaroslavyaroslav added the enhancement New feature or request label Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant