Great. Btw I will gladly consider any useful generic improvements to this plugin in case you decide to get coding again 
2 « J'aime »
Okay letâs start slow. I just submitted my first pull request to this repo 
.
https://github.com/merefield/discourse-discord-bot/pull/3
4 « J'aime »
merged 
thanks!
4 « J'aime »
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!
2 « J'aime »
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!
2 « J'aime »
I would definitely like to see if it is possible. That would make me even more interested in this plugin. 
1 « J'aime »
Just a small question: do we have to manually run !discsync every time we want to update roles, or is it automatic?
2 « J'aime »
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.
2 « J'aime »
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
2 « J'aime »
A proper batch job would be better so you donât lose data integrity due to one-off event glitches. Both would be perfect.
2 « J'aime »
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.
7 « J'aime »
@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.
5 « J'aime »
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.
9 « J'aime »
Jâai suivi les instructions dâinstallation et tout sâest dĂ©roulĂ© sans problĂšme jusquâau redĂ©marrage. Le bot nâa pas rejoint la salle, jâai donc vĂ©rifiĂ© /logs :
Cela fait-il rĂ©fĂ©rence au discord_bot_token ? Il est renseignĂ© et jâai vĂ©rifiĂ© la valeur. Des pistes ?
3 « J'aime »
Mark, dĂ©solĂ©, jâai ratĂ© ça.\n\nAvez-vous dĂ©couvert le problĂšme ?\n\nPouvez-vous sâil vous plaĂźt mettre Ă jour et essayer la nouvelle version et nous aviserons ensuite.
2 « J'aime »
Une mise Ă jour importante financĂ©e par lâĂ©quipe Discourse 
-
Une nouvelle commande
!disccopy <nombre-de-messages> <nom-de-catĂ©gorie-cible-optionnel> <nom-de-sujet-cible-optionnel>qui vous permet de copier lâhistorique des messages Discord (dans ce canal) vers votre instance Discourse depuis le chat Discord. Cela peut gĂ©rer en toute sĂ©curitĂ© des milliers de messages en une seule fois (mais pour ce volume, cela prendra du temps). -
Copie automatique de chat par message, par canal vers toute Catégorie de nom identique sur Discourse : si le nom du canal correspond au nom de la Catégorie, il copiera le message dans Discourse si ceci est activé :
-
Pour tout message copiĂ© dans Discourse depuis Discord, lâUtilisateur sâaffichera dĂ©sormais correctement si cet utilisateur sâest connectĂ© Ă Discourse en utilisant la connexion Discord (le Bot Discord est ainsi capable de faire correspondre les comptes utilisateurs).
-
Prise en charge de la localisation ajoutée pour de nombreuses fonctionnalités.
Merci Ă @erlend_sh & lâĂ©quipe Discourse dâavoir spĂ©cifiĂ© et sponsorisĂ© ce travail !! 
Plus de choses pour le bot Ă venir 
5 « J'aime »
Sâils se connectent avec lâauthentification Discourse ou toute authentification autre que lâauthentification OAuth Discord, ce plugin les ignorera-t-il simplement ?
1 « J'aime »
Il ne les ignore pas, il est juste incapable de faire correspondre lâutilisateur avec la personne sur lâautre systĂšme. Par consĂ©quent, les messages copiĂ©s sembleront provenir du « systĂšme »
2 « J'aime »
Les threads sont-ils pris en charge ?
4 « J'aime »
Pas encore, Klaus, mais câest potentiellement en cours. En attente de la mise Ă jour de lâAPI Ruby (bloqueur), puis dâun sponsor pour ajouter cette fonctionnalitĂ©.
2 « J'aime »