-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retroactively archive past snippets #1
Comments
for sure! the way i imagine it, this would be in the form of a one time process of scanning all of the chat history in the server, which we could provide as a cli command (and if we want to purge the collection for any reason, we could just do this process again, for example, once we finally decide how exactly we'll store the snippets and implement it, we can do a fresh full scan of the history) |
Sounds like a plan! |
The software will have two operating modes: "parse": it will go trough the entire message history |
when in "parse" mode, will it automatically exit after it's done, or automatically switch into "watch" mode? how will these modes be accessed? should we rename the option in the config file from "history" to "parseMode" or something similar, or do you have something else in mind? |
An option in the config should be good, while I tend to think to the "parse" mode only as a one-time task. |
i renamed the "history" option to "parse" and made it quit after finishing do you think it is a problem that new messages will be missed by the bot that are created while in parse mode or during the time between finishing parse mode and starting watch mode? |
We could launch 2 instances, one in |
the way it worked before i changed it was that once it logged in it would parse the history, meanwhile watching for new messages as well, and once it finished parsing it would stay logged in and continue watching |
It seems to have/had sense. Having that behaviour in the actual implementation would be cool. |
i added a 'oneshot' option in the config (in the |
We should make sure we (either with the bot or manually) archive all past snippets as well, so they're not lost like tears in the rain.
The text was updated successfully, but these errors were encountered: