Before submitting I have:

• Made sure this is actual unintended behaviour.
• Double checked !help <command name> (if this is command related) for potential misunderstandings.

Describe the bug
Not strictly related to the bot, but visiting http://trixiebot.com on Firefox 77 or Chromium 81 will cause the URL bar to turn into this, while displaying an empty page:

This doesn't occur when browsing https://trixiebot.com.

To Reproduce
Visit http://trixiebot.com (not https://trixiebot.com, which works correctly).

Expected behavior
http://trixiebot.com should redirect to https://trixiebot.com.

Before submitting I have:

• [ ] Checked !help <command name> (if this is command related) to make sure my question is not answered there N/A
• Checked the README.md
• Checked the site https://trixiebot.com

Question:

What are some examples of public servers using TrixieBot? I'd just like to try out what I can do with her as a user, but I didn't find any list of public Discord servers I could join to meet her (it?).

As a follow up, I guess such a list could also be added the README.md or the website.

Before submitting I have:

• Made sure this is actual unintended behaviour.
• Double checked !help <command name> (if this is command related) for potential misunderstandings.

Describe the bug
Someone in a server said lone pone, which triggered trixiebot to post an image, however bot didn't have Attach Files permission in that channel and ran into an issue.

To Reproduce

1. Make a channel, where bot doesn't haveAttach Files permission.
2. Send lone pone.

Expected behavior
Handle this edge case properly and check for permissions (and don't try to send a message) instead of catching an error...

Additional context
https://i.nuuls.com/T12TG.jpeg

Before submitting I have
(Simply replace the space inside the brackets with an X for the things you have done)

• Double checked existing Issues/Pull Requests for a similar feature.

Describe what you would like us to add
Add a self analysis register that analyses guilds for permission conflicts, etc. on demand through a command or the web dashboard. This would be useful for server owners to find out why a feature isn't working as intended or to help set up Trixie properly when she joins the server.

Describe the change you would like to see
Adding "feature sets" - essentially groups of commands, keywords, behaviours that can easily be integrated and disabled.

Why should we change it that way?
Features like the alert system (example above) still send alerts in servers where the "alert" command has been disabled. As well as that, keyword commands still struggle with proper integration into Trixie, because by themselves they just fit nowhere into the commands enable/disable scheme, are difficult to address as they are RegExps instead of unique short strings as is the case with normal commands and require separate Maps and logic in the CommandRegistry, which always bothered me and isn't very elegant.

Before submitting I have
(Simply replace the space inside the brackets with an X for the things you have done)

• [X ] Double checked existing Issues/Pull Requests for a similar feature.

Describe what you would like us to add
I have a calendar of member birthdays I have been manually maintaining. It would be handy to be the birthday command could also be passed a member name and set that member's birthday.

Before submitting I have\

• Double checked existing Issues/Pull Requests for a similar suggestion.

Describe the change you would like to see
Trixie should no longer send duplicate audio packets.

Why should we change it that way?
Discord removed support for sending duplicate audio packets which was useful for reducing packet loss rate and improve audio quality.

Describe the change you would like to see
Slowly migrate the entire project to Typescript. It'll be a lot more code, but it could be worth it.

Why should we change it that way?
Migrating from Discord.js v11 to v12 was a pain. There are probably many changes I simply don't see, with Typescript I could see the changes I need to make instead of guessing.

After half a year, Discord still hasn't approved Trixie for use in more than 100 servers and priviledged intents, like server members and presence. Maybe I have gotten an email from a developer, I'm sure it landed in the spam folder and has already been automatically removed and now Trixie is in the limbo of "awaiting approval" and there's no UI way to abort and request another review so I'll probably have to hit up the support.

However I won't do so yet, because she's just that much broken right now and I'm still working on the API and website rewrite. Once that's done I can request another approval.

So until then no one can add Trixie to their server... which sucks, but there's no other way. I'm trying to get this dealt with asap.

Before submitting I have
(Simply replace the space inside the brackets with an X for the things you have done)

• Double checked existing Issues/Pull Requests for a similar feature.

Describe what you would like us to add
Add configuration functionality of server timezones and date and time formatting. Make these configurations accessible to Resolvables, especially to new classes for formatting dates and times.

Before submitting I have

• Double checked existing Issues/Pull Requests for a similar suggestion.

Describe the change you would like to see
From what I've checked, there's no way to disable that keyword in a config and disabling it can be actually useful.

Why should we change it that way?
Not everyone wants to have their channels clogged with images while having a conversation, especially when there's no cooldown or anything which would prevent bot from being spammy. Most of the members/bots are not allowed to post images anyway and we want it to stay that way.

Additional context
Kinda offtopic, but you seem to have an unnecessary \ in your issue templates (near the checklist).

Before submitting I have

• Double checked existing Issues/Pull Requests for a similar suggestion.

Describe the change you would like to see
Rewrite i18n stuff to supply a more universal and cleaner approach to translating TrixieBot.

Why should we change it that way?
Currently i18n required manipulation of built-in discord.js class prototypes, adding properties to discord.js Objects and having the translation phrases in the code be exactly the same as in the translations, which reduced readibility of the locale files, increased junk and didn't make it clear what is translatable and what is not.