This was report and is being tracked by issue 582:
http://code.google.com/p/twitter-api/issues/detail?id=582
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On Thu, May 14, 2009 at 7:28 PM, elversatile elversat...@gmail.com wrote:
I have Data Mining public
Hi I`m getting strange errors on using update_profile_background_image
API call (see curl dump below)
The uploaded image size is 10Kb.
Also i`ve tried to use
mqpro_glowdotsGray.br.jpg;type=image/jpeg
and
mqpro_glowdotsGray.br.jpg;type=image/jpg
notations and go the same result.
Using the
And you can check on the progress of that Status ID on: www.twitpocalypse.com
Unless Twitter decides to blacklist us) for sending too many requests
to the public timeline API...
So Twitter, if you do so, please send me an email martin [insert at]
wherecloud [dot] com so we can work something out
Hey guys,
is anybody else having this problem? I have two apps registered at
Twitter. Both are working fine with OAuth. I can access (read/write)
data from Twitter.
While the first app shows “from source” correctly, the second app
doesnt.
Instead of “from source” it shows “from web”.
Maybe a
Is the created_at return value of http://twitter.com/statuses/friends.format
the date that person's Twitter account was created, or the date that
friendship began?
My guess is it is when the twitter account was created. If that is so, then
is there a way to determine the date someone started
On Thu, May 14, 2009 at 10:32 PM, TweetClean tweetcl...@gntmidnight.comwrote:
I see that there is the ability to remove people I am following using
the friendships/destroy API call. How do I remove someone who is
following me? I am sure it is right in front of my eyes but I am not
making
The fix seems to work from a link on an insecure page, but not from a
secure page. Any thoughts?
Thanks,
Sue
On Apr 30, 7:13 pm, John Adams j...@twitter.com wrote:
On Apr 30, 2009, at 4:00 PM, Matt Sanford wrote:
Hi there,
We're working on getting that fix out right now. I was
I've noticed this before but always tried to deal with it as a bug on
my side. It is, however, now clear to me that from time to time
Twitter Search API seems to ignore the since_id.
We track FollowFriday by polling Twitter Search every so often (the
process is throttled from 10 seconds to 180
Hilarious!
--
Patrick Burrows
http://Categorical.ly (the Best Twitter Client Possible)
@Categorically
-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Martin
Dufort
Sent: Friday, May 15, 2009 10:08 AM
Hi Brian,
My guess is that this is the same since_id/max_id pagination
confusion we have always had. If you look at the next_page URL in our
API you'll notice that it does not contain the since_id. If you are
searching with since_id and requesting multiple pages you need to
manually
Hi there,
A bug was re-introduced with the ?status parameter. I noticed it
yesterday on the replies link on search.twitter.com and we've got a
fix ready to go out with our next deploy. Sorry for the inconvenience.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On May 15, 2009,
So. Much twitter documentation talks about “140 characters” and “160
characters limit”. But “character” is not a raw data type, it’s a
string type. It has been observed[1][2][3][4] that 1) twitter expects
these characters to be encoded as UTF-8 (or ASCII, which is a strict
subset of UTF-8),
That value is the date that the account was created as you determined. There
is no way to determine programmatically when the account was followed. That
is not something we expose in the API.
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On Fri, May 15, 2009
On Fri, May 15, 2009 at 12:07 PM, Matt Sanford m...@twitter.com wrote:
Hi there,
A bug was re-introduced with the ?status parameter. I noticed it
yesterday on the replies link on search.twitter.com and we've got a fix
ready to go out with our next deploy. Sorry for the inconvenience.
Matt - I'll verify that is the issue (I assume I should have new
results on page one AND page 2 - otherwise there is something else
going on).
Brian
On May 15, 8:33 am, Matt Sanford m...@twitter.com wrote:
Hi Brian,
My guess is that this is the same since_id/max_id pagination
Matt -
That took care of it... minor change on my side with big resource
savings. Where was the original announcement made that this had
changed (wondering how I missed it).
Thanks!
Brian
On May 15, 8:33 am, Matt Sanford m...@twitter.com wrote:
Hi Brian,
My guess is that this is the
Hi Brian,
This has always been the case, that thread I linked to earlier is
where I made it more explicit. It was always there but it wasn't
documented properly. The documentation was updated as well to try and
help in the future.
Thanks;
– Matt Sanford / @mzsanford
Twitter
I'm using a bigint (20) with MySQL for TwitteReader so
18446744073709551615 available. Still many IDs to go ;)
On May 15, 2:03 pm, leoboiko leobo...@gmail.com wrote:
while one with 71 UTF-8
bytes might not (if they’re all non-GSM, say, ‘ç’ repeated 71 times).
Sorry, that was a bad example: 71 ‘ç’s take up 142 bytes in UTF-8, not
71.
Consider instead 71 ‘^’ (or ‘\’, ‘[’ c.). These take one byte in
I'd be interested to see a document that details the standards for
this as well.
On May 15, 12:01 pm, leoboiko leobo...@gmail.com wrote:
On May 15, 2:03 pm, leoboiko leobo...@gmail.com wrote:
while one with 71 UTF-8
bytes might not (if they’re all non-GSM, say, ‘ç’ repeated 71 times).
Hi I`m getting strange errors on using update_profile_background_image
API call (see curl dump below)
The uploaded image size is 10Kb.
Also i`ve tried to use
mqpro_glowdotsGray.br.jpg;type=image/jpeg
and
mqpro_glowdotsGray.br.jpg;type=image/jpg
notations and go the same result.
Using the
I'm having the same problem as Jesse using the Net::OAuth
Here's what I get back from twitter:
$VAR1 = bless( {
'_protocol' = 'HTTP/1.1',
'_content' = 'Failed to validate oauth signature or
token',
'_rc' = '401',
'_headers' =
22 matches
Mail list logo
