I have been researching the PHP script to update the background image
of twitter profile. I found lots of code but none of them seems to be
working.
Is it really possible to do this using API?
Thanks
I have an application where I have some product listings. I would like
to auto update my status with the addition of each new product. I have
seen some of the gems and plugins that are available out there but
they seem to be too much for my limited requirement.
Has anyone seen some example code
*Yes, is possible.*
*
http://apiwiki.twitter.com/Twitter-REST-API-Method:-account
update_profile_background_imagehttp://apiwiki.twitter.com/Twitter-REST-API-Method:-account%C2%A0update_profile_background_image
*
-
Pedro Junior
2010/1/10 rohit khariwal.ro...@gmail.com
I have been researching
I had similar weird experience on January 8: started to get incorrect
signature responses from twitter. Eventually everything started to
work correctly with no code change on my part.
Would be great if there was more info on the subject...
On Dec 21 2009, 9:35 am, jdangerslater
This question is directed towards John, but happy to hear how other
folks do it as well.
I've got a couple questions regarding the tokenizing process on the
streaming API. This would be remedied pretty easily with an example
from Twitter as to their tokenizing process/regexp as I'm slightly
OK, so it looks like I misunderstood the docs, as it relates to the
punctuation.
I understood this:
Terms are exact-matched, and also exact-matched ignoring
punctuation.
to mean that if I provide a keyword with punctuation, the punctuation
will be ignored when matching. Some testing reveals that
Do the twitter servers support it?
So if I wanted to access tweets from a year ago how would I do that?
Does twitter offer development access or is this where we would need
to write to a new database for extended trending?
thanks
On Jan 9, 4:45 pm, Mark McBride mmcbr...@twitter.com wrote:
Twitter search keeps a limited amount of
Currently there isn't a way to access tweets on twitter.com that fall off
the user's timeline. You can try to grab older tweets from Google or third
parties, but understand the licensing issues.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Sun, Jan 10, 2010 at 3:38 PM,
No. We cannot support long-lived connections on the REST API. The closest
thing we have is the Streaming API.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Sun, Jan 10, 2010 at 1:59 PM, Mark Sievers mark.siev...@gmail.comwrote:
Do the twitter servers support it?
The broader track matching is indeed confusing. It errs on the side of
over-delivery. The assumption is that there is post-processing on the client
end to perform the precise filtering required. I've added a note to take
another pass at the documentation and the filtering.
-John Kalucki
that is a bit odd - what HTTP error code were you seeing? do you have a
time of day that it was occurring and do you know when it stopped?
On Sun, Jan 10, 2010 at 11:33 AM, Stas stas.ant...@gmail.com wrote:
I had similar weird experience on January 8: started to get incorrect
signature
Why does Twitter reject the Expect: 100-continue header in HTTP requests
with this self-contradictory response?
HTTP/1.1 417 Expectation Failed
Date: Mon, 11 Jan 2010 02:22:10 GMT
Server: hi
Vary: Accept-Encoding
Content-Length: 364
Connection: close
Content-Type: text/html; charset=iso-8859-1
Ditto. ETA please.
On Wed, Dec 16, 2009 at 1:22 PM, M. Edward (Ed) Borasky zzn...@gmail.comwrote:
I see that applications that authenticate with oAuth are going to get
a 10X increase in the number of API calls they can make per hour. When
does that go into effect?
--
Harshad RJ
Cool. Thanks for the reply.
On Jan 11, 11:27 am, John Kalucki j...@twitter.com wrote:
No. We cannot support long-lived connections on the REST API. The closest
thing we have is the Streaming API.
-John Kaluckihttp://twitter.com/jkalucki
Services, Twitter Inc.
On Sun, Jan 10, 2010 at 1:59
It looks like I have everything working now. The Perl library looks
OK, but I don't think the documentation on the search API page is
right:
http://apiwiki.twitter.com/Rate-limiting
An application that exceeds the rate limitations of the Search API
will receive HTTP 503 response codes to
I am already seeing some change(not 10x though) with retweets api that use
api.twitter.com/1
On Mon, Jan 11, 2010 at 9:38 AM, Harshad RJ harshad...@gmail.com wrote:
Ditto. ETA please.
On Wed, Dec 16, 2009 at 1:22 PM, M. Edward (Ed) Borasky
zzn...@gmail.comwrote:
I see that applications
Any ETA for the following. Its been a while.
http://code.google.com/p/twitter-api/issues/detail?id=1214
http://code.google.com/p/twitter-api/issues/detail?id=1274
On Tue, Jan 5, 2010 at 12:30 AM, John munz...@gmail.com wrote:
I've noticed that this is not always the case.
If I retweet an
18 matches
Mail list logo
