[Question] How to implement Transcript store on Twitter Adapter
See original GitHub issueHow do I implement a transcript logger on the twitter adapter?, I am using Entity framework transcript store but I am only able to store outgoing messages with the following code:
((TwitterAdapter)_adapter).ContinueConversationAsync(_appId, conversationReference, BotCallback, default(CancellationToken));
and not able to store incoming messages, how can I do it?
Issue Analytics
- State:
- Created 4 years ago
- Comments:17 (7 by maintainers)
Top Results From Across the Web
How to implement Entity Framework transcript store on ...
The core of this issue is that the Twitter Adapter overwrites others. ... Transcript Store uses the AdapterWithErrorHandler , the Twitter ...
Read more >How to upload caption (.srt) file to Tweets
1. Upload a video to your Tweet. · 2. Select Upload caption file (. · 3. In the pop-up, select the Upload captions...
Read more >A Quick Guide To Creating Captions For Twitter Videos
A Quick Guide To Creating Captions For Twitter Videos · Upload Your Video · Create A Transcript · Double-Check Your SubRip File ·...
Read more >Closed Captioning & Everything You Need to Know About It
DIY Captioning. Create captions with YouTube; Create captions from an existing transcript; Transcribe your audio into text manually; Use an automatic speech ...
Read more >Twitter TWTR Q3 2021 Earnings Call Transcript
Twitter (symbol TWTR) reported Q3 2021 earnings on October 27, 2021. Read the full earnings conference call transcript here.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@fercom The PR is up. I’ve modified the code slightly to follow similar patterns as the existing adapters.
As an aside, we’ve got a pattern we’re using for our new Adapters (Twilio, WebEx, Slack, Teams, etc) that may be applicable to this adapter. I suspect we’ll end up writing hybrid / composite adapters as well for bots that support multiple channels…
Note: There’s also a WeChat adapter in progress, but I’ve not yet had eyes on it so I’m not sure if it conforms. Before we merge it, I’ll make sure that it does match our pattern…