kazwolfe / huskybot Goto Github PK

Similar to #8 if you add a ‘./‘ to the middle of the url it still works as in #8 and Huskey doesn’t see it

Example https://discord.gg/./sv8yMF

If I change my username to the format <@{user_id_here}> I can get huskey to mention people

General epic project to make the documentation for HuskyBot overall better.

Subcomponents:

• Fix and standardize builtin help documentation (and probably the command)
• Fix up the readme file overall, make it cleaner. Likely remove support for certain methods of running the bot.
• Start actually documenting things in the wiki as well. This will be important as the HuskyBot API matures.

After adding a new role, I tried running rpromote add which crashed the bot after it adding the emote to the specified message. After the bot rebooted, clicking on any of the reactions—not just the one created immediately before—causes the bot to crash without assigning or unassigning the role. Removing the reaction with rpromote remove crashes the bot as well, after it removes the emote. It seems like the problem may be with reactions in general, since running /debug react causes the bot to crash after it adds a reaction to any given message.

/admin logs doesn't record a reason for the crash.

At Kaz's suggestion I'm opening an issue regarding adding RSS capability to HuskyBot. And since I'm doing that, I may as well enumerate some other feature requests. Items presented in no particular order, just skimming the stream of consciousness.

1. RSS – Feature would ideally periodically check RSS sources for new content and then post what's found to a designated channel. At least fifteen sources would be required for NHC products, more would be handy for blog posts we monitor through IFTTT and Zapier.

2. Twitter – New tweets from selected accounts posted in specified channels.

3. Reddit – Links to new threads posted to subreddits would be placed in designated channels.

One of the core features of this bot should be the ability to allow users to grant themselves certain roles by using message reactions.

Users should:

• Only be permitted to do this in a single (configurable) channel
• Only be granted roles upon reacting to a message with a specific emoji
• Lose the role after removing their reaction to the message

To keep things clean, users should be allowed to promote one of a few selected emojis to a message.

The config of this feature should be in the following format:

    "promotions": {
        "11223344": {
            "thinking": "22112211"
        }
    }

In the above example, reacting with :thinking: to message ID 11223344 will grant you role 22112211.

If you modify the invite url by adding an extra “/“ in the middle, the url still works but Huskey doesn’t stop it.

Example https://discord.gg//diytech