Bulk add would be great. Here’s a log from doing individual adds.
Notice there were many over capacity errors. And that it took about a
minute 42 to add about 60 users. If I could do all in one request,
perhaps that would help reduce the over capacity errors.
I’m enjoying lists. Thanks for the fe
Multiple identical list create requests result in multiple lists,
differing in slug/url/full name.
Perhaps it should ignore, or return an error?
$ curl -u dcbriccetti -d "name=Scala" http://twitter.com/dcbriccetti/lists.xml
29926
Scala
@dcbriccetti/scala-2
scala-2
...
$ curl -u dcbricc
> On Sat, Oct 17, 2009 at 10:41 AM, Marc Mims wrote:
> > Updates longer than 140 characters should be forcibly truncated
> > according to the documentation. Instead, the update call returns with
> > a 200 status and the payload contains the prior update.
> >
> > Has there been a change to the AP
Yes, that is the one I mean.
Well I am on the developer website because I found it through Google.
And while I certainly know my way around HTML and CSS, any kind of
programming is beyond the scope of my brain, so no I could not make my
own widget without a lot of help.
My widget didnt stop work
Hi, I'm doing a Flash app using the Twitter Search API. In the ATOM
feed there's a node containing the profile photo url. However for some
users, when I try to get the photo I get a XML file similar to this:
AccessDenied
Access Denied
661A5450F0C3BC24
ZeVGawzEJVrKbgYDsRcNL2SWO
Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?
Dewald
Yes, not connecting at all here. Kust timing out.
On Oct 18, 2009, at 6:40 AM, Dewald Pretorius wrote:
Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?
Dewald
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 wrote:
Does anyone else have problems connecting to the API at the moment
(Sunday mor
In fact, looking at my logs, the API was down since at least 2 AM
Pacific (5 hours ago)...
On Oct 18, 2009, at 6:40 AM, Dewald Pretorius wrote:
Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?
Dewald
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 s
Further info I've collected:
Can't connect from:
- AT&T DSL in South Alabama
- AT&T iPhone network
- Northwest Florida, probably Comcast
- Other users in Atlanta
- Scoble reported various flakiness
- Servers at Slicehost in the St Louis datacenter
Can connect from:
- Blackb
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 this
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) 0
On my end: my server (at Rackspace) can't connect to twitter.com... If I
enter API URLs into my browser at home (Verizon DSL), I connect just fine.
Here's a traceroute from rackspace:
traceroute twitter.com
traceroute to twitter.com (168.143.161.20), 30 hops max, 60 byte packets
1 xxx-xxx-xxx-xx
>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
Tracert disabled from host - fail!
But I assume that if we can't reach you, you should not be able to
reach us either? My server's IP is 174.120.0.108 (The Planet)
On Oct 18, 8:14 am, John Kalucki wrote:
> I don't see any operational issues from here, but I'm not an
> operational guy. At first g
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 ge
I'm not able to connect to twitter via any interface or software.
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
[66.109.
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 (128.121.146
> 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 (IDNSO
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 :
> Further info I've collected:
>
> Can't connect from:
>
> AT&T DSL in South Alabama
> AT&T iPhone network
> Northwest Florida, probably Comcast
> Other users in Atlanta
> Scoble reported various flakiness
> S
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 18
Will someone from Twitter please respond if there is an ETA to resolve
this issue. Work arounds can never be really as effective as the real
deal.
+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 :
Further info I've collected:
Can't connect from:
AT&T DSL in South Alabama
AT&T iPhone networ
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 wrote:
> I don't see any operational issues from here, but I'm not an
> operational guy. At first glance the system lo
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 wrote:
> OK. I think we have enough trac
Yes. Unable to connect via Tweetie from home (one of my traceroutes
was from home) and lots of reports from iPhone, AT&T and Comcast users
in Southeast.
Sent from my iPhone
On Oct 18, 2009, at 9:56 AM, John Kalucki wrote:
And here's the next question:
Is anyone having trouble from non
Me either. All sources say Twitter.com doesn't seem to be "down" but I
can't get anything from the site.
On Oct 18, 10:56 am, 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?
Everything works fine from my home ISP in New York.
But Twitter is completely inaccessible
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
I only have two endpoints to test from. Hosted: fails. Home DSL: no
problem. I have several iPhone clients, but I'm bot sure if they're
proxies or connect to the API directly...
On Oct 18, 2009, at 7:56 AM, John Kalucki wrote:
And here's the next question:
Is anyone having trouble fr
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 wrote:
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 I
I'd be more than happy to wait longer for snazzy API 2.0 features so
that the Platform team can build a QoS system that monitors the API's
availability and performance from the outside. That will enable
Twitter to catch these kinds of issues long before we do.
Dewald
On Oct 18, 12:47 pm, Michael
Completely dead from multiple ISPs (Level3 upstream) as well as AT&T 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 monitori
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, AT&
I'm having problems with my code because it looks like the search
method is returning the created_at date in the following format: Fri,
16 Oct 2009 16:40:25 +
Everything else, and the documentation is using this format: Tue Feb
24 16:38:44 + 2009
Is this being fixed?
> I'm having problems with my code because it looks like the search
> method is returning the created_at date in the following format: Fri,
> 16 Oct 2009 16:40:25 +
>
> Everything else, and the documentation is using this format: Tue Feb
> 24 16:38:44 + 2009
>
> Is this being fixed?
Yes
Just for the record, +1 from Slicehost in St. Louis and Rackspace in
Dallas. It's been happening since around 4am central.
Hayes
On Sun, Oct 18, 2009 at 11:30 AM, Michael Steuer wrote:
>
> Amen to that. I find it kind of curious that as per John K., 5-6 hours into
> this issue, the Twitter op
I don't really blame Twitter Ops for not knowing. It's probably a new
edge defense that was installed by their service provider during
Sunday night.
However, a while ago Alex said the Platform team were working on an
external monitoring solution. Hopefully Ryan, who is now Director of
the Platfor
The situation seems to have been resolved, at least for me, as of a
few minutes ago. My Rackspace hosted servers can reach the API again...
On Oct 18, 2009, at 10:35 AM, Dewald Pretorius wrote:
I don't really blame Twitter Ops for not knowing. It's probably a new
edge defense that was i
Same here. Can connect again.
On Oct 18, 2:46 pm, Michael Steuer wrote:
> The situation seems to have been resolved, at least for me, as of a
> few minutes ago. My Rackspace hosted servers can reach the API again...
>
> On Oct 18, 2009, at 10:35 AM, Dewald Pretorius wrote:
>
>
>
> > I don't r
Setting up external monitoring isn't a huge undertaking. Their are
plenty of existing services out there already. Even free ones like pingdom.com
. Perhaps Twitter should set up a couple of those until they have
their full QoS implementation in place. Pingdom for example would have
started
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 wrote:
>
>
Works Fine... Duluth, MN.
On Sun, Oct 18, 2009 at 12:51 PM, Ryan Sarver wrote:
>
> 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
>
It is working for me. Would you mind sharing with the group what
exactly happened?
Thanks.
Michael
On Oct 18, 2009, at 10:53 AM, Atul Kulkarni
wrote:
Works Fine... Duluth, MN.
On Sun, Oct 18, 2009 at 12:51 PM, Ryan Sarver
wrote:
I wanted to check in and see if everyone is back t
I am now able to connect to twitter here in Wisconsin. ISP is TDS
Josh
Michael,
We are still working on getting the full picture, but once we have the
details I will report to the group what the issue was.
Thanks for updating us.
Best, Ryan
On Sun, Oct 18, 2009 at 10:55 AM, Michael Steuer wrote:
> It is working for me. Would you mind sharing with the group what
Twitter just came back 2 minutes in Chicago.
On Oct 18, 1:51 pm, Ryan Sarver wrote:
> 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.
I think everything is back to normal now. This is a very useful site
to ping Twitter from around the world:
http://j
We're back in action from Slicehost in St. Louis and Rackspace in Dallas.
Hayes
On Sun, Oct 18, 2009 at 12:58 PM, Ryan Sarver wrote:
>
> Michael,
>
> We are still working on getting the full picture, but once we have the
> details I will report to the group what the issue was.
>
> Thanks for up
I'm seeing lots of 502's now. Is the API overloaded?
Dewald
On Oct 18, 2:58 pm, Ryan Sarver wrote:
> Michael,
>
> We are still working on getting the full picture, but once we have the
> details I will report to the group what the issue was.
>
> Thanks for updating us.
>
> Best, Ryan
>
> On Sun
On Sun, Oct 18, 2009 at 8:09 AM, vivekpuri wrote:
>
> Will someone from Twitter please respond if there is an ETA to resolve
> this issue. Work arounds can never be really as effective as the real
> deal.
Sorry, I thought it was clear from the previous email. There is no ETA
because it's not goi
I am connected via AT&T 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 wrote:
> And here's the next question:
>
> Is anyone having trouble from non-service, non-hosted endpoints. In
> other words, probl
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 wrote:
>
> I'm seeing lots of 502's now. Is the API overloaded?
>
> Dewald
>
> On Oct 18, 2:58 pm, Ryan Sarver wrote:
>> Michael,
>>
>> We a
Thanks, but still failing today.
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 wrote:
> Dewald,
>
> Can you produce
The change has been made but it probably hasn't been pushed out yet to
the full cluster. I'll follow up with ops on Monday. Thanks.
On Sun, Oct 18, 2009 at 1:10 PM, Dave Briccetti wrote:
>
> Thanks, but still failing today.
>
--
Marcel Molina
Twitter Platform Team
http://twitter.com/noradio
I've seen a couple instances now (@beaker and @mediaphyter) where a
private list shows up on the list of a user's memberships. It doesn't
seem like the existence of these private lists should be showing up in
the memberships list, nor can I reproduce the issue on my own account.
As an example, her
http://twitter.com/widgets/which_widget
click on html widget, and chose the one you want, it will help you
build one. They are all html, though use Javascript to pretty them up.
http://twitter.com/goodies/widgets
That link does not as far as I can tell, for the Web site widgets,
make flash
Hi David,
I found your excellent post hoping that it would solve the same
challenge for my app: updating profile image via Oauth... using
similar .net base to yourself...
BUT I just get the 401 all the time... despite taking your advice to
just sign with the HTTPmethod & URL My post data is l
I agree. A silent failure seems like the wrong behavior.. It should
return an error if the tweet has failed to post.
Also this change was made without any announcement that I recall
seeing or can find now. This is a pretty significant change in
behavior for existing clients.. We are failing to po
Simon,
I believe the body of your post might be incorrect. It should look like
this:
POST /account/update_profile_image.xml HTTP/1.1
Content-Type: multipart/form-data;
boundary=8cbed79c91b24f3
Host: twitter.com
Content-Length: 3863(this will probably change now..)
---
I created an app today using just the Lists API at http://listleagues.com
when can I start publicising it?
If anyone has any feedback let me know ol...@ollieparsley.com :
thanks
Ollie
On Oct 16, 8:04 am, Marcel Molina wrote:
> Hey folks. As some of you have likely read we're starting to do so
Chad,
Sorry for not being clear. I was thinking about Abraham William's
suggestion above where Twitter Search API works with authenticated
sessions+rate limiting, instead of IP based rate filtering. Just so
you know, AppEngine has 30 second timeout on request to all AppEngine
urls, and 10 second
Once Twitter posted details of the API in this public forum, that
opened the door to our discussing lists publicly (if it wasn’t open
already). And I’ve been doing so. I even made a video showing
TalkingPuffin all of Robert Scoble’s lists at once on a big screen:
http://twitter.com/dcbriccetti/sca
Sorry, that video is here: http://www.youtube.com/watch?v=NUVDP5sX2rA
Copy/paste error.
I was just wondering why the Twitter API wiki isn't open to edit?
Well, I can understand that Twitter wants full control of it, but it
seems like you could grow some really strong documentation using crowd-
sourcing. Twitter would put out the bulk of the content, but indie
developers could probabl
So the conclusion is:
1. DO NOT use the search operators that appear in the queries
generated by the Twitter Advanced Search tool. For example,
http://search.twitter.com/search?q=&ands=
Do not use "ands" in your queries. The default interpretation of
spaces in yr queries is logical AND. And th
71 matches
Mail list logo
