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
Is your feature request related to a problem? Please describe.
Technically a problem, but it would be nice to have Pluralkit support set up on this platform. Currently, those with Pluralkit characters get their messages sent twice instead of simply the proxied message.
Describe the solution you'd like
I have a community that makes heavy use of Pluralkit and it would be nice to have Pluralkit proxied messages to be properly covered. This was implemented in that feature request for that bridging software, here and so it should be possible to integrate such support?
Describe alternatives you've considered
Prior to being recommended to use this platform for bridging multiple instances, I was using aronson's discord-irc for bridging Discord to IRC and now am using Matterbridge to bridge not only Discord, but also Telegram to IRC.
Additional context
None needed.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Technically a problem, but it would be nice to have Pluralkit support set up on this platform. Currently, those with Pluralkit characters get their messages sent twice instead of simply the proxied message.
Describe the solution you'd like
I have a community that makes heavy use of Pluralkit and it would be nice to have Pluralkit proxied messages to be properly covered. This was implemented in that feature request for that bridging software, here and so it should be possible to integrate such support?
Describe alternatives you've considered
Prior to being recommended to use this platform for bridging multiple instances, I was using aronson's discord-irc for bridging Discord to IRC and now am using Matterbridge to bridge not only Discord, but also Telegram to IRC.
Additional context
None needed.
The text was updated successfully, but these errors were encountered: