REST API v1
If a one word username (i.e. twitterapi) is searched, the resulting set could be:
1) A tweet originating from said author
2) A tweet mentioning that author (i.e. @twitterapi)
3) A tweet with a hashtag reference of that author (i.e. #twitterapi)
4) A Tweet that contains the author's handle in the body text
If a username is searched that contains and underscore then the underscore is treated as a space in the query string. Therefore, "nikerun_jp" becomes "nikerun jp" completely distorting the search results. Omitted results include:
1) A tweet originating from said author
2) A tweet mentioning that author (i.e. @nikerun_jp)
3) A tweet with a hashtag reference of that author (i.e. #nikerun_jp)
4) The exact match of the author's handle in the tweet
Therefore, in order to capture all of the results for a username search that contains an underscore one query must be broken out to contain a search for:
3) "nikerun jp" <---- aka "nikerun" & "jp"
and even then the exact match "nikerun_jp" is not returned by the search...
Please advise on any possible fix for the search mechanism or workaround solution for the underscore problem...
Thank You in Advance,
Yep... searching for my username has been utterly useless the last couple of weeks.
The frustrating part is nothing is done to prune inactive usernames unless it's trademarked, and the official support documents suggest adding underscores when your desired username is not available, however they make no mention of the fact that search won't return meaningful results if the query contains an underscore.
I think the best that can presently be done is to search for from, to, or mentioning: "from:The_Qwerty OR to:The_Qwerty OR @The_Qwerty"
Would be nice if Twitter, Feedback, Support, or twitterpi would at least acknowledge whether this change is a bug or part of an initiative to decrease the number meaningful results from a query.
This is surely something that must be adressed soon?
I have the same problem with the search: from:equilibrio_
Hi all, we're working to resolve this but it will take a few steps. Expect the full resolution sometime next week.
We are also experiencing this with one of our clients @Edinburgh_.
Would be grateful if you could let us know when this is fixed.
Andrew Weddle (Innovation Digital)
Hi, I recently came opun this topic when one of my friends sent it to me. I am called Jebs_Helper because I help someone named @jeb_ with their mentions. I can't do this anymore, because of how the searching works. You could use the same code as Google when searching, and have spaces be a "+" in the URL bar and not an "". Because if I search @jeb to see his mentions, I mainly only get mentions from @jeb. Again, my suggestion is above.
Thanks if you read this twitter....
Strange.... The underscore only worked once... I meant to have an underscore the first time it says @jeb (not @jeb[underscore), and in the empty quotation marks.
Hi Taylor, do we have any idea when this issue maybe resolved? Just an indicative 'we've no idea what's going on, argh' or 'we've got a handle on it, give it a couple of days' would suffice otherwise we're going to have to alter our code to consume the results.
The first part of this issue should be resolved:
The second part of this issue will be resolved within the next week or two:
- searching for users with underscores in the username through: users/search
If there's another aspect to this bug that I'm not aware of, please describe clearly with examples of executed API URLs and how the response doesn't jive with what you're expecting. Thanks!
What about searching usernames as search terms (w/o "@") through search.twitter.com without specifying "from:"?
http://search.twitter.com/search.json?q=jaguarusa&rpp=100 will return tweets FROM @JaguarUSA without the need to specify "from:"
http://search.twitter.com/search.json?q=roi_media&rpp=100 does not return tweets from @ROI_Media unless the query is rewritten to include "OR from:ROI_Media" .
The underscore is still omitted when a username is treated as a search term resulting in the AND logic to occur for the terms separated by the underscore.
Still getting no results from this query :
Thanks, I'll let the team know there are still some failing cases.
Hello, Seems the problem with searches like " from:useraname_ " doesn't be solved yet, please keep us posted
Hey Taylor, do you have any news on this? I'm also still having problems with trailing underscores: e.g. http://search.twitter.com/search.json?q=from:radian_&rpp=3 returns results for user @radian instead of @radian_
Still getting no results from this query http://search.twitter.com/search.json?q=from%3AEdinburgh_
Also searching Twitter using Hootsuite for @edinburgh_ only produces results for @edinburgh
Any news on when this will be fixed?
No update yet when this will be fixed. Will continue working on getting this prioritized.
Any update on this please? Getting a bit desperate now.....
as am I ... is there a planned fix for this, pls ?
next page →