Great. Btw I will gladly consider any useful generic improvements to this plugin in case you decide to get coding again 
Okay let’s start slow. I just submitted my first pull request to this repo
.
https://github.com/merefield/discourse-discord-bot/pull/3
merged
thanks!
Hey! I’ve been trying to find a plugin that will give users in Discord a role based on the badges they have on their Discourse profile. Is this possible with your plugin? If not, is it even possible? Thanks!
Not at present but no reason why you couldn’t fork it and add an appropriate command to implement that!
If implemented well I would consider merging a PR. However it might be a little specific for general use because presumably you’d have to maintain some kind of mapping unless the badge names were same as role names? In any case you’d have to filter out most of them? That might get messy for general use. If you find a really clean way to manage that which would work for general users of the plugin let me know.
But fork away, fill your boots!
I would definitely like to see if it is possible. That would make me even more interested in this plugin. 
Just a small question: do we have to manually run !discsync every time we want to update roles, or is it automatic?
Unfortunately yes. It might be a nice enhancement to add a ‘repeat in x hours’ parameter (PR welcome or hire me to implement), but as I’ve mentioned before in this Topic, it would be better if someone produced a new plugin using their API and created some scheduled sidekiq jobs to do that. A bot is a fun solution but not the best architecture for scheduled syncing.
Oh, thanks anyway. Yeah, we have already thought about a possible alternative…
We wanted to sync Discourse groups with Discord roles, but it looks like there is no perfect solution that suits.
We are now going to make some kind of bot using webhooks: Discourse will trigger a webhook when an user’s groups is updated (or username change as well) to a custom solution, which will then assign roles in Discord. We will keep using the Discord OAuth choice in order to get guilds, and by creating a custom Data Explorer query, we can get through the API those guilds.
It would be something like this:
- User changes groups or username
- Webhook to custom solution is triggered
- This custom solution will call back to Data Explorer API to a custom query that returns the guilds from the user
- With that guild, we call Discord back to update roles
A proper batch job would be better so you don’t lose data integrity due to one-off event glitches. Both would be perfect.
Well, I didn’t go through that way… ![]()
I’ve forked your repo, and made a new plugin that suited our needs:
It basically syncs all groups with Discord roles, but automatically. When a user is added or removed from a group, it will run a sync job and update their roles according to the public groups. In addition, I’ve added a setting to mark a “verified role”, that will be added to all users who have a Discourse account. And also it supports adding a list of safe roles, which the bot will ignore when syncing users (useful, for example, if wanting to set different admins and mods in the server than in the forum).
I’ve also added a username-nickname syncer. It can enforce users to have the same server nickname as the forum username.
I’ll open a plugin topic after cleaning up a couple of things, as maybe someone can find it useful.
@barreeeiroo what was really interesting about your fork was your leveraging of DiscourseEvents hooks.
I had assumed that wasn’t possible because the bot is running in a separate thread. But as you’ve discovered, it seems we can act on events and influence the bot. So thanks for that, that’s a really important insight we can develop going forward.
So I’ve started adopting that technique in the main repo, starting with the ability to set some watches on new posts or Topics that willl be announced in the admin channel of Discord.
https://github.com/merefield/discourse-discord-bot/commit/9f8498c6a56baebb4d21009dff57932b35a46b86
The functionality may be of little use as it currently stands but it demostrates the concept for others to leverage.
OK I’ve developed the plugin a little further now and have POC for two way communication working:
Here are the new settings

-
You can designate an Announcements Channel on Discord in the plugin settings.
-
You can now type into the assigned Discord Announcements Channel and this will post your message to your assigned Discourse Topic in the plugin settings
-
You can set up a list of Categories in Discourse to post to the Announcements channel on your Discord if someone Posts there or adds a new Topic (either or both).
https://github.com/merefield/discourse-discord-bot/commit/a19aa35f6aab2504aa220a1ab3856475f27c795a
In addition I’ve added a new file to manage Discord events supported by the discordrb API, with Announcements logic being the first example (feel free to develop new ones and PR if of general use to the community).
I’ve also removed the changes required to app.yml to install libsodium-dev as this is now optional having updated the dependencies and not required for the plugin at present (no need to handle voice). This will make installation much simpler.
马克,抱歉,我不知怎么错过了这个。
你找到问题了吗?
请更新并尝试新版本,然后我们再继续。
Discourse 团队资助的重要更新 ![]()
-
新增命令
!disccopy <消息数量> <可选目标分类名称> <可选目标主题名称>,允许您在 Discord 聊天中将 Discord 消息历史记录(在该频道中)复制到您的 Discourse 实例。这可以安全地一次性处理数千条消息(但对于如此大的数量将需要一些时间)。 -
自动按频道进行每条消息的聊天复制,复制到 Discourse 中任何同名的分类:如果频道名称与分类名称匹配,并且启用了此功能,它将把消息复制到 Discourse 中:

-
对于任何从 Discord 复制到 Discourse 的消息,用户现在将正确显示,前提是该用户已通过 Discord 登录到 Discourse(因此 Discord Bot 能够匹配用户帐户)。
-
为许多功能添加了本地化支持。
感谢 @erlend_sh 和 Discourse 团队对这项工作的规范和赞助!! ![]()
更多机器人功能即将推出
![]()
如果他们使用 Discourse 身份验证或 Discord OAuth 以外的任何身份验证登录,此插件是否会忽略他们?
它没有忽略它们,只是无法在另一个系统上将用户与该人匹配。因此,复制的消息将显示为来自“系统”。
是否支持线程?
还没有,克劳斯,但有可能在计划中。等待 Ruby API 更新(阻塞),然后等待支持者添加该功能。

