Since I already use it in so many other projects, I will probably leverage mongoDB and mongoose.

Depends on #24

https://dev.twitch.tv/docs/api/reference/#modify-channel-information

When we suspect the output of a command (i.e. !commands) is going to be longer than the maximum message allowed by Twitch, we should split up the output and send it over several messages.

https://dev.twitch.tv/docs/api/reference#get-chatters

change the filter of your camera based on this command for a certain time. add a big cooldown to it
!filter [name: string]
!filterlist - sends the list of available filters

    add a song request with channel points, it will submit it to a queue Spotify will play

Originally posted by @JumpyLionnn in #15 (comment)

https://dev.twitch.tv/docs/api/reference/#modify-channel-information

Filter out any command that has a mustBeUser property

Probably want to make it work with lastfm, or Spotify directly

Use the scope user-read-currently-playing while following the guide https://developer.spotify.com/documentation/general/guides/authorization/code-flow/

make cool effects with alerts on stream. for example some party particles when there is a raid

Roll a die basically. Should accept parameters min max with default of min = 1 and max = 6

Instead of simply opening a webpage to the new issue form

https://docs.github.com/en/rest/issues/issues?apiVersion=2022-11-28#create-an-issue

Should return a random issue's title from GitHub

Example:

!randomissue
Here's a random issue: ${issueTitle}

In this example taken from Twitch docs, we see a channel.subscription.end event. The subscription object contains the type property "channel.subscription.end":

{
    "subscription": {
        "id": "f1c2a387-161a-49f9-a165-0f21d7a4e1c4",
        "type": "channel.subscription.end",
        "version": "1",
        "status": "enabled",
        "cost": 0,
        "condition": {
           "broadcaster_user_id": "1337"
        },
         "transport": {
            "method": "webhook",
            "callback": "https://example.com/webhooks/callback"
        },
        "created_at": "2019-11-16T10:11:12.634234626Z"
    },
    "event": {
        "user_id": "1234",
        "user_login": "cool_user",
        "user_name": "Cool_User",
        "broadcaster_user_id": "1337",
        "broadcaster_user_login": "cooler_user",
        "broadcaster_user_name": "Cooler_User",
        "tier": "1000",
        "is_gift": false
    }
}

We should be able to therefore infer that the event object is of a certain structure. How do we do this in Typescript?

We don't want to use the as keyword in Typescript for this!

Reference: https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types

Some work has been done on this where there are several voices present in the constants file.

With no param: Informs the user how long it has been since they followed the stream

Example:

!followage
It has been 27 days, 2 hours, 8 seconds since you started following

With param (username): Informs how long it has been since the provided user followed the stream

Example:

!followage John
It has been 18 days, 18 hours, 9 seconds since John started following

Currently, the stream status state ("online" or "offline") is only set when the Twitch API sends the WebSocket event, but we may be restarting the bot several times during the same stream.

Let's also request the state when the bot starts up using https://api.twitch.tv/helix/streams https://dev.twitch.tv/docs/api/reference/#get-streams

For example, it is used twice in this same callback to avoid issues with async/await

Twitch will be deprecating many chat commands through IRC.

https://discuss.dev.twitch.tv/t/deprecation-of-chat-commands-through-irc/40486

Only the /ban and /unban currently, by the lutf1sk chat command:

With https://dev.twitch.tv/docs/irc/capabilities/ the membership capability, we can receive messages when a user enters or leaves the chat channel, so we could send them a welcome message.

Personally, I think I would prefer this to be opt-in only from a user's perspective because it's quite anti-lurk.

Combined with this is a need to keep a memory of user choices, so some sort of database is required.

Depends on #24

!remindme <timeframe> <thing>

Example:

!remindme 2d Dentist appointment!

List the current todo issues from the GitHub API

Potentially with a search string

Examples:

When the stream is online:

!uptime
The stream has been live for 1 hour, 5 minutes, 20 seconds

When the stream is offline:

!uptime
The stream is offline

Currently, it doesn't really handle multiple parameters in a nice way. It could be nicer to return this as an array of strings, or even as a separate property in addition to the existing botCommandParams.

Potential proposal:

Return both botCommandParams and a new botCommandParamsList which is pre-split by space.

Should be a separate webpage /credits where it shows all active chatters, new followers, new subscribers, and raiding channels

There is a queue for commands, but not for sounds. Currently, that means if two separate sound commands are used then the last one will play, even if the former was in the process of being played.

Shows details about a command:

• Who can use it
• What cooldown it has
• Aliases
• What it does
• What arguments it takes

Currently we can't play sounds from commands that are made with the !addcommand command. If this is added then a lot of the custom commands saved to the repo could be removed.

Currently, the Discord webhook is required in code by default and requires a manual change to remove it.

Let's just make this optional from the beginning.