3 ms·

It depends on what you mean by a "chatbot platform". If it's a way of developing a single "chatbot" and having it work across multiple "platforms" (think slack

It depends on what you mean by a "chatbot platform". If it's a way of developing a single "chatbot" and having it work across multiple "platforms" (think slack, hipchat, irc, facebook, standalone, etc... maybe even including voice-specific platforms like Amazon echo and Google Home). I would LOVE that. However it's going to most likely suffer from the same issues as other "platform-independent systems" which is that you'll be developing to the lowest common denominator. If it's just a way to make a chatbot via a GUI, I'm personally not interested at all.

ohstopitu 10y ago
The idea is just as you mentioned - a platform where you'd basically create a bot (by that i mean, your code will be given a context, and your response would be forwarded to the chatting service - be it slack, irc, etc.) Furthermore, with an base SDK, you'd not build for a specific service, you'd build it for MY service and it'd handle every other service out there (insert XKCD joke about different platforms here) Also as for GUI, it's not a requirement - it's for those who are not programmers but want to a chatbot for their Echo or Home etc. (an IFTTT of sorts if you will). Also it'd have extra stuff that devs won't have to worry about (like hosting or charging users, promoting etc.) - all of which would be handled by my platform).
- johnsmith21006 10y ago
  Checkout AI .API. This sounds like!E what you might be looking for.
tonylucas 10y ago
The way we handle this (and avoid the lowest common denominator problem) is allowing you to have one bot, but then specific 'modules' that execute only if being accessed over a specific network. This lets you build one bot that supports everything from SMS to Messenger to Slack in the same interface. Other tools I've seen apparently do automatic conversion of one rich media form to another, but I'm less keen on that idea personally.

ohstopitu 10y ago

The idea is just as you mentioned - a platform where you'd basically create a bot (by that i mean, your code will be given a context, and your response would be forwarded to the chatting service - be it slack, irc, etc.) Furthermore, with an base SDK, you'd not build for a specific service, you'd build it for MY service and it'd handle every other service out there (insert XKCD joke about different platforms here) Also as for GUI, it's not a requirement - it's for those who are not programmers but want to a chatbot for their Echo or Home etc. (an IFTTT of sorts if you will). Also it'd have extra stuff that devs won't have to worry about (like hosting or charging users, promoting etc.) - all of which would be handled by my platform).

johnsmith21006 10y ago
Checkout AI .API. This sounds like!E what you might be looking for.

tonylucas 10y ago

The way we handle this (and avoid the lowest common denominator problem) is allowing you to have one bot, but then specific 'modules' that execute only if being accessed over a specific network. This lets you build one bot that supports everything from SMS to Messenger to Slack in the same interface. Other tools I've seen apparently do automatic conversion of one rich media form to another, but I'm less keen on that idea personally.