Twitter feed - no data with csdl used


#1

Hi

I am using muti streaming and testing realtime streaming with twitter. A post was made to twitter with the content: “www.alicemccall.com

I used this csdl: links.domain in “alicemccall.com

I was monitoring in realtime…no hits. Question…,why?

Did I use the wrong csdl?
You you random sampling because I am a trial account?
Are you not realtime?
Anything else I did wrong given the below URL?

Here is the stream I used
https://stream.datasift.com/multi?username=test&api_key=fffffff&hashes=8957b8b3877913be8c1dd56043b00a72

Thanks


#2

The CSDL you specified ( links.domain in "alicemccall.com" ) compiles to a different stream hash ( ba3412e3a6702e6f25265d6f05286d5d ), suggesting you have not subscribed to the correct CSDL. Could you please ensure you have subscribed to the correct stream.


#3

I used the correct hash. Just posted the wrong one. In fact there where 50 hashes in total. {u’created_at’: u’2014-05-18 21:50:07’, u’hash’: u’43f4c48b8d62cec3e62453c61f081f8e’, u’dpu’: u’0.1’}

Here is the full url I used…

https://stream.datasift.com/multi?username=test&api_key=test&hashes=8957b8b3877913be8c1dd56043b00a72,43f4c48b8d62cec3e62453c61f081f8e,7fcc93603b476a60adfba0e43875161f,51af8479fc51afc5c889237db8dc2782,1ddad2e10529bb20136dc7a5276f40c9,b8c8144c83962a833df311024a5995f8,4ccebacf16088b5984484070ef5f09ed,a0d15738fea68b7d3a03db06ef229b50,6c15441d84752df0837b0d1fd95d6acb,d492ec765cc4ab906477d658fea20c60,6c110c94f0bda9fe67188dce35c16d17,0061412dcc9d60578bff3951868cbf73,3904d4aeb1c95d54cb45d9f3a195c47b,2d3796f70b62a643e775f7a15abc9288,907242656e98a202002f71e097a49a1c,4454bc8cd06bf3988d6b8e846400faa4,178ec1d27876c759292f1c497417c31c,fb7ea8cbb3f8088a92b34de75148ef4a,4239587be0f82e4e4559327908985634,bdb1cbf6f718b0005bd8f5e29972b182,06cb0b7114822a21d718e67d2f1012fe,5ce5fba4218cd31522804c568137d584,dd58f0b866659625d15ea6a5bcc5640b,4de21e2758e860c14f1cb3f1dc1aff77,85a1c114f66846623eae850caa5e56d3,015fe9053eaff39078ad085f3c1f3956,b668920f4be2b64e39f98408eb2e66ce,22ac806008dd3c6dc4e70ecb5f7621f7,b628bd423583948c05cc874bdda1908d,d0e6d7a65e06d75fa577ad5dcc76b6af,fe7e54ef3fbdb1846e66d5a1ae8e52dd,e0ffafce649b8760a842e3bee2948220,d3c4ebf83401f60ed7197a8bbf2b1cd0,73a84895939739c1bf40dd1a7f159683,acfae759a97d4f12a7486eb3729f0599,e902572e206e857cdbc3e908155499ed,223dcef09f38e3a1a043a281c4e34774,3cdad71373b4b1b8736c7b6a2495747f,40d9aa6fc52b79d84b8eb712c0d1b007,27adb989756e75c4e1fe1751727b4374,85a1cb2cb805e2bdcbb0c72c2925e83d,4cf4882a027b6ca338ea73a5bfd9ef78,581efc62358f0842c52fab6c1d16c309,5713383c59bf3e3b5f7a232145e3cd55,66b7c651e62ec810c94e27fa5d2f0928,dafa87126f9e04a993bd627d66155835,a00fed871ad14b2a071e80b4857a148b,1fd704ab0bb695aea22bbd54ab8cee75,81aa2db2cd27dfc3880c05058f57b9cf

So…going back to the question…why did the real time streaming pick up the tweet?

Thanks


#4

Looking at the URL you have posted, it doesn't contain the stream hash for the CSDL you originally posted. It seems to me that you might be consuming the wrong stream hash.