node.js

[Raynos]

[Zirak]

Out of spite

[Zirak]

Tell you what: If you change the bot to not leech off of the chat xhr for input and off of the chat DOM for output, I'll use node.

[Raynos]

So you basically mean "If you write the IO layer for me and allow me to port the bot verbatim"

[Zirak]

Started a port to node. Basics are probably covered, just need to do the login part (that'll be super annoying) and actually retrieving chatroom data. Know any good js html->DOM parsers or should I brush up on my regex-Cthulu-summoning skills?

[ryankinal]

Know any good js html->DOM parsers or should I brush up on my regex-Cthulu-summoning skills?

Er... documentFragment and innerHTML?

[Zirak]

Too bad they're not available on node.

[ryankinal]

Aaaaand I'm a moron

[AmaanC]

Using Zombie.js would mean you'd get to log in and wouldn't have to change much of the IO code

[SomeKittens]

Commenting here so I can feel important.

[Zirak]

This has come up on several discussions so I'll comment on this here (sorry for any stupidity, I'm really tired):

This won't "just happen". The bot won't be re-written since let's be honest, nobody gives enough fucks. It'll be a path of slow migration, slowly decoupling the bot from the chat DOM/BOM.

We can also go the Phatom/Selenium/whatever route but I'm less happy about it. Decoupling from the chat's DOM and BOM gives tons of advantages. It'll at most be a workaround so the bot can work headless, i.e. what we have now run-headless (sort of).

Meh.