3 ms·
I remember writing a generic chat bot that took in commands and did arbitrary things with it circa 1998, and I was already following decades-old prior art. I b
by jerf 11y ago
I remember writing a generic chat bot that took in commands and did arbitrary things with it circa 1998, and I was already following decades-old prior art.
I bet if we could magic up a list of all the things you could do from IRC in, say, 2000, by using the right chat bot, you'd be less impressed by hailing a taxi.
The rest of what you mention is just service-specific frippery. All the services have had frippery here and there. None of them are particularly important to text moving around, in the end.
- derefr 11y agoI think the point that people are trying (but often failing) to make is that, in this "era" of chat, rather than there being global user-agnostic bots (e.g. Cleverbot) or bots you have to set up and run on some server yourself (e.g. a personal channel dice roller), bots are now also available as a thing you can consume through the service—in the same way that "addons" (third-party services) can be consumed through Heroku, or "service subscriptions" like Netflix can be consumed through a TV box. It's the discoverability and consumption-model of the functionality that's novel, rather than the functionality itself. The novel model also sits at the intersection of "interesting enough to third-parties to incentivize them to create lots of these integrations", and "usable by non-technical people", allowing anyone to "have a bot" for anything they need without all the logistical implications that idea had previously.