57 karma · joined December 24, 2008
www.workpiece.ai
Probably not explaining it very well but I think it's pretty effective at reducing token usage.
Now just onto the fact that most MCP tools are just transforming API calls and their functionality and return data structures suck for LLM's....
Saw more than the occasional jackknifed lorry as well on that hill
It would attempt to send to people as they joined a channel.
More info: http://www.irchelp.org/security/si.html
I used Cabin late last year, and am 6ft 2. It was compact but I had enough space (would have liked more ceiling height but length was ok)
Didn't have any problems with the bus noise, or other people, and the bus was about 3/4 full.
Biggest issue for me was the bumps in the road, so the latest ideas sound like a good step forward.
Being able to go from Santa Monica in the late evening to San Francisco first thing the next morning worked out really well for me, I'd use them again.
Definitely a good way of doing things, still looking for more beta testers but feedback is very positive so far.
https://get.converse.ai/v2.0/docs/plugin-development if anyone wants to kick the tires on it, all feedback welcome.
I was cynical about it to begin with, when it was just 'Facebook at Work' but I do believe it addresses a lot of the issues brought up in the blog post and the Workplace team are executing very well.
Accounts are completely separate from Facebook, no crossover at all.
I don't think it's a Slack killer, as they both solve different problems in different ways, and Workplace is very much a 'big co, top down' approach.
I do think other existing collaboration tools have a lot to be worried about between Slack & Workplace though.
Last stat I heard was there is over 14k companies using it.
It's not using OpenResty though (although OpenResty is very cool)
We are going to be adding Node as well though, for the reasons you mention above around Ecosystem.
Citrix hasn't bought LastPass Citrix hasn't merged directly with LogMeIn, it's still a separate company.
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.
Some are more developer/write your own code focussed, other more graphically focused.
In alphabetical order and not exhaustive.
API.AI (now Google) Chatfuel (YC) Converse.AI (disclaimer, $currentstartup) Flowxo Gupshup.io IBM Watson Engagement Advisor/Watson Meya.ai Microsoft Bot builder Motion.ai Wit.ai (Facebook)
AWS also has a suite of tools that between them you could use, check out Lex, Polly & Steps
All of these do one or more of the following:
NLP User management Messaging Platform Integrations Conversation State & Context Management Workflow Human Escalation Backend integrations (Helpdesk, CRM etc) Analytics
Pick your poison based on what you need :)
Our customers (thankfully) are typically looking for ways to engage with their existing customer base better, and/or deliver their existing commercial services in a better way.
Spent my days deep in TCL, accidentally discovering probably the single deadliest bug in Eggdrop with an accidental copy and paste (would cause all bots in the botnet to go into an infinite loop)
For the last two years I've been working on similar problems but for Messaging networks (Messenger, SMS, Intercom, Slack etc) in $currentstartup
If anyone has questions around bots, conversation management, integrations, NLP etc etc, feel free to ask.
Think Intergenia was probably the biggest from memory.
They will still have a significant vote, but a long long way from a majority on any key issues.
Major differences that I can see are we enable multiple functions to be sent per state, and that the output data from any state is referenceable by any other state, not just passing it down in turn through the states.
We support fallback states but in a different way, and don't support the retry concept directly within the state language itself, has to be built as a set of states to perform a loop to attempt a retry.
We don't support parallel stages, but do support branches, and remerging of those branches.
Probably the final difference I can see, is one of our options when running a function allows you to actually append additional states to the machine during the runtime process.
Front end integrations (Slack, Skype etc) NLP Conversation state and context management Automated knowledge/learning.
etc etc.
I'm in the middle of writing a blog post on this, but https://medium.com/point-nine-news/software-bots-c56aeedcfec... is a good piece to read
Semi or fully automating realtime customer service is definitely a real use case :)
There is a whole pile of interesting posts around building conversational services/bots.
Some interesting ones:
Sam Lessin: https://t.co/0ZFlBGPqpg Chris Messina: https://medium.com/@chrismessina/2016-will-be-the-year-of-co...
Matt Galligan: https://medium.com/@mg/the-graphical-user-interface-will-soo...
Clement Vouillon: https://medium.com/point-nine-news/software-bots-c56aeedcfec...
Ryan Block: https://medium.com/@ryan/bots-messaging-and-the-interface-vi...
I've also written a bunch of articles on how we tackle some of these problems at Converse AI here:
http://blog.converse.ai/introduction/an-introduction-to-conv...