Skip to content
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

Open
tobiasvl opened this issue Nov 24, 2017 · 10 comments
Open

Retroactively archive past snippets #1

tobiasvl opened this issue Nov 24, 2017 · 10 comments

Comments

@tobiasvl
Copy link
Member

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.

@MegaLoler
Copy link
Collaborator

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)
what do you think?

@tobiasvl
Copy link
Member Author

Sounds like a plan!

@MegaLoler MegaLoler reopened this Nov 28, 2017
@avivace
Copy link
Member

avivace commented Nov 28, 2017

The software will have two operating modes:

"parse": it will go trough the entire message history
"watch": it will consider messages sent from the moment the bot/execution starts

@MegaLoler
Copy link
Collaborator

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?

@avivace
Copy link
Member

avivace commented Nov 30, 2017

An option in the config should be good, while I tend to think to the "parse" mode only as a one-time task.

@MegaLoler
Copy link
Collaborator

MegaLoler commented Nov 30, 2017

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?

@avivace
Copy link
Member

avivace commented Dec 1, 2017

We could launch 2 instances, one in parse and one in watch?
Or we need to think about a single mode capable of saving/resuming the parsing, and eventually start the "watch"

@MegaLoler
Copy link
Collaborator

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

@avivace
Copy link
Member

avivace commented Dec 2, 2017

It seems to have/had sense. Having that behaviour in the actual implementation would be cool.

@MegaLoler
Copy link
Collaborator

MegaLoler commented Dec 8, 2017

i added a 'oneshot' option in the config (in the README) which, when true, will cause the bot to exit after it has finished scanning the history, as well as telling it to ignore any new messages in the mean time
by default it's false, so the bot will continue running after scanning and accept new messages in the meantime

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants