In most chat rooms, IRC, discord, slack, etc, you can see a list of users. On IRC this is frequently changing. It would be helpful if we verified that users exist, maybe even collect some information about them (perform a /whois, discord user API lookup equiv, etc.) and store this in NATS.
[x] Create NATS KV stream
[ ] Instance based
[ ] Nickname change tracking
[ ] Word frequency / wordgram analysis
[ ] Link harvesting - check sentiment of links shared, political lean
[ ]
By instance based I mean, users should be able to spin up a new instance in the portal for a particular project, a new graphDB is created, a new vector DB is created to store the chat logs and user info, and the user info is synchronized to the NATS KV <--> vectordb so we can use it for RAG.
We need to figure out what to do about long-term storage of this data and making it available for reporting, perhaps implementing Apache superset and giving customers their own instance.
In most chat rooms, IRC, discord, slack, etc, you can see a list of users. On IRC this is frequently changing. It would be helpful if we verified that users exist, maybe even collect some information about them (perform a /whois, discord user API lookup equiv, etc.) and store this in NATS.
By instance based I mean, users should be able to spin up a new instance in the portal for a particular project, a new graphDB is created, a new vector DB is created to store the chat logs and user info, and the user info is synchronized to the NATS KV <--> vectordb so we can use it for RAG.
We need to figure out what to do about long-term storage of this data and making it available for reporting, perhaps implementing Apache superset and giving customers their own instance.