search

Zirak / SO-ChatBot

Other
124 stars 60 forks source link

unonebox timeout too long? #209

Open rlemon opened 10 years ago

rlemon commented 10 years ago

I've been thinking 90sec is too long.

should we :
a) reduce the timeout to say 60sec?
b) make it configurable via a command?
c) leave it at 90sec, rlemon is just drunk and doesn't know what he's on about.

I'd like input.

monners commented 10 years ago

60 Seconds should be more than enough to appreciate the questionable gifs we love to share. Also, having it as a command would be great.

darkyen commented 10 years ago

having a command is best.

AmaanC commented 10 years ago

Yeah, it'd be nice to have it be configurable. And reducing the default to 1m makes sense too On Aug 1, 2014 11:38 AM, "Abhishek Hingnikar" notifications@github.com wrote:

having a command is best.

— Reply to this email directly or view it on GitHub https://github.com/Zirak/SO-ChatBot/issues/209#issuecomment-50852074.

RUJodan commented 10 years ago

I like the idea, but we can take it a little further and add a custom timer (!!burn 5) and reduce the default if no second arg is provided.

rlemon commented 6 years ago

I'm thinking of two changes,

1) I make the timeout a config.
2) I make an additional command to force the unonebox

Zirak commented 6 years ago

Maybe a command to configure it is a tad overkill (who'll remember to run it?), and if it's too long/too short for several cases it could justify respecifying it.

However, a unonebox command sounds good. /unonebox [msgid] by default takes the last message sounds nice.