Todd Kuebler - Oct 16, 2017:
There is a lot of unexplored territory to cover here.
Thanks Todd,
1. tech side:
and back to the original point (how to keep in touch multiple CS bots, as separated TCP server) I’m thinking about a general purpose, low level software, virtually independent from any specific application context. Just a router/dispatcher. That could be realized with the pseudocode I wrote above. I’m also thinking about how to use a standard linux openvswitch.
More generally, fantasizing about an “internet of bots” (not just ChatScript), but anything, I feel that websocket protocol ( https://en.wikipedia.org/wiki/WebSocket ) is possibly a better solution for message based (bots) interchange, instead of TCP sockets (and so HTTP).
I have to deepen about it.
2. business implications of group chat with bots:
Of course sound bizarre to connect any bot to any other independent bot with one-to-one connection.
What could be instead interesting is to have a group chat populated by humans and bots.
Two real scenarios are Slack and Telegram (with Groups) platforms. btw, many months a go I sketched some examples here: https://github.com/solyaris/BOTServer/blob/master/wiki/services.md#5-complex-group-chat-multiple-humans-multiple-bots)
both platforms act as “hubs” and bot authors can test ideas…