Thomas Loupe

I had to take some time to think about this request as there is a good case for cleaning up the timestamps in general. One change was already done to...

Okay, I'll consider this and make a decision. More than likely there's no issue with doing the latter of the two so I may just do so.

The latest Windows release now has cleaner timestamps. Messages are a bit more clean now, too. See the latest Windows [release](https://github.com/thomasloupe/Slackord2/releases/tag/v2.3) (Linux/Mac coming soon).

This feature has been completed and released for all releases of Slackord2. See the latest release [here](https://github.com/thomasloupe/Slackord2/releases/tag/v2.3).

The message should have been split up, as this functionality is already included. Would you be willing to shoot me the JSON file for testing so I can hotfix this?...

This bug should be fixed in https://github.com/thomasloupe/Slackord2/releases/tag/v2.4! Please feel free to re-open this issue if you encounter it again.

Hello! This usually means your connection is unstable. I believe I can defer the task to post messages so that it doesn't do this.

This issue exists because I am not using DeferAsync/FollowupAsync in the responses. When a user invokes the /Slackord slash command, commands must be executed within 3 seconds and an acknowledgement...

I will still be adding code to remedy this, but this is intended behavior of the Discord.NET lib and Discord. Removed the bug label, since this really isn't a bug.

Specifically, I don't have the time right now to get it done programmatically. It will be some time before I can get this implemented.