Linvi,
Thanks for the quick response. Your activity on the forums is super helpful.
I updated the code and ran it with your changes but the StreamStopped event never fires.
I would also note that I tested this with UserStreams and I get the same limit. Only two of the streams (random every time) get stream data.
Reading the documentation further I noticed that Twitter says connecting to a public stream more than once with the same account credentials will cause the oldest connection to be disconnected. If that is the case I should be fine since I am connecting as a different account with each thread so I shouldn't be limited that way.
I did some experimenting and found that if I ran two instances of my console application that I could get four streams running at the same time (two random ones from each app). They were from four different user accounts and they were all streaming in real time.
Could I have stumbled on a bug in Tweetinvi? I am running 0.9.9.5 from NuGet. Thanks again for all your help.
Thanks for the quick response. Your activity on the forums is super helpful.
I updated the code and ran it with your changes but the StreamStopped event never fires.
I would also note that I tested this with UserStreams and I get the same limit. Only two of the streams (random every time) get stream data.
Reading the documentation further I noticed that Twitter says connecting to a public stream more than once with the same account credentials will cause the oldest connection to be disconnected. If that is the case I should be fine since I am connecting as a different account with each thread so I shouldn't be limited that way.
I did some experimenting and found that if I ran two instances of my console application that I could get four streams running at the same time (two random ones from each app). They were from four different user accounts and they were all streaming in real time.
Could I have stumbled on a bug in Tweetinvi? I am running 0.9.9.5 from NuGet. Thanks again for all your help.