<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Julien Odent on Medium]]></title>
        <description><![CDATA[Stories by Julien Odent on Medium]]></description>
        <link>https://medium.com/@jodent?source=rss-f9d6d032854d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*evmqV8anc4Iv5Q5jeYFprw.jpeg</url>
            <title>Stories by Julien Odent on Medium</title>
            <link>https://medium.com/@jodent?source=rss-f9d6d032854d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:24:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jodent/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Richer Voice Experiences]]></title>
            <link>https://medium.com/wit-ai/richer-voice-experiences-9da370179362?source=rss-f9d6d032854d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9da370179362</guid>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[voice-recognition]]></category>
            <category><![CDATA[conversation-design]]></category>
            <category><![CDATA[naturallanguageprocessing]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <dc:creator><![CDATA[Julien Odent]]></dc:creator>
            <pubDate>Tue, 11 Oct 2022 19:44:03 GMT</pubDate>
            <atom:updated>2022-10-11T19:44:03.070Z</atom:updated>
            <content:encoded><![CDATA[<h4>Releasing Composer Beta for Wit.ai and Unity</h4><p>Today, we’re graduating Composer to Beta. We’re also rolling out the <a href="https://developer.oculus.com/documentation/unity/voice-sdk-composer">Composer integration</a> to the Oculus Voice SDK for Unity. Composer enables you to support rich voice experiences in a simple way.</p><p>Composer offers a visual way to understand, draft, iterate on, run, test and author conversations. Using four powerful modules, you can map out user interactions with control and confidence. The new endpoints <a href="https://wit.ai/docs/http/#post__converse_link">POST /converse</a> and <a href="https://wit.ai/docs/http/#post__event_link">POST /event</a> run your deployed flow. Learn more about Composer in the <a href="https://wit.ai/docs/recipes#composer">documentation</a>.</p><p>Since the <a href="https://medium.com/wit-ai/introducing-composer-alpha-b3b808e1cdc3">alpha release</a>, we’ve seen early adopters craft intent-based responses, hook up custom actions and handle missing entities with multi-turn conversations. We’ve improved the design language of the modules, reviewed the content, polished the layout and simplified the authoring of flows. Composer flows are now included in the <a href="https://wit.ai/docs/recipes#export-your-app">Import/Export</a> feature.</p><p>We’re also introducing Groups so you can continue visualizing and iterating on your flows effortlessly as your natural language experience becomes richer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MWBh8TVTlnZ1qmlU3snxnw.png" /></figure><p>Check out the <a href="https://metaconnect.com/en-us/program/cf8f52e1-8b8e-4eeb-8149-c22c51ff0e36/">Building Immersive Voice Driven Experiences with Presence Platform</a> session at Meta Connect for a demo of Composer.</p><p>Since the renewed focus on <a href="https://medium.com/wit-ai/improving-voice-experiences-52492b4849b4">improving voice experiences</a> about a year ago, we’ve launched <a href="https://medium.com/wit-ai/pure-audio-transcription-7372aa0bda7e">POST /dictation</a>, <a href="https://medium.com/wit-ai/turning-text-into-speech-7f5e088e42c">POST /synthesize</a>, and <a href="https://wit.ai/docs/http#post__speech_link">live understanding</a>. We’ve improved the latency and the reliability of our service. Thank you for being part of this journey with us.</p><p>The Wit.ai team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9da370179362" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wit-ai/richer-voice-experiences-9da370179362">Richer Voice Experiences</a> was originally published in <a href="https://medium.com/wit-ai">Wit.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Composer Alpha]]></title>
            <link>https://medium.com/wit-ai/introducing-composer-alpha-b3b808e1cdc3?source=rss-f9d6d032854d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3b808e1cdc3</guid>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[wit]]></category>
            <category><![CDATA[naturallanguageprocessing]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <dc:creator><![CDATA[Julien Odent]]></dc:creator>
            <pubDate>Mon, 01 Aug 2022 18:45:38 GMT</pubDate>
            <atom:updated>2022-08-01T18:45:38.696Z</atom:updated>
            <content:encoded><![CDATA[<p>Today we’re launching the alpha release of Composer, bringing end-to-end conversational support to Wit.ai. Composer enables you to author rich conversation maps by managing the dialogue state and your application responses in a visual way. This is the largest Wit.ai product update to date, and we’re eager to see you give it a try!</p><p>Building natural language experiences is hard, but we can do better. We believe that Composer is a significant step forward in our mission to <em>enable Natural Language for Everyone</em>. We believe that if you can speak a language, you should be able to create a natural language experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p2Ot6WvycOo3KsLNoe3TMQ.png" /></figure><p>Composer offers a visual way to understand, draft, iterate on, run, test and author conversations.</p><p>Since <a href="https://medium.com/wit-ai/launching-built-in-nlp-for-messenger-and-sunsetting-bot-engine-beta-46e9038869a5">Bot Engine</a>, we’ve scaled our platform and bolstered our API offering. We’ve learnt a lot along the way, and are ready to tackle the hard problem of dialogue again. While machine learning is going to be a necessary path to scale dialogue in a simple way, today’s bottleneck isn’t really scale. We first need an approachable tool to author and deploy simple conversations.</p><p>Composer focuses on the essence of conversation design. Using a few functional components and an explicit information flow, you can create conversation maps with control and confidence. It’s simple, transparent and reliable.</p><p>In Composer, you manage the conversation state using your own key-value store: the context map. To upgrade to Composer, <a href="https://wit.ai/docs/http/#post__speech_link">POST /speech</a> (resp. <a href="https://wit.ai/docs/http/#get__message_link">GET /message</a>) developers should integrate with <a href="https://wit.ai/docs/http/#post__converse_link">POST /converse</a> (resp. <a href="https://wit.ai/docs/http/#post__event_link">POST /event</a>). Read more in the <a href="https://wit.ai/docs/recipes#composer">documentation</a>.</p><p>We’re only 1% there, and are looking forward to hearing your <a href="https://github.com/wit-ai/wit/issues">crucial feedback</a>. Thank you for being part of this journey.</p><p>The Wit.ai team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3b808e1cdc3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wit-ai/introducing-composer-alpha-b3b808e1cdc3">Introducing Composer Alpha</a> was originally published in <a href="https://medium.com/wit-ai">Wit.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving Voice Experiences]]></title>
            <link>https://medium.com/wit-ai/improving-voice-experiences-52492b4849b4?source=rss-f9d6d032854d------2</link>
            <guid isPermaLink="false">https://medium.com/p/52492b4849b4</guid>
            <category><![CDATA[naturallanguageprocessing]]></category>
            <category><![CDATA[wit]]></category>
            <category><![CDATA[voice-recognition]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[virtual-reality]]></category>
            <dc:creator><![CDATA[Julien Odent]]></dc:creator>
            <pubDate>Thu, 11 Nov 2021 22:36:43 GMT</pubDate>
            <atom:updated>2021-11-11T22:36:43.658Z</atom:updated>
            <content:encoded><![CDATA[<p>Since we launched the <a href="https://github.com/wit-ai/wit-unity">Wit-Unity SDK</a>, we’ve been deeply focused on improving voice applications in AR and VR. Today, we’re excited to announce the experimental release of the <a href="https://developer.oculus.com/downloads/package/unity-integration/">Voice SDK</a>, as part of the <a href="https://developer.oculus.com/blog/introducing-presence-platform-unleashing-mixed-reality-and-natural-interaction-for-oculus-developers/">Meta Presence Platform</a>. If you missed the Voice Interactions in VR session at Facebook Connect, you can watch it <a href="https://www.facebook.com/watch/?v=268180458652073">here</a>. You can download the Voice SDK today, in the <a href="https://developer.oculus.com/downloads/package/unity-integration/">Oculus Integration SDK v34 release</a>. Read more about the Voice SDK on the <a href="https://developer.oculus.com/blog/presence-platform-voice-sdk-and-passthrough-now-available/">Oculus Developer Blog</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F21T7v3wJ-2yIh2h" /></figure><p>When deploying voice applications, a key factor in the quality of the experience is the perceived latency. Using voice is natural, but it’s only efficient if it’s fast.</p><p>We’ve upgraded our POST /speech API to deliver transcriptions as they come. For versions above 20210928, intermediate speech recognition results will be sent in chunks. The last chunk will return the final transcription with the intents, entities and traits as usual. Refer to the <a href="https://wit.ai/docs/http/#post__speech_link">latest API documentation</a> for further details.</p><p>You can now use the partial transcriptions to build your own attention system! We believe this is an important update toward richer voice experiences.</p><p>We’ve also significantly improved the overall latency of our <a href="https://wit.ai/docs/http/#post__speech_link">POST /speech</a> API. For better performance, please consider sending <a href="https://wit.ai/docs/http/#post__speech_link">16kHz raw, wav or flac audio</a>. The other audio encodings are still supported, incurring a higher processing time.</p><p>Finally, we’ve upgraded our Automated Speech Recognition (ASR) English model to a better architecture, with personalization support. This means that the utterances you’ve validated in your app will help improve the ASR accuracy.</p><p>Note that POST /speech is still optimized for short voice inputs.</p><p>As you know, the context of a natural language request matters. We’ve enabled <a href="https://wit.ai/docs/http/#dynamic_entities_link">dynamic entities</a> support for GET /message and POST /speech. You can now extend your defined keywords entities with new keywords and synonyms for each request! Dynamic entities will help inform the ASR processing in English as well.</p><p>To help you get familiar with NLP in Unity, we’ve enabled Built-In NLP in the Voice SDK. We’ve shared 16 new built-in intents for English, and we’ve extended the support for built-in entities with 59 new entities in 16 languages. Thank you for all your contributions to <a href="https://github.com/facebook/duckling">Duckling</a>!</p><p>The Oculus Voice SDK is a drop-in replacement for the Wit-Unity SDK. It offers the same API and utilizes the Wit-Unity SDK under the hood. We encourage early Wit-Unity developers to upgrade to the Oculus Voice SDK.</p><p>As always, we welcome your feedback, comments and suggestions. Please reach out to us <a href="https://github.com/wit-ai/wit/issues/new">on GitHub</a>!</p><p>Wit.ai Team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52492b4849b4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wit-ai/improving-voice-experiences-52492b4849b4">Improving Voice Experiences</a> was originally published in <a href="https://medium.com/wit-ai">Wit.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reminder: Connect Your Account to Facebook]]></title>
            <link>https://medium.com/wit-ai/reminder-connect-your-account-to-facebook-7f895c2a66?source=rss-f9d6d032854d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f895c2a66</guid>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[nlp]]></category>
            <category><![CDATA[wit]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Julien Odent]]></dc:creator>
            <pubDate>Tue, 03 Nov 2020 00:37:27 GMT</pubDate>
            <atom:updated>2020-11-03T00:37:27.123Z</atom:updated>
            <content:encoded><![CDATA[<p>As we <a href="https://medium.com/wit-ai/introducing-the-refreshed-wit-ai-3a7c603d325a">previously announced</a>, by December 30, 2020, you will need to log in with Facebook to access your Wit.ai account. The transition to Facebook infrastructure will allow us to simplify our codebase, allowing us to ship new features to you faster.</p><p>What does this mean?</p><ul><li>If you currently use a GitHub login to access your Wit.ai account, you will have to connect your Facebook account to use Wit.ai and access your apps</li><li>If you are using Wit.ai for the first time, you will need to log in with a Facebook account</li></ul><p>After December 30, 2020, we will end support for Wit.ai accounts that are accessed with a GitHub login. We know this is a significant switch and to help you connect your accounts, here are steps to take to continue to have access to your account and apps.</p><p><strong>How to connect to your Facebook account</strong></p><p>To switch your account over from using a GitHub login to Facebook:</p><p>First, go to <a href="https://wit.ai/">https://wit.ai/</a>.</p><p>Click on the “<strong>Continue with GitHub</strong>” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/0*ojKoJDy3Q_5XlRlh" /></figure><p>On the next page you can choose to continue with Facebook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6LeBbsNlisj3JL7q" /></figure><p>You’ll then be prompted to connect Wit.ai to your Facebook account and grant permission for Facebook to connect your accounts. From there, you’ll be directed to your current Wit.ai Dashboard, where you can access your apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a92yC9st6q_HDq1_" /></figure><p>We will continue to update existing users of this change as we get closer to ending support for GitHub accounts. In the meantime, here are some answers to questions you may have about this transition, you can also check out our <a href="https://wit.ai/faq">FAQ</a> page.</p><p><strong>Can I still log in to my Wit.ai account using my GitHub account after I connect my Facebook account?</strong></p><p>If you have connected your Facebook account with your Wit.ai account, you may transition to the Facebook login immediately. You can still log in to your Wit.ai account using the GitHub authorization option until December 30, 2020. Once your Facebook and Wit.ai accounts are connected, if you log in using the Github authorization option you will be automatically directed to the refreshed user interface associated with your Facebook account where you will be able access all your apps.</p><p><strong>If I am currently using the GitHub authentication option, what will happen to my apps when I connect my Facebook account to my Wit.ai account?</strong></p><p>When you connect your Facebook account with Wit.ai, all apps associated with your current GitHub account will be moved to a refreshed user interface associated with your Facebook account. Your existing apps will not be impacted, and no data will be lost. After December 30, 2020, the GitHub authentication option will cease to be available and all developers will need to have a Facebook account to access Wit.ai.</p><p><strong>What happens to my GitHub Wit.ai account if I do not connect my account to my Facebook account by December 30, 2020?</strong></p><p>You will need to connect your Wit.ai account to your Facebook account by December 30, 2020. You won’t be able to sign into your GitHub account after December 30, 2020. You will not be able to access your apps unless you connect your Wit.ai account to your Facebook account.</p><p><strong>Is a Facebook account required to use my Wit.ai account?</strong></p><p>As of May 2020, developers can no longer create a Wit.ai account using a GitHub account. First time Wit.ai users need to log in with a Facebook account. If you want to create a Wit.ai account and don’t have a Facebook account, you will be given the option to create one.</p><p>If you are an existing Wi.ai user currently using a GitHub account to log in, you will have the option to log in with a Facebook account. If you choose to log in with a Facebook account, your apps will be moved to a refreshed user interface associated with your Facebook account. If you choose not to log in using a Facebook account, you can continue to log in using a GitHub account until December 30, 2020, but full functionality will require a Facebook account. After December 30, 2020, the GitHub authentication will no longer be an option and you will need a Facebook account to use Wit.ai</p><p><strong>What happens if I delete my Facebook account? Can I still access my Wit.ai account?</strong></p><p>Wit.ai will use your FB login to authenticate your access to your Wit.ai account. If you delete your account, you will not be able to access your apps.</p><p>While you can still access your previous interface through your GitHub account till December 30, 2020, your apps will have been moved to your Facebook account and not accessible through your GitHub account.</p><p><strong>Questions or Feedback?</strong></p><p>Leave a comment in our <a href="https://www.facebook.com/groups/withackers/">Wit.ai Hackers</a> Facebook group if you have any questions or feedback.</p><p>Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f895c2a66" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wit-ai/reminder-connect-your-account-to-facebook-7f895c2a66">Reminder: Connect Your Account to Facebook</a> was originally published in <a href="https://medium.com/wit-ai">Wit.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Built-in NLP Integration with Page Inbox ]]></title>
            <link>https://medium.com/wit-ai/built-in-nlp-integration-with-page-inbox-a1ecfc8c0d11?source=rss-f9d6d032854d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1ecfc8c0d11</guid>
            <category><![CDATA[naturallanguageprocessing]]></category>
            <category><![CDATA[messenger-platform]]></category>
            <category><![CDATA[messenger-bots]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[nlp]]></category>
            <dc:creator><![CDATA[Julien Odent]]></dc:creator>
            <pubDate>Tue, 01 May 2018 17:47:05 GMT</pubDate>
            <atom:updated>2018-05-01T17:47:05.299Z</atom:updated>
            <content:encoded><![CDATA[<p>Last year we <a href="https://medium.com/wit-ai/launching-built-in-nlp-for-messenger-and-sunsetting-bot-engine-beta-46e9038869a5">launched built-in NLP</a> to enable developers to easily <a href="https://messenger.fb.com/developers/resources/natural-language-processing/">integrate NLP in their Messenger bot</a>. When built-in NLP is enabled, it automatically extracts relevant information as entities in the messages your bot receives. Today we support 14 default entities and 21 languages.<br> <br>We do realize that each business has different needs which require custom entities, and it is impossible to come up with all the ways people are messaging a Page.<br> <br>To address both limitations, we’re launching an easy way to integrate built-in NLP with Page inbox. Page admins are now able to create a custom Wit app and then automate responses to common requests using anonymized samples from past messages their Page has received.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=facebook&amp;url=https%3A//www.facebook.com/MessengerPlatform/videos/1803036439991126/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.xx.fbcdn.net%252Fv%252Ft15.0-10%252Fp720x720%252F28761695_2059995404019273_4972708024297717760_n.jpg%253F_nc_cat%253D0%2526oh%253D944caf4a70d7c1faaddaa3f4534a561f%2526oe%253D5B9438A1%26key%3D4fce0568f2ce49e8b54624ef71a8a5bd" width="600" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/e36c9a65489782a95bf5e5d5828d3840/href">https://medium.com/media/e36c9a65489782a95bf5e5d5828d3840/href</a></iframe><p>With this new integration, we hope to make NLP even more accessible than before within Messenger. As mentioned in <a href="https://medium.com/wit-ai/community-update-february-2018-d6a25c93827f">last our community update</a>, we are focused on providing powerful and simple natural language processing for the community.<br> <br>As always, <a href="https://www.facebook.com/groups/withackers/">feel free to reach out</a> if you have any questions, comments, or suggestions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1ecfc8c0d11" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wit-ai/built-in-nlp-integration-with-page-inbox-a1ecfc8c0d11">🚀Built-in NLP Integration with Page Inbox 🚀</a> was originally published in <a href="https://medium.com/wit-ai">Wit.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>