Great. Btw I will gladly consider any useful generic improvements to this plugin in case you decide to get coding again 
2 curtidas
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 curtidas
merged 
thanks!
4 curtidas
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 curtidas
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 curtidas
I would definitely like to see if it is possible. That would make me even more interested in this plugin. 
1 curtida
Just a small question: do we have to manually run !discsync every time we want to update roles, or is it automatic?
2 curtidas
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 curtidas
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 curtidas
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 curtidas
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 curtidas
@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 curtidas
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 curtidas
Segui as instruções de instalação e tudo correu bem até a reinicialização. O bot não entrou na sala, então verifiquei /logs:
Isso está se referindo ao discord_bot_token? Ele está preenchido e verifiquei o valor. Alguma pista?
3 curtidas
Mark, desculpe, de alguma forma perdi isso.
Você descobriu o problema?
Você pode, por favor, atualizar e tentar a nova versão e seguiremos a partir daí.
2 curtidas
Uma atualização significativa financiada pela equipe do Discourse 
-
Um novo comando
!disccopy <número-de-mensagens> <nome-opcional-da-categoria-de-destino> <nome-opcional-do-tópico-de-destino>que permite copiar o histórico de mensagens do Discord (nesse canal) para sua instância do Discourse a partir do chat do Discord. Isso pode lidar com segurança com milhares de mensagens de uma vez (mas para esse volume levará tempo). -
Cópia automática de chat por mensagem, por canal para qualquer Categoria com o mesmo nome no Discourse: se o nome do canal corresponder ao nome da Categoria, ele copiará a mensagem para o Discourse se isso estiver configurado:
-
Para qualquer mensagem copiada para o Discourse do Discord, o Usuário agora será exibido corretamente se esse usuário fez login no Discourse usando o login do Discord (Assim, o Discord Bot é capaz de corresponder às contas de usuário).
-
Suporte de localização adicionado para muitos recursos.
Obrigado a @erlend_sh e à equipe do Discourse por especificarem e patrocinarem este trabalho!! 
Mais coisas de bot virão 
5 curtidas
Se eles fizerem login com autenticação do Discourse ou qualquer autenticação diferente do OAuth do Discord, este plugin simplesmente os ignorará?
1 curtida
Não os ignora, apenas não consegue corresponder o usuário com a pessoa no outro sistema. Como resultado, as mensagens copiadas aparecerão como vindas do “sistema”.
2 curtidas
Threads são suportados?
4 curtidas
Ainda não, Klaus, mas é potencialmente algo que está em desenvolvimento. Estamos aguardando a atualização da API Ruby (bloqueador) e, em seguida, um patrocinador para adicionar esse recurso.
2 curtidas