#10

Thanks, very helpful. I’ll update this thread when I have more info to share.

#11

Interesting, so there are actually no results that have been geocoded in the result set, so if you have changed providers, then they aren’t providing any functionality for search at the moment.

This has resulted in at least a 10x drop in results. Only a relatively small portion of people have either a lat/lon in their profile, or attached to their tweet. The above search I provided for the web search interface is mirroring the problem :

https://twitter.com/search/realtime?q=near%3Amelbourne&src=typd

Thanks!

#12

The following query…

(“:)” OR “:))” OR “:-)” OR “: )” OR “:D” OR “=)” OR “;-)” OR “;)” OR “;))” OR “:(” OR “:-(” OR “: (” OR “;-(” OR “;(” OR “;((”) AND (geocode:“50.86594,10.30086,400km”)

…was returning approx. 25.000 results / day. Since March 27th it is returning 1.000 results / day. Other geocode based query are exhibiting the same behavior making them unusable.

#13

Hi Taylor,

I’m also noticing a drop to less than 10% like everyone else, if it helps, here is another example query:

https://api.twitter.com/1.1/search/tweets.json?geocode=-31.203405%2C26.938477%2C1350km&count=100&result_type=recent&q=i’m

#14

Thanks, our search team has identified a bug that’s arose as part of the transition. It may take some time to resolve. I’ll update this thread when I have another update to share. Thanks everyone for the examples!

#15

Taylor thank you for your prompt investigation. Could you please give an example of a time frame this will be solved in, so we could have something credible for our customers/users?

#16

It looks like it won’t get resolved for about a week – hopefully quicker.

#17

Given it appears it may still take quite some time, is it possible for you to rollback the code to the known working geocoding, until this is properly resolved with the new setup? Particularly given this is seriously affecting so many services? Thanks!

#18

Am I right in assuming this issue explains why the ‘near this place’ filter on twitter advanced search is now only filtering about 10% of normal content? Is this problem effecting all users?

#19

Yes, as it seems it should be affecting all users.

#20

Many thanks for confirming that. I’m surprised there isn’t more internet chatter about this bug. There must be many developers/users pulling their hair out with frustration. At least the twitter people are ‘on the case’. Hope a solution is found sooner than a week!.

#21

We are seeing much more that 10:1 drops in the number of results. In some cases, we are seeing 50:1 drops. Practically no results.

Here’s a picture of such a case: http://twitter.yfrog.com/z/h621edp

#22

Unfortunately not, we’ll just have to wait for the fix.

#23

OK, Is there an updated ETA on this? This is seriously affecting our site (http://trendsmap.com/) along with a number of our clients, so would be great to at least have something more concrete to work with. Thanks!

#24

As soon as possible please!! Thanks.

#25

Any update on ETA to fix?

#26

Taylor, can you update us on this issue? Thanks.

#27

Any update on when this will be fixed?

#28

Has anyone seen a fix for this? Or at least as ETA?

#29

+1