By sheer coincidence I managed to capture a minor milestone in @tippy's life earlier with the script now having replied 420 times to myself and a few other users that have been lucky enough to catch it while it's up and running during R&D. Made a bit of a breakthrough today thanks to @fabien who let me try out an upcoming beta release of steemJS which has some neat options coming in the next release. Going to go bake with my robot and get back to it.

Still having some issues with the whole "sync the not yet scanned blockchain" functionality of the bot and have yet to build the queue system to allow the bot to operate under heavy load and reply to everyone as well as look into hybridizing command scanning between the last irreversible block and the head block. A difference of about 50 seconds latency or so in replies or bot functions lies between the header and irreversible block.

With all services speed is of the essence however security is the #1 priority and I'll have to experiment with the right mix of express service and block-chain based security measures. Most calls such as help or balance calls SHOULD be able to listen and reply on the header block operations coming in live on the network.. However things like deposits or transfer of funds require a bit more finesse and security thus would likely have to listen on the last irreversible block to make sure it cannot be reversed.