It seems one can reference any valid status by id using the following
URL formula *if* you are signed in to twitter.com:
http://twitter.com/#!/this_can_be_anything/statuses/38671791899684864
but this will lead to a "sorry this page doesn't exist" if you are not
logged in. This seems like strange
hey!
Because work with 3rd party APIs is not always nice (network issues,
rate limits, complicated reproduce steps etc) I've started project
which make such tasks much easier. Sources will be available on github
- https://github.com/mlowicki/node-api-simulator . The idea is to have
local server wh
Hey Nikita,
you are one of the Greatest! It took me 2 weeks to find no solution and you
found one in 5 minutes.
So I am going to use the other number.
Thanks again.
Hajo
---
... indessen wandelt harmlos droben das Gestirn
On Sat, Feb 19, 2011 at 6:20 PM, Nikita Kovshov wrote:
> 199.16.156.1
Hajo, try to change server to 199.16.156.11
There is no problem in request.
On Feb 19, 5:09 pm, dl1sdz wrote:
> Hello,
>
> I try to code a fun project
> MorseTweeter.http://hajos-kontrapunkte.blogspot.com/2011/01/morsetweeter-v-07-is-r...
>
> After a lot of research I came back and wanted to use
Hi,
Have a loook at this code for some ideas.
This code connects
// a brute test of twittering with arduino.
// source for handling the twitter api was
http://pratham.name/post/39551949/twitter-php-script-without-curl
// the scetch lacks a lot of functionality, the encoding of username
and passw
Hello,
I try to code a fun project MorseTweeter.
http://hajos-kontrapunkte.blogspot.com/2011/01/morsetweeter-v-07-is-running.html
After a lot of research I came back and wanted to use the Arduino
standalone. But here I got stuck in formulating the query:
byte server[] = { 128, 242, 240, 148
On 2/19/11 2:23 PM, Paresh Nakhe wrote:
On going through the documentation in more detail i found this:
-> The the track parameter (keywords), and the location parameter (geo)
on the statuses/filter method are rate-limited predicates.
You can't have an infinite number of search terms.
-> Afte
On Sat, Feb 19, 2011 at 7:52 AM, Tom van der Woerdt wrote:
> On 2/19/11 1:49 PM, Paresh Nakhe wrote:
>>
>> Hi,
>> From what i understand, there is no concept of rate limiting for
>> streaming api. Actually it does make sense because if anyone is to use
>> 'statuses/sample' method (say) the limit
On going through the documentation in more detail i found this:
-> The the track parameter (keywords), and the location parameter (geo) on
the statuses/filter method are rate-limited predicates.
-> After the * limitation period* expires, all matching statuses will once
again be delivered, along w
On 2/19/11 1:49 PM, Paresh Nakhe wrote:
Hi,
From what i understand, there is no concept of rate limiting for
streaming api. Actually it does make sense because if anyone is to use
'statuses/sample' method (say) the limit will soon be crossed. We are
working on something that will heavily use th
Hi,
>From what i understand, there is no concept of rate limiting for streaming
api. Actually it does make sense because if anyone is to use
'statuses/sample' method (say) the limit will soon be crossed. We are
working on something that will heavily use the streaming api, so if rate
limiting is im
11 matches
Mail list logo
