Sorry, I was wrong. In fact the hashtag was : #dsexperiment ; I assume it’s a kind a filtering from twitter. Can we have a clear idea of what kind of hashtag we should ‘prevent’ from our user ?
Dears,
Some tweets can’t be found from the API (search/streaming) when a user created an account a few hours ago.
Here is a tweet : https://twitter.com/BierCrow/status/587669512637382656, tagged with #dsexperiment
Let me know if you need more testing, i’ll do that gladly since we use your api for business purpose.
Here is an apigee response from a classic request searching for dsexperiment term :
HTTP/1.1 200 OK
x-frame-options:
SAMEORIGIN
content-type:
application/json;charset=utf-8
x-rate-limit-remaining:
179
last-modified:
Mon, 13 Apr 2015 17:53:28 GMT
status:
200 OK
x-response-time:
27
date:
Mon, 13 Apr 2015 17:53:28 GMT
Connection:
keep-alive
x-transaction:
8a1ce82265f57f70
pragma:
no-cache
cache-control:
no-cache, no-store, must-revalidate, pre-check=0, post-check=0
x-connection-hash:
90ffe6ab9ac7964f852688b5cc75fa8d
x-xss-protection:
1; mode=block
x-content-type-options:
nosniff
x-rate-limit-limit:
180
expires:
Tue, 31 Mar 1981 05:00:00 GMT
set-cookie:
lang=en
set-cookie:
guest_id=v1%3A142894760879779457; Domain=.twitter.com; Path=/; Expires=Wed, 12-Apr-2017 17:53:28 UTC
content-length:
262
x-rate-limit-reset:
1428948508
content-disposition:
attachment; filename=json.json
server:
tsa_b
x-twitter-response-tags:
BouncerCompliant
strict-transport-security:
max-age=631138519
x-access-level:
read-write-directmessages
{
“statuses”: [],
“search_metadata”: {
“completed_in”: 0.01,
“max_id”: 587674898971111400,
“max_id_str”: “587674898971111424”,
“query”: “dsexperiment”,
“refresh_url”: “?since_id=587674898971111424&q=dsexperiment&include_entities=1”,
“count”: 15,
“since_id”: 0,
“since_id_str”: “0”
}
}
Sadly nothing come back
