Discord Bot Bausatz đŸ€–

Plugin
67

Great. Btw I will gladly consider any useful generic improvements to this plugin in case you decide to get coding again :wink:

2 „GefĂ€llt mir“
68

Okay let’s start slow. I just submitted my first pull request to this repo :smile:.
https://github.com/merefield/discourse-discord-bot/pull/3

4 „GefĂ€llt mir“
69

merged :slight_smile: danke!

4 „GefĂ€llt mir“
70

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 „GefĂ€llt mir“
71

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 „GefĂ€llt mir“
72

I would definitely like to see if it is possible. That would make me even more interested in this plugin. :smiley:

1 „GefĂ€llt mir“
73

Just a small question: do we have to manually run !discsync every time we want to update roles, or is it automatic?

2 „GefĂ€llt mir“
74

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 „GefĂ€llt mir“
75

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:

  1. User changes groups or username
  2. Webhook to custom solution is triggered
  3. This custom solution will call back to Data Explorer API to a custom query that returns the guilds from the user
  4. With that guild, we call Discord back to update roles
2 „GefĂ€llt mir“
76

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 „GefĂ€llt mir“
77

Well, I didn’t go through that way
 :sweat_smile:
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 „GefĂ€llt mir“
78

@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 „GefĂ€llt mir“
79

OK I’ve developed the plugin a little further now and have POC for two way communication working:

Here are the new settings

image

  • 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 „GefĂ€llt mir“
80

Ich habe die Installationsanweisungen befolgt und alles lief reibungslos bis zum Neustart. Der Bot ist dem Raum nicht beigetreten, also habe ich /logs ĂŒberprĂŒft:

image
image789×100 8.56 KB

Bezieht sich das auf den discord_bot_token? Er ist ausgefĂŒllt und ich habe den Wert ĂŒberprĂŒft. Irgendwelche Hinweise?

image
image651×821 29.7 KB

3 „GefĂ€llt mir“
81

Mark, Entschuldigung, das habe ich irgendwie ĂŒbersehen.

Haben Sie das Problem entdeckt?

Können Sie bitte das Update durchfĂŒhren und die neue Version ausprobieren, dann sehen wir weiter.

2 „GefĂ€llt mir“
82

Ein bedeutendes Update, finanziert vom Discourse-Team :tada:

FEATURES: new message auto-copy and history copy command by merefield · Pull Request #4 ·
merefield/discourse-discord-bot (github.com)

  1. Ein neuer Befehl !disccopy \u003cAnzahl der Nachrichten\u003e \u003coptionaler Zielkategorie-Name\u003e \u003coptionaler Zielthema-Name\u003e, mit dem Sie den Discord-Nachrichtenverlauf (in diesem Kanal) von Ihrem Discord-Chat aus in Ihre Discourse-Instanz kopieren können. Dies kann problemlos Tausende von Nachrichten auf einmal verarbeiten (wird aber bei diesem Volumen Zeit in Anspruch nehmen).

  2. Automatisches Kopieren von Chats pro Nachricht, nach Kanal in jede gleichnamige Kategorie auf Discourse: Wenn der Kanalname mit dem Kategorienamen ĂŒbereinstimmt, wird die Nachricht in Discourse kopiert, wenn dies eingestellt ist:
    image

  3. Bei jeder Nachricht, die von Discord in Discourse kopiert wird, wird der Benutzer jetzt korrekt angezeigt, wenn sich dieser Benutzer mit dem Discord-Login bei Discourse angemeldet hat (damit der Discord-Bot die Benutzerkonten abgleichen kann).

  4. LokalisierungsunterstĂŒtzung fĂŒr viele Funktionen hinzugefĂŒgt.

Vielen Dank an @erlend_sh & das Discourse-Team fĂŒr die Spezifikation & das Sponsoring dieser Arbeit!! :pray:

Mehr Bot-Sachen kommen :wink: :robot:

5 „GefĂ€llt mir“
83

Wenn sie sich mit Discourse-Authentifizierung oder einer anderen Authentifizierung als Discord OAuth anmelden, wĂŒrde dieses Plugin sie einfach ignorieren?

1 „GefĂ€llt mir“
84

Ignoriert sie nicht, es kann den Benutzer nur nicht mit der Person im anderen System abgleichen. Daher erscheinen kopierte Nachrichten von „System“.

2 „GefĂ€llt mir“
86

Werden Threads unterstĂŒtzt?

4 „GefĂ€llt mir“
87

Noch nicht, Klaus, aber es ist potenziell in der Pipeline. Wir warten auf die Aktualisierung der Ruby-API (Blocker) und dann darauf, dass ein Backer diese Funktion hinzufĂŒgt.

2 „GefĂ€llt mir“