Open ralt opened 10 years ago
known issue.
I was positive this had been reported before. The bot relies on the DOM messages for the replacement. This could be possible if she reached into the transcript for the room. I'll look into it this afternoon.
I think the main problem here is that it gets it from a different room, not that it doesn't work in other rooms. In other rooms, it should probably just say, "Sorry, that only works in the JavaScript room because...." On Sep 18, 2014 8:00 PM, "Robert Lemon" notifications@github.com wrote:
I was positive this had been reported before. The bot relies on the DOM messages for the chat. This could be possible if she reached into the transcript for the room. I'll look into it this afternoon.
— Reply to this email directly or view it on GitHub https://github.com/Zirak/SO-ChatBot/issues/216#issuecomment-56046344.
@AmaanC I'm pretty sure it is possible. I just need to /get on the transcript and search that.
Yeah, I'm sure it's possible too. Just more work! We're a lazy bunch of contributors On Sep 18, 2014 8:03 PM, "Robert Lemon" notifications@github.com wrote:
@AmaanC https://github.com/AmaanC I'm pretty sure it is possible. I just need to /get on the transcript and search that.
— Reply to this email directly or view it on GitHub https://github.com/Zirak/SO-ChatBot/issues/216#issuecomment-56046875.
LAZY?!?! I'm working my tail off here, feeding you lot!
So the NodeJS port is about done, right? :D On Sep 18, 2014 10:38 PM, "Randall Koutnik" notifications@github.com wrote:
LAZY?!?! I'm working my tail off here, feeding you lot!
— Reply to this email directly or view it on GitHub https://github.com/Zirak/SO-ChatBot/issues/216#issuecomment-56070741.
Once they (as in, Intel) makes node-webkit headless, we can trivially port my so-chatbot-driver to node-webkit and call it a day. No need to port the guts of the bot to node; we can continue running it in a webkit context, just headless and driven by node itself.
It's coming. :)
http://chat.stackoverflow.com/transcript/message/18962557#18962557
Notice the rooms of message's source and where the command was run (and answered).