Ollama Chat Threads

[kevinthedang]

Steps to Reproduce

• Run the bot on 1 machine (server or local machine)
• Allow 1 person to run a query from the bot
• Then another different person queries the bot
• The result should be similar as below

Ideas

• It would be nice to reduce the clutter on a channel by allowing the bot to create threads and chat individually with a user
  • The permissions of the thread should only be writable to the bot and the conversation with another user.
  • It should be fine for other users to view the thread, but not create queries (chat)
  • Refer below as an example from Slash Commands Integration #12 called threadCreate.ts. Maybe the same way but instead it is on a new query.
    • Shifts message to thread and creates an ephemeral message (somehow)
    • We want to store the threadId and make sure that it is a parent of this thread is the one in the environment.

[kevinthedang]

Just found this out while testing out the slash command:

• Threads have their own channels (so kind of like a child process in a OS)
• There is no threadMessageCreate so we just have to use messageCreate to handle valid chat instances
  • For example, let's say we have 2 chat threads with ids 123 and 124. The bot should only validate messageCreate somehow within those channels.
  • When threadCreate is called, we want to add it to the instance of valid channels to run Ollama.
  • When threadDelete is called, we want to remove it from the instance of valid channels to run Ollama in.

The Client Class found in the discord.js docs lists all of their interactions and brief descriptions of how they work.

[kevinthedang]

Since we are dealing with channels that are "valid", meaning they are still up and being used, we need a way to store them:

I thought about:

1. Storing via json file, editing and removing from it. We can already do that like with the config so it's possible. What is also cool is that we can create configs for different users and put it in their threads/channels/servers so different for each type. What differs between them? Not sure! We'll figure that out later.
2. Some kind of external service, but it would be nice to not depend on other services and only depend on the discord.js package development to reduce dependencies.

[kevinthedang]

Just had a thought:

• If a user ran the /thread command again, it would generate another chat thread. Should we allow this or prevent multiple chats threads with the same user? @JT2M0L3Y

[kevinthedang]

Another thing is when a thread is created these appear:

Should we clean this up using the bot or should we leave them there. @JT2M0L3Y
Deleting these do not delete the thread.

[JT2M0L3Y]

@kevinthedang
I think users should be allowed multiple threads.
We should clean up the remnant thread messages in the main channel stream.

[kevinthedang]

@JT2M0L3Y New Idea for this...

We allow threads to be created everywhere, but the bot can no longer talk in channels.

The only exception for this is in #43 as the bot would talk in a regular public channel.

[JT2M0L3Y]

Definitely.

[kevinthedang]

Extra Stuff

• Introducing Redis would be nice... here are some resource @JT2M0L3Y
  • Redis for Node.js
  • Redis
  • Talks about how Redis Improves Performance
  • YouTube Playlist on Redis

[kevinthedang]

Thoughts:

• Going to move the redis stuff off this issue and keep it on Storing Data Using a Redis Database #57. It will not be required for this issue to close.
• Likely Store Collections of Threads for Chat Validation #59 will be completed along with this issue.

@JT2M0L3Y