Third party Discord servers such as https://gitlab.com/litecord/litecord and https://github.com/fosscord/fosscord exist. It would be great to be able to use this bot with those third party servers.

To Reproduce Steps to reproduce the behavior:

1. Fire up the bot
2. Then on Disocrd/Matrix type ;mute @ UserExample (must be an admin)
3. See error

Logs

/home/tuckerj/Documents/graim/node_modules/discord.js/src/rest/RequestHandler.js:350
throw new DiscordAPIError(data, res.status, request);
^

DiscordAPIError: Missing Permissions
at RequestHandler.execute (/home/tuckerj/Documents/graim/node_modules/discord.js/src/rest/RequestHandler.js:350:13)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async RequestHandler.push (/home/tuckerj/Documents/graim/node_modules/discord.js/src/rest/RequestHandler.js:51:14)
at async GuildMemberRoleManager.add (/home/tuckerj/Documents/graim/node_modules/discord.js/src/managers/GuildMemberRoleManager.js:124:7) {
method: 'put',
path: '/guilds/968319055717085184/members/818995901791207454/roles/969439573912453120',
code: 50013,
httpStatus: 403,
requestData: { json: undefined, files: [] }
}

Desktop (please complete the following information):

• Node.js v18.0

Additional context Add any other context about the problem here.

Describe the bug You can use markdown to make links look different than they are. This could be a security issue. Ex: [https://www.google.com](this could link to a phishing page)

To Reproduce Steps to reproduce the behavior:

1. Go to any room that is bridged.
2. Do the markdown magic(e.g., https://github.com/)

Expected behavior Graim should delete message or there should be a config option to auto-delete these messages.

I also added a docker file in the website for ease of use. It can be used with Github pages however, since it is completely static. The Documentation Website Should be more user friendly. The website is built an generated using Hugo. The whole thing is untouched but the "docs" folder. A live version of this website can be seen at: https://graimdocs.motortruck1221.tech

Hi.

This is a command for identifying a matrix user's MXID from their display name. Since the Discord webhook bridge only displays the display name, this could be useful to prevent impersonation.

Also included in this commit was a little optimization in lookupUser. Not sure if there is any reason to having the order execute like that, but if there is this probably broke something. Seems fine from my manual tests though.

Basically, just a feature within the bot which will check all of the configurations for the Discord server, Matrix rooms, and bot, to ensure that everything is correctly set up. This would allow people to much more quickly figure out exactly what they need to do.

Reqs

• Error if not capable of role mgmt, kick, ban, mute on Discord
• Warn if no moderator in graimdb.json
• Warn if power level is not high enough to kick/ban/mod powerlevels in n room
• Warn if autojoin is on in config
• Warn for rooms not bridged directly to channel via graimdb
• Warn if no channel mgmt permissions on Discord
• Info if no logging room set

Some things are probably missing from this list, but that's the general idea. None of these will cause fatal errors in graim itself, but they WILL cause graim to not work.

Most extensive moderation bots will have a room in which it logs all moderation actions (i.e.: kicks, mutes, strikes, bans). This makes it much, much easier to keep track of moderation that a team is doing, as well as keeps a significantly more reliable and accessible log than Discord's audit log. The reason I didn't think to implement this already, is because Matrix already logs all moderation events right in chat - but this absolutely is a must-have feature for large moderation teams

Would change room/channel settings, preventing users from speaking.

Primarily, this would be a challenge due to its existence on both Discord and Matrix side. I don't want to have to implement another part of the database where entries must be manually considered, so I am thinking about it.

My best idea so far - verbosity in syntax. User is expected to write ;lock <discord channel>, to lock whatever room the message was sent in on Matrix, and the room specified.

The main issue is that this is not good on the M=>D side of things, because they are unable to specify a specific channel.

This is a logic thing, for the most part, and I will update the issue as progress moves forward

Describe the bug The deleteuser command does not actually remove the user from the database

To Reproduce Steps to reproduce the behavior:

1. Run deleteuser <graim_name>
2. See the success message
3. Run userinfo <graim_name>
4. See the user is not deleted

Expected behavior No user in db

Logs N/A

Desktop (please complete the following information):

• Node.js version 18

Additional context N/A

Describe the bug When you run unban on a banned user bridged from Discord to Matrix, the unban doesn't go through on the Discord end.

To Reproduce Steps to reproduce the behavior:

1. Run ;unban on user that already is banned
2. Note that the user is not unbanned on Discord

Expected behavior User is unbanned from both Matrix and Discord

Logs N/A

Desktop (please complete the following information):

• Node.js version - 18

Additional context It makes sense that it didn't work, because I have done minimal testing on the ban and unban commands (Discord banned my testing accounts from the platform for suspicious activity).

To Reproduce Steps to reproduce the behavior:

1. run graim @ latest
2. ;mute
3. crash

Logs

/home/hi/graim/node_modules/ms/index.js:33                                                                                throw new Error(                                                                                                              ^                                                                                                                                                                                                                                       Error: val is not a non-empty string or a valid number. val=undefined                                                       at module.exports (/home/hi/graim/node_modules/ms/index.js:33:9)                                                        at /home/hi/graim/lib/commands/mute.js:52:26                                                                            at Generator.next (<anonymous>)                                                                                         at /home/hi/graim/lib/commands/mute.js:8:71                                                                             at new Promise (<anonymous>)                                                                                            at __awaiter (/home/hi/graim/lib/commands/mute.js:4:12)                                                                 at runMuteCommand (/home/hi/graim/lib/commands/mute.js:22:12)                                                           at CommandHandler.<anonymous> (/home/hi/graim/lib/commands/handler.js:103:51)                                           at Generator.next (<anonymous>)                                                                                         at /home/hi/graim/lib/commands/handler.js:8:71 

Desktop (please complete the following information):

• Node.js version

Additional context the issue is that I had assumed ms was okay with undefined i.e. bad data, and simply returned 0 (as it does for other strings). however, if there is NO argument, undefined is passed, which crashes ms.

This feature would simply catch any messages that include content which is specified by the moderators (regex, i'm thinking). That way, you could auto moderate things like slurs, spam, or whatever else you'd like

graim currently essentially ALWAYS tells you that the operation was completed successfully. While this is fine 90% of the time (usually, any non-fatal errors are not really errors but simply non-issues), I think it would be a lot more useful for the bot to at least warn you in the situation that something has gone wrong partially.

For example - when a user is banned, graim will attempt to ban them from discord and matrix. As long as the command isn't improperly formatted, graim ALWAYS responds with a success - even if there was not actually a success in the action. For example, if graim's power level isn't high enough in every room, then it will not be able to ban the user - however, there is no way for the end user to know the interaction failed, without logging on Matrix themselves and seeing the ban event in the log.

Mostly I am using this issue to track a long-term implementation of more reception from graim, because this is a big design issue that I am currently completely ignoring. First, I need to figure exactly how I want output to show (should I log in every room/channel individually that it failed in? Should I print out another message after the ban success showing any warns?)

Any outsider input is greatly appreciated!

I am going to be tracking this development in the commit names, so it should be easy to follow progress on this specific development.

I think a good feature to implement to graim would be purging by user/graim user. this is a pretty common feature of moderation bots and is super super useful in the event of, say, a raider. with one command you can then delete ALL of one user's messages