tweetinvi | intuitive Twitter C # library for the REST and Stream API | REST library

Tweetinvi opens a socket with the Twitter Stream Endpoint. It means that any delay (apart from network latency) will come from when Twitter manages to analyse the event and send it back to its streams.

You can see it in the code you posted. The second line of that method does it. You use the Await operator to await the completion of the Task.

That said, there is no result to get anyway. If you have a synchronous Sub then that becomes an asynchronous Function that returns a Task. In both cases, there is no actual value to get out of the method. As such, awaiting such a method doesn't return anything. If you have a synchronous Function with a return type of T then that becomes an asynchronous Function that returns a Task(Of T). Awaiting that gives you a result of type T.

If you had these methods:

Auth for older versions. Check Tweetinvi 5.0.3 documentation out https://linvi.github.io/tweetinvi/dist/twitter-api-v1.1/tweets.html

Yes, you can create an access token and secret for your secondary account. The standard way to do this would be to implement sign-in with Twitter in an app, which would require a web backend.

There are a couple of alternative options:

1. You can use twurl, which is a Twitter-provided command line tool. You’ll need to have Ruby installed, and then install twurl. Using twurl you can run

twurl authorize --consumer-key [your API token] --consumer-secret [your API secret]

This will then provide a URL you should open in your browser. Authenticate this to your secondary account and type the PIN into your terminal. The account token and secret will be placed in a hidden file called .twurlrc in your home directory, and you can use them for your bot in the same way you’re currently using your main account tokens.

1. You can use another utility called tw-oob-oauth-cli to do the same thing. This is a bit easier as you don’t need to install Ruby, and can just download a Windows binary. You’ll want to rename the binary with a .exe extension.

tw-oob-oauth.exe --key [your API token] --secret [your API secret]

This will output the account token and secret on the terminal after you’ve been through the web flow.

After a large amount of time spent I was able to figure out the issue. I guess Twitter is now requiring TLS 1.2 as stated here: https://api.twitterstat.us/ (scroll down to update on 25/7/2019). Upgrading my .NET Framewokr to 4.6 (from 4.0) resolves the issue.

I read somewhere else you can use System.Net.ServicePointManager.SecurityProtocol |= System.Net.SecurityProtocolType.Tls12;. Source

Hope this helps someone else in the future.

1. Discord does not provide an endpoints for Bots to search/filter on specific criteria. The only way to retrieve messages is to use the GetMessagesAsync() method
2. The limit for GetMessagesAsync() is technically Int32.MaxValue. The 100 that you see is simply the default. This is because Discord will return in chunks; 100 messages at a time. For example if you set the limit to 1000, you will get 10 chunks of 100.
3. Possible issues with retrieving a large number of messages? The main issue would be the length of time taken to retrieve the messages, which could block the gateway unless offload the process to its own task.

A possible solution would be to implement your own system for linking and storing twitter posts to discord posts. Could be as simple as a dictionary of Twitter post id and discord post id which would allow you to easily find the message id related to a given twitter post.