You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Some one publish a message in tlg
Bot repeats it in Discord in let's say support channel.
Someone answers that message (by selecting it and pressing answer) in Discord
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.
The text was updated successfully, but these errors were encountered:
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:
support
channel.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.
The text was updated successfully, but these errors were encountered: