Public stream track seems to be case sensitive?


#1

Hi

The documentation states that the track used in the public stream is not case sensitive.

I have tried the following:

  • adding the cased variations as tracks
  • using only the lower cased version
  • trying with and without hashtag

The tracking keyword we are using is “futurepastmirror”. Anything that contains FuturePastMirror does not come through the public stream.

Please Help.


#2

Bump


#3

Same issue, since few hours.

Don’t know if it’s an issue or change in API. Do not find any clue in the blog or forum


#4

We are also experiencing the same issue


#5

Hello Devonne, Pascal and Lorraine,

Thank you very much for reporting this issue.

We are currently investigating with the team and it seems related to a change we made yesterday. We will be deploying a fix as soon as possible and will keep you updated.

Thanks for your patience.

Best,
Romain


#6

Hi Romain,

As well as this case sensitivity issue, there seems to be other issues with tracking keywords using the streaming API.

We have noticed that tracking “4sq” for example is no longer pulling back tweets such as “I’m at Sheffield University Management School http://4sq.com/1lplU8O” Could this also be related, as this has only stopped working very recently? Tracking ‘4sq’ is now only returning tweets where ‘4sq’ is a standalone word in the tweet.

Thanks ,
Adam


#7

Hello again everyone,

The team has just deployed a fix to production. We have performed some tests and the case-insensitive keyword tracking should work again as expected.

Please let us know if you encounter any other issues with the Streaming API endpoints.

Thank you all again for the report and your patience.


#8

Thanks Romain … all looking good. Very impressed with the quick turn around on this!


#9

Thank you for the note, Adam! Glad to hear everything is working again as expected on your side.