Show HN: Wit.ai Bot Engine beta(wit.ai) |
Show HN: Wit.ai Bot Engine beta(wit.ai) |
With that said, i understand how hard doing this in a home baked way could be. I think i just won't be happy until we have repositories of standardized ai training sets or baked results (forgive any pseudo terms). It just feels like these days, using awesome AI services means cementing yourself into the service, and making their service stronger as you increase their datasets and training.
As much as i really do love wit.ai, i just don't want to use these types of services unless my backs against a wall.
X as a service allows you to get X with a lot less efforts. It allows you to understand the problem and your needs by getting started quickly. Over time, if X as a service saved you enough time and you become successful, you can choose to develop an expertise in X and cut the dependency.
Wit is also about building a community of developers and advancing the state of the art of NLP in apps. Once the bot engine matures a bit, we'll be focusing again on the community aspect of Wit and hopefully advance the field enough so that efforts like the standardization you mentioned are started.
I think it's more accurate to say that it allows you to borrow X. It's very true that it helps to bootstrap your own product and eventually if things work out you can bring X in-house.
My worry about everything-as-a-service is that until that point, each different service that you use is an another vulnerability to your product. This goes double for specialized services like AI, where unless you already have experts in that field, you're unlikely to have the expertise to replicate the service in-house. (Although by that same token, in this case without the service you couldn't provide your product anyway.)
From a company standpoint, the commoditization of the GP's comment is directly counter to your incentives as a business.
I'm thinking of lots of other places I can use it too now - is there a name for this approach yet?
Can't say I love it though.
Thanks for an awesome product!
2. We use a combination of traditional NLP (CRF NER, maxent classifiers) and deep learning. The "old" stuff needs less data to be trained. We'll continue to support duckling, we always love PRs, please help us!
i've seen/heard that wit.ai likes to use clojure (lisp for AI programming? of course!). was clojure used to power Bot Engine? if so, how did your team like the experience?
I was wondering if there is any way to have predefined stories? I'm sure there is already a bunch of "weather" stories or "how are you" stories that must come over and over. I don't want to spend much time on it
Lacks documentation and examples. There is no support for story branching, conditional flows, or intents.
What is Merge supposed to do.. How is it possible for my server code to know what to merge the entity into context, without knowing the intent.
Basically looking for something like this: https://wit.ai/Francis88/Internet%20of%20Things/eval?_t=856&...
Been playing with the Bot Engine all day btw - great product so far :)
Thank you for the interest :-)
We haven't released any examples showing an integration with Messenger Platform API. In the meantime, please refer to the Messenger Platform docs: https://developers.facebook.com/docs/messenger-platform/quic...
If you have any feedback, please shoot!
Thanks for the insight.
Use cases on Messenger will probably be more around customer care or entertainment, news, etc.
We had planned to release the Bot Engine at F8 long before MSFT's announcement. If you ask me, F8 might have affected their timing more than the other way around ;-)
Today, Wit offers many advantages out-of-the-box so you don't have to setup your own solution.
As NLP gets more commoditized (e.g. through open-source, open datasets), Wit will have to provide even more value than today to stay relevant. Value can be ease of use, accuracy, etc. That's how the field makes progress.
Regarding best interest, if you mean FB's best interest, FB wants more intelligent bots in Messenger, VR, etc. It makes sense to provide the tools to do so. Opening these tools also helps make them better (why is FB open-sourcing React for example?)
If you mean the Wit team's best interest, we're always happy to provide better tools to developers and innovate in AI / UX. That's why we started Wit after all :-)
Any startup founder who follows this strategy is concentrating on the wrong thing. Pick the provider who's most likely to last and build against their service. That way you are more likely to fail than they are.
