Filtered Streams not working

Sep 2, 2014 at 3:14 PM
Edited Sep 2, 2014 at 4:45 PM
I see that User Streams are down according to Twitter. However, I have a Tweetinvni filtered stream service running on Azure that's been running just fine for months that suddenly stopped working.

Twitter lists their API status here: https://dev.twitter.com/status

I can't even get the little filteredStream example working anymore using different (definitely not throttled) credentials.

Is anyone else seeing the same issue?

My thought is that the Twitter API for streams is down but I'm getting no response from Twitter.


[Adding a bit more detail]
I am able to get a sample stream working just fine. This appears to be limited to Filtered Streams only.
Here's the simple sample I'm trying to test. I've run this test code successfully several times before today.

var filteredStream = Stream.CreateFilteredStream();
filteredStream.AddTrack("someuniquekeyword");
filteredStream.MatchingTweetReceived += (sender, argsStream) => { Console.WriteLine(argsStream.Tweet.Text); };
filteredStream.StartStreamMatchingAllConditions();
Sep 2, 2014 at 5:15 PM
tjbutler wrote:
I see that User Streams are down according to Twitter. However, I have a Tweetinvni filtered stream service running on Azure that's been running just fine for months that suddenly stopped working.

Twitter lists their API status here: https://dev.twitter.com/status

I can't even get the little filteredStream example working anymore using different (definitely not throttled) credentials.

Is anyone else seeing the same issue?

My thought is that the Twitter API for streams is down but I'm getting no response from Twitter.


[Adding a bit more detail]
I am able to get a sample stream working just fine. This appears to be limited to Filtered Streams only.
Here's the simple sample I'm trying to test. I've run this test code successfully several times before today.

var filteredStream = Stream.CreateFilteredStream();
filteredStream.AddTrack("someuniquekeyword");
filteredStream.MatchingTweetReceived += (sender, argsStream) => { Console.WriteLine(argsStream.Tweet.Text); };
filteredStream.StartStreamMatchingAllConditions();
False alarm and lesson learned?

I was tweeting from the account I used to authorize the stream listener. It appears as though a filtered stream does not get matches from the account from which its auth credentials were generated.

I simply used another Twitter account and the keywords were matched as expected.

Very odd that I hadn't hit this behavior on my original testing but... I wanted to share that with the community.
Marked as answer by linvi on 9/13/2014 at 6:14 PM