The example here no works in browser, well?

lse99300548 · 2013-09-04T16:05:44.000Z

https://dev.twitter.com/docs/api/1.1/get/search/tweets the example here no works in browser, well?

episod · 2013-09-05T15:01:39.000Z

It doesn’t work in a browser because you need authentication to connect to API v1.1, and the browser can’t provide that kind of authentication.

lse99300548 · 2013-09-05T20:09:00.000Z

for what is this? Also, what is the equivalent of
http://search.twitter.com/search.json
in 1.1 in browser?

episod · 2013-09-06T14:56:55.000Z

It’s to identify the application requesting data and rate limit it appropriately.

There is no equivalent of the former unauthenticated search API for the browser.

lwdlse · 2013-09-11T08:21:00.000Z

what about use it in place of http://search.twitter.com/search.json, what to use and what params???


$(document).ready(function() {
  var searchTerm = 'celebs';
  var baseUrl = "http://search.twitter.com/search.json?q=";
  $.getJSON(baseUrl + searchTerm + "&callback=?", function(data) {
    $.each(data.results, function() {
      $('')
        .hide()
        .append('')
        .append('' + this.from_user 
          + ' ' + this.text + '') 
        .appendTo('#tweets')
        .fadeIn();
    });
  });
});

episod · 2013-09-11T15:14:54.000Z

There’s no equivalent to this kind of use of the old Search API beyond what’s available in embedded timelines.

lse99300548 · 2013-09-13T17:13:00.000Z

can you provide url least nearest to http://search.twitter.com/search.json?q=";

I do not got the chance to try code, this old gets recent tweets i guess, well what url of the knowledge base helps me get the nearer to this result? var baseUrl will differ i guess…

lse99300548 · 2013-09-14T20:53:20.000Z

I mean equivalent as of new api twitter 1.1

from 1 -to->1.1…?