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

Discord Matterbridge Use Channel ID Instead of Channel Name #13877

Closed
Fibbicles opened this issue Nov 27, 2024 · 2 comments · Fixed by #13936
Closed

Discord Matterbridge Use Channel ID Instead of Channel Name #13877

Fibbicles opened this issue Nov 27, 2024 · 2 comments · Fixed by #13936

Comments

@Fibbicles
Copy link

How to use GitHub

  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

Which Nextcloud Version are you currently using: Hub 9 (30.0.2)

Is your feature request related to a problem? Please describe.
Essentially we can only identify Discord channels by name, this leads to many problems for users of most Discord servers where unicode symbols and emojis are used within the text names. Also mentioned here: nextcloud/talk_matterbridge#71

Describe the solution you'd like
We can specify the Server ID as an integer like 1187942610669686868 and should be able to do the same with channel ids rather than specifying the name.

Describe alternatives you've considered
None because there's no alternatives.

Additional context
This has been a problem for almost 2-3 years now since it was reported and seems like a very quick and simple fix.

@nickvergessen
Copy link
Member

Specifying ID:1234567890 should work
https://github.com/42wim/matterbridge/wiki/How-to-create-your-config#step-5

@Antreesy
Copy link
Contributor

Antreesy commented Dec 4, 2024

Tested and confirmed with using channel name general or ID:12345

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants