Skip to content
This repository has been archived by the owner on Jul 17, 2020. It is now read-only.

Cross-room substitute #216

Open
ralt opened this issue Sep 18, 2014 · 8 comments
Open

Cross-room substitute #216

ralt opened this issue Sep 18, 2014 · 8 comments

Comments

@ralt
Copy link
Collaborator

ralt commented Sep 18, 2014

http://chat.stackoverflow.com/transcript/message/18962557#18962557

Notice the rooms of message's source and where the command was run (and answered).

@rlemon
Copy link
Collaborator

rlemon commented Sep 18, 2014

known issue.

@rlemon rlemon closed this as completed Sep 18, 2014
@rlemon rlemon reopened this Sep 18, 2014
@rlemon
Copy link
Collaborator

rlemon commented Sep 18, 2014

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.

@AmaanC
Copy link
Contributor

AmaanC commented Sep 18, 2014

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" [email protected] 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
#216 (comment).

@rlemon
Copy link
Collaborator

rlemon commented Sep 18, 2014

@AmaanC I'm pretty sure it is possible. I just need to /get on the transcript and search that.

@AmaanC
Copy link
Contributor

AmaanC commented Sep 18, 2014

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" [email protected] 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
#216 (comment).

@SomeKittens
Copy link
Contributor

LAZY?!?! I'm working my tail off here, feeding you lot!

@AmaanC
Copy link
Contributor

AmaanC commented Sep 18, 2014

So the NodeJS port is about done, right? :D
On Sep 18, 2014 10:38 PM, "Randall Koutnik" [email protected]
wrote:

LAZY?!?! I'm working my tail off here, feeding you lot!


Reply to this email directly or view it on GitHub
#216 (comment).

@allquixotic
Copy link

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. :)

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

No branches or pull requests

5 participants