Ah, that's a bit annoying...
I would of though that an application being able to send notifications
to a user was a fairly common requirment.
Thanks for the advice.
On Feb 3, 6:48 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Twitter's API doesn't really support the notion of an
This is how we architected the first version of TweetPo.st back before
the streaming API was available. It was a good workaround for
regularly polling the accounts of all our users individually to know
if they had tweeted. However, we ran into the same issue with the
follower/following ratio.
The
That was exactly the problem.
Server was about 20 min ahead of twitter's time, working perfectly
now.
Thanks for the help.
On Sep 10, 2:20 pm, Colin Hill hil...@gmail.com wrote:
Angelus,
I ran into this the other day. Check the clock on your production
system and sync it to your favorite
Hi Taylor,
Thanks for the quick response. I stand corrected on the three-legged
authentication. Skipping a few steps doesn't make it 2 :)
You're right about the typo - the code I was using was incorrect.
Having fixed it, however, didn't seem to help. Here's the response I'm
getting (after the
Invalid/Expired token says it all..
Tom
On 9/9/10 11:00 PM, EranD wrote:
Thanks for the help.
Unfortunately I've already tried all of those :(
res = access_token.post(/1/statuses/update.xml, {status = Hello
tweet})
response is the same:
HTTP/1.1 401 Unauthorized\r\n
- Date: Thu, 09
Very strange. The token and access keys were all created yesterday by
twitter. Swithcing to gem 0.3.6 didn't help either.
On Sep 9, 5:08 pm, Tom van der Woerdt i...@tvdw.eu wrote:
Invalid/Expired token says it all..
Tom
On 9/9/10 11:00 PM, EranD wrote:
Thanks for the help.
Very strange. The tokens and keys were generated by Twitter yesterday
and still seem to be valid in the app interface. Switching to gem
v0.3.6 did not help.
On Sep 9, 5:08 pm, Tom van der Woerdt i...@tvdw.eu wrote:
Invalid/Expired token says it all..
Tom
On 9/9/10 11:00 PM, EranD wrote:
Yep I am seeing same problem. API return OK, but no update is made.
Any movement on this, are twitter guys aware of the issue ?
@MyAvatars
Neil Pepper
Thanks
On Jul 25, 12:24 pm, Bob movingforwa...@gmail.com wrote:
We are also seeing that the issue withprofileimage updates returning
a 200OK
Hey,
We're tracking this issue on our bug tracker. In that thread there are a
number of examples and solutions that have helped users, as well as an
explanation of how the asynchronous processing affects what is happening.
Im summary. the reason the old avatar profile image URL is being returned
We are also seeing that the issue with profile image updates returning
a 200OK but not updating the image has returned.
Please advise if you are aware of the problem / if you are working on
it.
Bob
Founder
Twibbon.com
On Jul 23, 2:28 am, Ron rbther...@gmail.com wrote:
So it looks like the
If possible, can you send along member ids or screen names, and if
possible, an HTTP capture of the image download attempt?
Thanks!
Taylor
On Wed, Jul 21, 2010 at 8:12 PM, Ron rbther...@gmail.com wrote:
Same problem seems to be back - slow/no profile image downloads.
On Jul 21, 3:14 pm, Ron
Right now it all seems back to working normally again. I'll look at
it again late this afternoon about the same time I saw the issue
yesterday. Perhaps it's time related. If it occurs again, I'll take
some captures and send them along.
On Jul 22, 10:29 am, Taylor Singletary
Hi Taylor,
Tried again this afternoon and operation appears normal, except for an
occasional profile image not loading. I find about 1 out of 200. An
example is hiro07118.
Ron
On Jul 22, 10:42 am, Ron rbther...@gmail.com wrote:
Right now it all seems back to working normally again. I'll look
So it looks like the problem is back, and perhaps time sensitive.
Servers affected are a0, a1, and a3.twing.com. Problem is no response
from server. URLs all look ok, but a few perhaps very long (i.e.
http://a3.twimg.com/profile_images/598514017/l_58bce087ff00416383ca2b5595036c90_normal.jpg).
On
I'm having the same problem too... But just sometimes.
Anyway, looks like Twitter is better now... At least is not so slow as
was a couple of weeks ago.
On Jul 21, 4:59 am, Ron rbther...@gmail.com wrote:
Anyone noticing problems loading profile images (slow, no image
returned, hanging...)?
Hi Everyone,
We had some issues with profile updates and image uploads last week
and early this week. Some images uploaded in that time period resulted
in incorrect image URLs, and while this should now be fixed for more
recently updated/created images, those with avatars saved while in
this
Dooh. I thought I changed that.
Thanks. Luckily its a test pair.
Clay
On Jul 21, 12:13 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Clay,
Just noticed that you have an API secret in this code sample you've
provided -- you'll want to go to your application record and
Taylor,
So the permission failure is on the request token. Not on the
callback, so even though my callback code is a little different it
shouldnt matter because it never gets to it.
Thanks again for catching that I posted my keys.
Clay
On Jul 21, 12:13 pm, Taylor Singletary
Ok I know what the problem is!
The manifest was blocking connections to the internet because access
was not defined. AARRRG!
Here is the proper manifest. Hope this helps somebody
Sorry
?xml version=1.0 encoding=utf-8?
manifest xmlns:android=http://schemas.android.com/apk/res/android;
So does it works completely now with manifest.xml permission in place?
uses-permission
android:name=android.permission.ACCESS_COARSE_LOCATION/
uses-permission
android:name=android.permission.ACCESS_FINE_LOCATION/
uses-permission android:name=android.permission.INTERNET/
What OAuth
Same problem seems to be back - slow/no profile image downloads.
On Jul 21, 3:14 pm, Ron rbther...@gmail.com wrote:
Not seen it happen at all anymore since corrections were made.
On Jul 21, 2:08 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Everyone,
We had some issues
OK, I managed to solve this problem. All I had to do was change the
POST to a GET.
You should use the POST HTTP method when using this end point
doesn't seem to be the case.
- Dan
On Jul 3, 4:35 pm, Daniel daniel.mcken...@gmail.com wrote:
So, I thought I'd learn a bit about Chrome extension
I downloaded the Twitter iPhone app (v. 3.0.1c) and when I use it my
geocoded tweets are showing up in the location-filtered stream. So,
seems there is Twitterrific-specific issue with location - I will pull
and compare tweets from both apps and compare them to see if I can
figure out whats
I came across this a few days ago. The problem here I believe, is that
there's some calculation going on in javascript based on the block
you're displaying it in, which in your case is not visible at all,
thus the iframe is being tagged with a 0x0 width and height. There are
two ways to solve it:
That seems to have fixed it.
Thanks a lot! I was going crazy.
On Mar 4, 3:33 pm, Thomas Woolway tswool...@gmail.com wrote:
Hi,
Tryhttps://twitter.com/statuses/home_timeline.json?since_id=9959648124
count=50
The since_id is a limiting parameter - the API will give you statuses going
back
Hi Vadim,
I see that you've filed a ticket about this too, and our Support team
should reply there soon.
Brian
On Feb 3, 11:10 am, Vadim Grekov vgi...@gmail.com wrote:
Hello! I have such problem: my accounthttp://twitter.com/MoscowTwestival
has become suspended. I can't understand why? We
Problem solved.
On Nov 3, 7:03 am, lane.montgomery lane.montgom...@gmail.com
wrote:
Hi, just signed up for the forum and posting a new topic. Gotta love
people like me, but I really need the help.
When I make a call to the API like this:
$user1results =
It would be useful to others if you posted more information about what
the solution was.
- h
On 2009-11-03, lane.montgomery lane.montgom...@gmail.com wrote:
Problem solved.
On Nov 3, 7:03 am, lane.montgomery lane.montgom...@gmail.com
wrote:
Hi, just signed up for the forum and posting a
We're getting problems on the iPhone clients again, it looks like the
old 200 error might have cropped up again of serving HTML instead of
XML too.
On Oct 18, 4:10 pm, Michael Steuer mste...@gmail.com wrote:
I only have two endpoints to test from. Hosted: fails. Home DSL: no
problem. I have
I've also been seeing intermittent connection refuses and really very
slow performance at times today.
Dewald
On Oct 19, 3:13 pm, Michael Steuer mste...@gmail.com wrote:
Hi All,
While it's not complete unreachability like yesterday morning, I'm again
experiencing, let's call it spotty
I'm also experiencing that today. It started to get slow several days ago,
but today is worse.
Regards,
Arnaldo
On Mon, Oct 19, 2009 at 5:58 PM, Dewald Pretorius dpr...@gmail.com wrote:
I've also been seeing intermittent connection refuses and really very
slow performance at times today.
I keep getting {request:/statuses/user_timeline.json?
user_id=TheUserIDcount=200,error:This method requires
authentication.}
when I try to pull a user's tweets. This never used to happen. Earlier
today I did not need to authenticate to do this.
Even when I pass my username and password, I still
Ryan,
Are you still experiencing this? I just tried several user timelines
(w/o authentication) from my home computer (outside of twitter
network) with no errors...
-Chad
On Mon, Oct 19, 2009 at 5:51 PM, Ryan Rosario uclamath...@gmail.com wrote:
I keep getting
Hi Chad,
I am still experiencing problems with this. I have tried on several
different computers, each with the same result. I am using curl to
test, but Python urllib2 returns a 401 instead.
Ryan
On Oct 19, 3:45 pm, Chad Etzel c...@twitter.com wrote:
Ryan,
Are you still experiencing this?
Not just you. Every machine I've tried times out, but
istwitterdown.com says No and Seesmic Web works. Seems to be
connectivity issue.
Sent from my iPhone
On Oct 18, 2009, at 8:40 AM, Dewald Pretorius dpr...@gmail.com wrote:
Does anyone else have problems connecting to the API at the
THANKS for posting - I've spent the last hour trying to figure this
out and since there were not reports I thought it was me.
Down from my server as well, although if I try the exact same calls
that my server (in USA) is making from my desktop (in Costa Rica) they
all return. This is what had me
I don't see any operational issues from here, but I'm not an
operational guy. At first glance the system looks fine, and the
operational team isn't in response mode. This is puzzling.
Seems like a connectivity issue upstream from twitter. At lest a few
developers: please send a traceroute to
traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
packets
1 81.b5.85ae.static.theplanet.com (174.133.181.129) 1.351 ms 1.439
ms 1.464 ms
2 et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5) 0.198 ms 0.229
ms 0.266 ms
3 et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)
From slicehost St. Louis:
traceroute to twitter.com (168.143.161.20), 30 hops max, 60 byte packets
1 174.143.199.2 (174.143.199.2) 4.000 ms 4.000 ms 4.000 ms
2 98.129.84.172 (98.129.84.172) 4.000 ms 4.000 ms 4.000 ms
3 edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115) 4.000 ms
I'm getting this from my slicehost servers.
$ traceroute twitter.com
traceroute to twitter.com (168.143.161.20), 30 hops max, 40 byte
packets
1 67-207-128-2.slicehost.net (67.207.128.2) 0.191 ms 0.165 ms
0.153 ms
2 209-20-79-2.slicehost.net (209.20.79.2) 0.704 ms 0.776 ms 0.347
ms
3
Time Warner NYC
Tracing route to twitter.com [168.143.162.116]
4 8 ms 8 ms 7 ms gig10-0-0-nycmnya-rtr1.nyc.rr.com
[24.29.157.98]
5 7 ms 8 ms 5 ms tenge-0-3-0-nwrknjmd-rtr.nyc.rr.com
[24.29.97.6]
6 6 ms 8 ms 7 ms ae-4-0.cr0.nyc30.tbone.rr.com
So somewhere before you reach twitter.com, traceroute must get
blocked. I just did a traceroute from my home (Verizon DSL) where I
can access Twitter perfectly, and traceroute still doesn't complete:
michael-steuers-computer:~ msteuer$ traceroute twitter.com
traceroute to twitter.com
So somewhere before you reach twitter.com, traceroute must get
blocked. I just did a traceroute from my home (Verizon DSL) where I
can access Twitter perfectly, and traceroute still doesn't complete:
I wouldn't read too much into that. From what I remember of Twitter's
infrastructure
We also can't connect from Chicago. I think we also lost connectivity
around 2am.
traceroute to cnn.com (157.166.255.18), 30 hops max, 40 byte packets
1 ip131.67-202-65.static.steadfast.net (67.202.65.131) 0.393 ms
0.467 ms 0.507 ms
2 te-8-2.car3.Chicago1.Level3.net (4.71.101.1) 0.332 ms
+1 can't connect from slicehost.com (I believe in St. Louis).
2009/10/18 Michael Ivey michael.i...@gmail.com:
Further info I've collected:
Can't connect from:
ATT DSL in South Alabama
ATT iPhone network
Northwest Florida, probably Comcast
Other users in Atlanta
Scoble reported various
NTT America is not responding to requests coming from certain IP
addresses.
According to my tests from a few different hosts, it seems that some
nodes of ntt.net are not relaying requests for US-based IPs, but a few
of Asian hosts that I tested from are able to reach twitter.com fine.
On Oct
+1 also can not connect to twitter api from any of our servers.
On Oct 18, 2009, at 10:32 AM, Mark Ng wrote:
+1 can't connect from slicehost.com (I believe in St. Louis).
2009/10/18 Michael Ivey michael.i...@gmail.com:
Further info I've collected:
Can't connect from:
ATT DSL in South
OK. I think we have enough traceroutes for now. Thanks for sending
them in!
If we need more datapoints or information, I'll update this thread.
On Oct 18, 7:14 am, John Kalucki jkalu...@gmail.com wrote:
I don't see any operational issues from here, but I'm not an
operational guy. At first
And here's the next question:
Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Oct 18, 7:55 am, John Kalucki jkalu...@gmail.com wrote:
OK. I think
Yes. Unable to connect via Tweetie from home (one of my traceroutes
was from home) and lots of reports from iPhone, ATT and Comcast users
in Southeast.
Sent from my iPhone
On Oct 18, 2009, at 9:56 AM, John Kalucki jkalu...@gmail.com wrote:
And here's the next question:
Is anyone
On Oct 18, 10:56 am, John Kalucki jkalu...@gmail.com wrote:
And here's the next question:
Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?
Everything works fine from my home ISP in New York.
But Twitter is
John Kalucki wrote:
And here's the next question:
Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
Yep. (comcast, cannot access through either the
This outage is now going on 7 hours. Any word from Twitter as to an
ETA for resolution?
On Oct 18, 2009, at 8:08 AM, John Meyer john.l.me...@gmail.com wrote:
John Kalucki wrote:
And here's the next question:
Is anyone having trouble from non-service, non-hosted endpoints. In
other
Completely dead from multiple ISPs (Level3 upstream) as well as ATT in
Minnesota.
Amen to that. I find it kind of curious that as per John K., 5-6 hours
into this issue, the Twitter ops team was still blissfully unaware of
anything going on... Also weird that they apparently are unable to
reproduce the issue without our help, ie. they really haven't set up
any
Desktop via Comcast, Chicago, local times:
-last successful timeline call at 3:50am
-one search query got a response, at 7am
-no access to web site
Michael D. Ivey wrote:
Yes. Unable to connect via Tweetie from home (one of my traceroutes
was from home) and lots of reports from iPhone, ATT
I wanted to check in and see if everyone is back to normal? We think
things have been fixed but its hard to confirm without your help.
Let me know if you are still experiencing any issues and if so, where
you are located.
Best, Ryan
On Sun, Oct 18, 2009 at 10:48 AM, Dewald Pretorius
I am connected via ATT DSL from Ft. Pierce, FL. I am unable to
connect with Firefox or TweetDeck. Firefox gives a time out error.
On Oct 18, 10:56 am, John Kalucki jkalu...@gmail.com wrote:
And here's the next question:
Is anyone having trouble from non-service, non-hosted endpoints. In
Dewald,
Can you produce some TCP dumps and requests with headers so we can better debug?
Thanks, Ryan
On Sun, Oct 18, 2009 at 12:05 PM, Dewald Pretorius dpr...@gmail.com wrote:
I'm seeing lots of 502's now. Is the API overloaded?
Dewald
On Oct 18, 2:58 pm, Ryan Sarver rsar...@twitter.com
Ryan,
These 502s happen in my high-volume processes. I can't manually
reproduce them.
Most calls don't 502 after the second geometric back-off.
I'm guessing it's just everyone doing a 9-hour catch-up against the
API.
Dewald
On Oct 18, 4:54 pm, Ryan Sarver rsar...@twitter.com wrote:
Dewald,
As far as i know thats correct.
blogtoilet.com
On Sep 26, 7:36 am, Patrick pkollit...@gmail.com wrote:
Hi there,
this might be obvious to everybody working longer with the API but to
me its a bit unclear:
If I call rate_limit_status from a script that I registered
I was unable to reproduce with a script. Is anyone else seeing this?
Thanks,
Doug
On Sun, Jul 26, 2009 at 7:12 PM, TjL luo...@gmail.com wrote:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-friends_timeline
lists
URL:
http://twitter.com/statuses/friends_timeline.format
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e6d8532c3ac46265/a820b56d94bda074?hl=en#a820b56d94bda074
On Wed, Apr 8, 2009 at 20:03, ben benjamin.co...@gmail.com wrote:
For confidentially reasons, I can't disclose here the niche that our
application operates in
Perhaps that was the issue with the monitter widget. However, I no
longer care because I discovered that my problem with the standard
twitter html widget was a Safari 4 bug rather than a problem with
twitter's javascript or json results generation. When viewing a page
using the widget in Safari
Sorry to hear that you're having trouble with this. Unfortunately,
this isn't the right channel to report those bugs on. Please contact
our support staff via http://help.twitter.com/. Thanks!
On Thu, Mar 5, 2009 at 05:16, raketra...@gmail.com raketra...@gmail.com wrote:
Hi. The Twitter
65 matches
Mail list logo
