fabiobarrinovo / otterapi Goto Github PK

What steps will reproduce the problem?
1. curl 'http://otter.topsy.com/search.json?q=flattr&window=d&perpage=50&page=3'

What is the expected output? What do you see instead?
Since this happens to be the last page of results (at the time of writing), I 
expect that whatever the last_offset is, it should be equal to the total. But 
it is less than the total - and indeed, the last_offset given is consistent 
with the number of items returned on this page, indicating that about 10 
results are missing from the resultset.

What steps will reproduce the problem?
1.$ curl  'http://otter.topsy.com/search.json?q=from:suncicakaric&window=a'
2.
3.

What is the expected output? What do you see instead?
There is 'from:' in query, but 90% of returned tweets are NOT from 
suncicakaric. Most of them are tweets that suncicakaric retweeted.

Also as trackback_nik stands twitter user that did not write that tweet.
Example: "trackback_author_nick":"suncicakaric","content":"Out of the 500 U.S. 
billionaires 98% come from millionaire or billionaire families."

Also for that tweet stands url as suncicakaric wrote it 
"trackback_permalink":"http://twitter.com/suncicakaric/status/183665671677284352
 and that url resolves to 
https://twitter.com/InjusticeFacts/status/183664996239147008 so it is totally 
inaccurate.

What version of the product are you using? On what operating system?
Tested on Linux and Windows using PHP.

Please provide any additional information below.

What steps will reproduce the problem?
1. When all the tweets are required to be stored in a database sorted datewise.
2.
3.

What is the expected output? What do you see instead?
Tweets are expected to be sorted. But getting tweets sorted pagewise only.

What version of the product are you using? On what operating system?
Windows.

Please provide any additional information below.
I want tweets of all the dates. So when I try to get tweets of a particular 
date using mindate=2013-01-01&maxdate=2013-01-01 it still shows tweets of 1 day 
ago, 2 days ago & all.

What steps will reproduce the problem?
1. Mr.A tweets something. eg: "I'm Mr.A, posted a new article in my blog 
http://exsample.com/article1"
2. Mr.B retweets.
3. Get twitter trackbacks about "http://exsample.com/article1" by 
otterapi(trackbacks.json).
4. otterapi returns as Mr.B tweeted "I'm Mr.A, posted...".
   ("Author" is Mr.B, no mention about Mr.A anywhere).

What is the expected output? What do you see instead?
Mr.B retweeted Mr.A's tweet is the expected output.

What version of the product are you using? On what operating system?
http://otter.topsy.com/trackbacks.json

Please provide any additional information below.

What steps will reproduce the problem?
Searchcount is not reporting all hashtag mentions:
http://otter.topsy.com/searchcount.json?q=%23LewisAustralia&type=tweet

What is the expected output? What do you see instead?
The results should be at least 600 when the api is only returning 297.

I suspect this may have something to do with Topsy displaying 'Mentions That 
Matter'. Is it possible to retrieve ALL results?

Please remove.

Would be nice to clean the irrelevant comments from the Resources wiki page as 
well.

I use the following code

$.getJSON("http://otter.topsy.com/searchcount.json?q=from:"+username+"&callback=
?", 
    function(data){ }
);

but, the error comes: 
Uncaught SyntaxError: Unexpected token : in line 1...

I believe that the final numbers here:
"response":{"w":38,"h":0,"a":1049,"d":2,"m":126}}

must be
"response":{"w":"38","h":"0","a":"1049","d":"2","m":"126"}}

or not?

http://code.google.com/p/otterapi/wiki/Resources?tm=6#/urlinfo

"oneforty" : "Twitter: What are you doing? http://twurl.nl/pd8k44",

Please tell me what does 'oneforty' mean.

What steps will reproduce the problem?
1. curl "http://otter.topsy.com/linkposts.json 
url=http://twitter.com/bbrinck&mintime=1286696632"

What is the expected output? What do you see instead?

I expect that the tweets will be restricted to those tweets created after the 
mintime.

Instead, I see the same list of tweets as if I had omitted the mintime 
parameter. The documentation for linkposts indicates is supports all the List 
Parameters described at http://code.google.com/p/otterapi/wiki/ResListParameters

What version of the product are you using? On what operating system?

I am using the version deployed at http://otter.topsy.com

Please provide any additional information below.

Please provide any additional information below

http://topsy.com/twitter/jinpinlongxing

Can you remove this cache pages please?

What steps will reproduce the problem?
1. Run 
http://otter.topsy.com/search.json?window=a&allow_lang=en&q=loving+blueseed&type
=tweet - no results
2. Remove the allow_lang=en parameter, re-run: 
http://otter.topsy.com/search.json?window=a&q=loving+blueseed&type=tweet - one 
result, in English

Some searches seem to no longer be returning a list property, Instead they just 
return a blank success and error properties.

For either of these searches of whitney,
http://otter.topsy.com/search.js?type=image&q=whitney&perpage=100&offset=200
http://otter.topsy.com/search.js?type=image&q=whitney&perpage=100&page=2

which should have way more than 200 results, are returning this result
{"request":{"parameters":{"q":"whitney","type":"image","offset":"200","perpage":
"100"},"response_type":"json","resource":"search","url":"http://otter.topsy.com/
search.json?offset=200&perpage=100&q=whitney&type=image"},
"response":{"errors":"","status":""}}

This seemed to start happening around the 4/18 system maintenance - 
http://status.topsy.com/performing-system-maintenance.

What steps will reproduce the problem?

1.
Access to the URL below.
http://otter.topsy.com/search.json?q=%E3%83%AD%E3%83%B3%E3%82%B0%E3%83%88%E3%83%
AC%E3%82%A4%E3%83%AB&maxtime=1367068860&mintime=1367068740&apikey=[Your API-Key]

2.
You will get response like [actual response] written bellow.
 -> "content" value of the response is empty.

3.
Access to the URL below which is contained in the response as 
"trackback_permalink"
http://twitter.com/hikermasa/status/328136687081373696

4.
The tweet has text. Nevertheless "content" of [actual response] is empty.

Doesn't "content" represent the text of tweet indicated by 
"trackback_permalink"?


What is the expected output? What do you see instead?
[expected response]
{
    "request": {
       ........
    }, 
    "response": {
        "hidden": 0, 
        "last_offset": 1, 
        "list": [
            {
                "content": "皆さんが、早めに紹介されておりましたので、タイミングをずらしてお知らせします。........", 
                ........
                ........
               "trackback_permalink": "http://twitter.com/hikermasa/status/328136687081373696", 
                "trackback_total": 1, 
                "url": "http://fb.me/2CxwUllgl"
            }
        ], 
       ........
    }
}

[actual response]
{
    "request": {
        "parameters": {
       ........
    }, 
    "response": {
        "hidden": 0, 
        "last_offset": 1, 
        "list": [
            {
                "content": "", 
                ........
                ........
                "trackback_permalink": "http://twitter.com/hikermasa/status/328136687081373696", 
                "trackback_total": 1, 
                "url": "http://fb.me/2CxwUllgl"
            }
        ], 
       ........
    }
}

What version of the product are you using? On what operating system?


Please provide any additional information below.
This phenomenon also occurs with other request condition.

I'm using otterapi 4j warpper i'm getting a rate limiting even if i have got a 
new free api key with manager http://manage.topsy.com/app/


it seems that topsy team take time to active this api key 

is that true ??

what can i do ??

thanks 

What steps will reproduce the problem?
1. $ curl 
'http://otter.topsy.com/searchdate.json?q=flattr&window=m&perpage=50&page=3'

What is the expected output? What do you see instead?
I expect some results, because I am only on page 3 and there are supposed to be 
4412 results in total, according to that output, but there are no results. Page 
2 is the last page that contains any results.

What steps will reproduce the problem?
1. in python:
import urllib2
temp = urllib2.urlopen('http://otter.topsy.com/search.json?q="Netflix customers 
see red after price hike"&window=h3')

2. you will get a 400 error
3. but if you type the url in the browser:
http://otter.topsy.com/search.json?q="Netflix customers see red after price 
hike"&window=h3
you get a json file with the correct results.

What is the expected output? What do you see instead?
I expect to get the same response from both methods. it seems that there is a 
bug and your system gives a 400 error to urlopen2

What version of the product are you using? On what operating system?
python 2.6.5
linux

Please provide any additional information below.

This just started happening on 3/20.

https://code.google.com/p/otterapi/wiki/Resources should list the name of the 
API key parameter, 'apikey'.

Topsy rightly considers www.domain.com and domain.com to be different sites, 
but definitely has a mechanism for knowing when one redirects to the other. I 
can't figure out a way to trigger it.

If you access http://otter.topsy.com/trackbacks.json?url=http://www.topsy.com/. 
The response begins with 
{"request":{"parameters":{"orig_url":"http://www.topsy.com/","redirected_url":"h
ttp://topsy.com/","url":"http://topsy.com/"}. I'm trying to achieve the same 
effect for my domain (borismus.com, formerly www.borismus.com).

What steps will reproduce the problem?

1. Visit http://otter.topsy.com/trackbacks.json?url=http://borismus.com/
2. Visit http://otter.topsy.com/trackbacks.json?url=http://www.borismus.com/
3. Note the difference.

What is the expected output? What do you see instead?

I'd expect topsy to notice the 301 redirect from my www to the non-www domain, 
and respond with a similar "redirected_url" response, effectively giving the 
same response for both requests in (1) and (2).

What version of the product are you using? On what operating system?

Using the currently live otter API (as of 2010-02-10).

What steps will reproduce the problem?
1. Conduct a /search query
2. Add the mindate/maxdate optional parameters (in Unix date format)

What is the expected output? What do you see instead?
Expect a JSON response containing tweets only within specified dates, but 
instead getting tweets from what seems like random dates all the way back to 
2009

What version of the product are you using? On what operating system?
Topsy Otter on Max OSX

Please provide any additional information below.

What steps will reproduce the problem?
1. Search for query 
"http://otter.topsy.com/search.json?q=vodafone&mintime=1324385400&maxtime=132438
7203&order=date&perpage=100" and 
http://otter.topsy.com/search.json?q=vodafone&type=tweet&mintime=1324385400&maxt
ime=1324387203&order=date&perpage=100
2. In the second query &type=tweet is added
3.

What is the expected output? What do you see instead?
By specifying "type" we are getting more results and also there are tweets 
which are present in first and not in second as well as tweets present in 
second and not in first (and count of such tweets are high)

What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1. Call 
http://otter.topsy.com/search.json?window=d10&nohidden=1&q=blueseed&type=tweet&p
erpage=40
2. At the moment, the response lists a "total" of 35, but only 28 results are 
returned. "last_offset" is also 28.

What is the expected output? What do you see instead?
"nohidden" was set to 1, so this looks like a bug. The window was only 10 days.

What steps will reproduce the problem?
1. REMOVE the link from the internet 
2. http://topsy.com/tb/twitpic.com/12ioh9 PLEASE REMOVE THIS LINK!! 
3. Please remove the link

What is the expected output? What do you see instead?
Please remove this page from the internet!! THis picture was posted without my 
consent. 

What version of the product are you using? On what operating system?


Please provide any additional information below.

When I search using the otter api for any tweet that is longer than 112 
characters I get 112 characters followed by ...

Is there some way I can get the remaining 28 characters?

Just a feature request, that I can include &callback=my_callback to wrap the 
data so it's JSONP and 
usable from client side requests:

my_callback(topsy_data)

I can see a number of apps I'd like to pull together that could use this.

Cheers,

Remy.

1. I tried to look up the list of tweets (trackbacks) that mention the query 
URL 
http://otter.topsy.com/trackbacks.json?url=https://epetitionen.bundestag.de/inde
x.php?action=petition;sa=details;petition=3860

2. Topsy only looks up 
https://epetitionen.bundestag.de/index.php?action=petition without the 
additional characters after the semicolon

3. I encoded the URL into 
https%3A%2F%2Fepetitionen.bundestag.de%2Findex.php%3Faction%3Dpetition%3Bsa%3Dde
tails%3Bpetition%3D3860 but topsy still doesn't change its response.

Is this a known or wanted issue?

What steps will reproduce the problem?
1.443
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

http://code.google.com/p/otterapi/wiki/Resources#/search

"Time window for results. (default: json"

The description of the "window" parameter could be improved like this:

<<
Time window for results. (default: dynamic)
Options:
* h - last hour
* hN - last N hours
* d, dN - last (N) day(s)
* w, wN - last (N) week(s)
* m, mN - lsat (N) month(s)
* a - all time
* dynamic - will pick the most relevant window. Possible responses are 1-23 
hours or 1-100 days. For example: h6 or d10.
* auto (DEPRECATED) - automatically pick the most relevant window. This will 
return one of the standard h,d,w,m,a window values.
>>

What steps will reproduce the problem?

Take a look at this request:

http://otter.topsy.com/trackbacks.json?
beta=zw5lcmf&url=http://ekstrabladet.dk/sport/fodbold/udenlandsk_fodbold/ty
skfodbold/article1212875.ece

What is the expected output? What do you see instead?

The response is utf-8 encoded which I believe is correct, but I'm seeing 
strange character encoding i the content-field like : "Bayern München og 
Real Madrid er enige: Arjen Robben skal fortsætte karriere." 

What version of the product are you using? On what operating system?

Latest

Please provide any additional information below.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1. request 
http://otter.topsy.com/search.json?perpage=100&order=date&q=riot&page=1&offset=0
&mintime=1312516800&maxtime=1312776000

2. 
http://otter.topsy.com/search.json?perpage=100&order=date&q=riot&page=2&offset=1
00&mintime=1312516800&maxtime=1312776000

The result says there are over 1700 posts, but page 2 returns nothing.

What is the expected output? What do you see instead?
I would expect the result to continue up until the limit of 10 pages.

This query works correctly without the "order=date"