[twitter-dev] Re: Seeing duplicate Twitter User ID's under the same Username in our DB
That is the problem. User ID's are not suppose to change, though in our DB we see the same screen name with a different User ID. Of the 5,000 users in the DB, some have 6 ID's, a few have 5, 4 and 3 ID's but many have 2 User ID's. We are talking 5,000 users being affected of 5 million users in our DB. Sean On Sep 13, 5:46 pm, Mark McBride wrote: > One thought is that people change screen names at some frequency. IDs > never change. > > ---Mark > > http://twitter.com/mccv > > > > On Mon, Sep 13, 2010 at 4:41 PM, Sean Callahan wrote: > > Hello Twitter Support, > > > We are seeing something really weird. > > > We just noticed about 5,000 users in our database that have multiple > > User ID's under the same Username. > > > Have you every seen this and know why it happens and how we can > > prevent it from occurring again? > > > Thanks so much! > > > Sean > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list > > Change your membership to this > > group:http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Seeing duplicate Twitter User ID's under the same Username in our DB
Hello Twitter Support, We are seeing something really weird. We just noticed about 5,000 users in our database that have multiple User ID's under the same Username. Have you every seen this and know why it happens and how we can prevent it from occurring again? Thanks so much! Sean -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] How to get all Verified Users @ http://twitter.com/verified
Is there an API call or a quick way to get a list of all users on Twitter that are verified? I am updating this list, http://tweetphoto.com/celebrities, and was looking for a quick way to update it. Thanks for your help! Sean
[twitter-dev] Re: Introduce yourself!
I'm Sean Callahan, @CallahanSean, creator of http://tweetphoto.com, and have been working with the Twitter API since the fall of 2008. I now work with a team of seven who are very skilled at working with the Twitter API. Using the Twitter API we have created an extensive and easy-to-use photo sharing API and client libraries for Obj-C, Java and .Net. Other 3rd party developers in the Twitter community have developed client libraries for PHP and Python as well. Like you Abraham, we are constantly looking to improve our API. Please take a look at our API and let us know what we can provide the Twitter community to create an even better photo sharing experience. Please let me know how I can help you create a more social photo sharing experience in your application. The TweetPhoto API can be found http://groups.google.com/group/tweetphoto ~Sean On Feb 19, 1:20 pm, Abraham Williams <4bra...@gmail.com> wrote: > We have not had an introductions thread in a long time (or ever that I could > find) so I'm starting one. Don't forget to add an answer to the tools thread > [1](Gmail link [2]) as well. > > I'm Abraham Williams, I've been working with the Twitter API and this group > since early 2008. I do mostly freelance Drupal and Twitter API integration > and personal projects. I love seeing the creative projects developers build > or integrate with the API and look forward to meeting many of you at Chirp. > > TwitterOAuth [3] the first PHP library to support OAuth is built and > maintained by me, and will hopefully see a new release soon. I also built a > fun Chrome extension [4] that integrates common friends and followers into > Twitter profiles. > > The feature I would most like added to the API is a conversation method to > get replies to a specific status. > > So. Who are you, what do you do, what have you built, and what feature do > you most want to see added? > > @Abraham > > [1]http://groups.google.com/group/twitter-development-talk/browse_thread... > [2]https://mail.google.com/mail/#inbox/12680cd0fa59011e > [3]https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogo... > [4]http://code.google.com/p/twitter-api/issues/detail?id=142 > > -- > Abraham Williams | Community Advocate |http://abrah.am > Project | Out Loud |http://outloud.labs.poseurtech.com > This email is: [ ] shareable [x] ask first [ ] private. > Sent from Seattle, WA, United States To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[twitter-dev] TweetPhoto now setup for OAuth support
TweetPhoto now supports OAuth for photo sharing within third-party applications. http://groups.google.com/group/tweetphoto/web/authentication Let me know if you have any questions whatsoever. Sean
[twitter-dev] Re: A proposal for delegation in OAuth identity verification
That is similar to what we are doing at TweetPhoto and it is working out fine. Feel free to check out what we are doing: http://groups.google.com/group/tweetphoto/web/oauth-signin Third-party apps share with us their app's consumer key and secret. We receive the same level of access to the third-party app using our photo sharing service. When two companies work together and are partners there needs to be a level of trust. Furthermore, developers can change their consumer secret at any time so their is no real issue with this method. There are a few integrations coming out soon with this method in place. Please let us know your thoughts and if you have any questions. Sean On Feb 11, 10:05 am, Brian Smith wrote: > Raffi Krikorian wrote: > > > The term most frequently used for “delegator” is “relying party.” > > What you call the service provider is most frequently called the > > “identity provider.” What you call the consumer is usually called > > the “subject.” See OpenID, InfoCard, and other similar > > specifications for example usage of these terms. > > First, what I wrote about "subject" was misleading: the user--not the > consumer--is the subject. > > > i hear all this - it just gets a bit complicated with because we are > > conflating this with our oauth situation. > > This doesn't really have much to do with OAuth, because you are not > trying to allow delegation of credentials--that is, you are not trying > to allow the "consumer" app to let the relying party use the consumer > app's OAuth access token to read/write the user's account.> perhaps its time > to move to an oauth + openID hybrid system. > > I don't know if OpenID really solves this problem well, especially for > apps that aren't webapps. > > > The subject doesn’t want the relying party to have access to the > > entire response from the account/verify_credentials request as if > > he had given the relying party read access to his account. I am > > not sure if account/verify_credentials returns sensitive > > information (information only available to apps that have been > > authorized by the user) yet, but I think it is likely in the > > future that it will do so. It would be prudent to have delegation > > use a different resource designed specifically for delegation. > > > i think this is again a general case vs a twitter case. i think in > > the general case, the delegator would call some endpoint that would > > simply verify the identity through a HTTP code (2xx for success, 4xx > > for failure). twitter, as a special case, sends along the user object > > [as] part of it? > > account/verify_credentials discloses information that is private. For > example, the HTTP header of account_verify_credentials discloses > information about how frequently the user accesses twitter (the rate > limit headers). If the user hasn't previously authorized (via OAuth) the > delegator (relying party) to have read access to his account, then the > delegator (relying party) shouldn't be able to get this information. > Also, I think you should plan ahead for the case where > account/verify_credentials returns even more sensitive information. If > you were going to reuse an existing resource, I'd reuse > users/show.format?user_id= instead. But, AFAICT, it's much > better to create a new resource for this purpose, and pretty easy to do so. > > I think the following would be a better protocol: > > Consumer to Relying Party: Give me , a nonce signed > with your OAuth credentials for the relying party'sidentity verification > service. Relying Party to Consumer: Here is the token . > (This is done using whatever protocol the consumer and the relying party > agree to use.) > > Consumer to Identity Provider: Here's . Give me > , which is (, screen_name) signed with > a signature that the relying party can verify is from the identity > provider. Identity Provider to Consumer: I verified that the token was > signed by the relying party identified by . Here is > . (This is an OAuth-protected transaction using the > consumer's credentials). > > Consumer to Relying Party: Here is .Relying Party to > Consumer: OK, let's continue on with whatever we need to do. (This is > done using whatever protocol the consumer and the relying party want to > use.) > > Notice in particular: (a) each server only has to process one request, > (b) the relying part and the identity provider never have to communicate > directly with each other, (c) the consumer (user) can control the level > of security used in all the communication (e.g. TLS for everything), (d) > IP-RP-SIGNED-TOKEN> can be used as the assertion in the OAuth 2.0/WRAP > assertion profile, if the relying party is using OAuth WRAP to > authenticate the user, (e) the user and the identity provider can both > restrict which consumers can sign into which relying parties for which > users using this mechanism. > > Regards, > Brian
[twitter-dev] Re: OAuth Photo Support Now Available at TweetPhoto
All the other functionality in the TweetPhoto API is also supported using OAuth as well. Let me know if you have any questions. Sean On Jan 31, 9:01 pm, Sean Callahan wrote: > TweetPhoto now supports photo uploads using OAuth for all 3rd party > application developers. > > http://groups.google.com/group/tweetphoto/web/oauth-signin > > Basic Auth may be depreciated soon so we created a way for you to > allow your users to continue to uploadphotos. > > Please let me know if you have any questions or if I can help in any > way. > > Sean
[twitter-dev] Re: How Does TwittPic Works ?
TweetPhoto offers an OAuth solution for uploading photos. Please check out the link below and let me know if you have any questions. http://groups.google.com/group/tweetphoto/web/oauth-signin Thanks! Sean On Feb 2, 7:04 am, Feras Allaou wrote: > Dear Sirs, > > I was trying to do oAuth to use Twitter API but I was surprised that > TwitPic doesn't use this Authentication method ! so How could TwitPic > publish it's name when it updates the status ? > I mean if I use simple Auth method the message will be sent using API > which means Twitter API. > but When I was OAuth the sending method will be my Twitter Client , > right ? > So how does TwitPic sending method is TwitPic & they don't use Oauth ? > > Regards, > Feras Allaou
[twitter-dev] Basic Auth seems to be down right now - Last 10 minutes
Looks like basic auth is down. Anyone else seeing lots of login failures? Sean
[twitter-dev] OAuth Photo Support Now Available at TweetPhoto
TweetPhoto now supports photo uploads using OAuth for all 3rd party application developers. http://groups.google.com/group/tweetphoto/web/oauth-signin Basic Auth may be depreciated soon so we created a way for you to allow your users to continue to upload photos. Please let me know if you have any questions or if I can help in any way. Sean
[twitter-dev] iPhone Developers: Objective-C Library for TweetPhoto
We just released the Objective-C library for the entire TweetPhoto API. It is a set of drop in classes designed to allow you to get up and running quickly with the TweetPhoto Photo Sharing API. http://code.google.com/p/tweetphoto-api-objective-c/ This library includes every feature you'll need to manage the entire photo sharing experience within your application - from uploading photos, commenting, favoritng, and voting to social feeds, user feeds, and everything in between. Please let me know if you have any questions whatsoever. Sean
[twitter-dev] URGENT: Error Signing In Twitter Users on TweetPhoto API (Metering/Rate Limiting)
Hi Doug, Alex & Ryan, We need your immediate help. Right now Twitter users are not being able to authenticate through the TweetPhoto photo sharing API at tweetphotoapi.com. 9 times out of 10, no one can upload a photo through the platform and receive, "error message - invalid twitter username/password". The error we're receiving from Twitter: Rate limit exceeded. Clients may not make more than 15 requests per 60 minutes. It seems like the problem goes away at the top of every hour which could mean it is a metering and/or a rate limiting issue. Everything works for the first 7 to 10 minutes at the beginning of every hour and then no one can sign in to upload photos through our API. I think we've narrowed this down to being a sign in issue and need your immediate help. I've received reports about this over the last 72 hours, but could not replicate the issue from our end until now. I've whitelisted over 12 to 15 IP addresses in the past to prevent such issues and was always told whitelisting does not affect sign in issues. I am stumped. Everything has always worked fine with the levels of volume we have today. Please let us know if you can help. I am standing by on the phone if you need to call me. Thank you! Best Regards, Sean Callahan TweetPhoto.com Co-Founder Office (760) 230-5579 Mobile (760) 840-7468 Skype: seancallahan
[twitter-dev] Does anyone have an ASPinfo.asp file they can share?
I am in need of an aspinfo.asp file to grab detailed system information on a windows server. I can't find one of those files to save my life. Can someone please email me one to s...@tweetphoto.com ??
[twitter-dev] Re: Developer Preview: Geolocation API
Quick question Ryan, because none of this will surface on Twitter.com will you keep the Location field for a users profile or is that going away when this becomes love? If it stays, will there be any specific changes regarding the location on a user's profile when this API becomes available? Sean On Aug 20, 5:28 pm, Lepton wrote: > Perfect timing! My iPhone app about to be released has a lot to do > with geolocation, and already uses Twitter to set and see locations of > people. Myallo HotList tracks the "hotness" of people and places in > your social universe partly through their locations. For example as a > person gets nearer to you, they get hotter, if friends gather near a > place, they and the place get hotter. I want to use these upcoming > features to "discover" nearby people. You can preview the app via its > documentation athttp://myallo.com/hotlist
[twitter-dev] Re: Platform downtime is expected
Hi Ryan, When I sent the email 30 minutes ago I was not able to login. Now, like you, I was able to login. Now it is a sporadic issue. I will get you the info you need to those 5 questions. Because our current environment at the Rackspace Cloud is shared I need to call them. Basically, it is simply a basic auth issue. We're not calling anything, but that. User's cannot login. The IPs of the Rackspace Cloud that I am on are (Primary) 74.205.61.228 and (Secondary) 74.205.61.229 Not sure if this helps. Please advise. Sean On Aug 17, 3:37 pm, Ryan Sarver wrote: > Sean, > > I was just able to log into TweetPhoto using my basic auth credentials > with no problem. Please test again and provide any of the additional > details that you can: > > *Copying from Alex email to make sure its consistent > 1. The IP of the machine making requests to the Twitter API. If you're > behind NAT, please be sure to send us your *external* IP. > > 2. The IP address of the machine you're contacting in the Twitter > cluster. You can find this on UNIX machines via the "host" or > "nslookup" commands, and on Windows machines via the nslookup" command. > > 3. The Twitter API URL (method) you're requesting and any other > details about the request (GET vs. POST, parameters, headers, etc.). > > 4. Your host operating system, browser (including version), relevant > cookies, and any other pertinent information about your environment. > > 5. What kind of network connection you have and from which provider, > and what kind of network connectivity devices you're using. > > > Best, Ryan > > > > On Mon, Aug 17, 2009 at 3:33 PM, Sean Callahan wrote: > > Hi Ryan, > > > I just replied to your email and also will post here in case you read > > this first. Maybe others will have an idea too as why basic auth is > > not working. Long story short - we were down for 3 days, up for the > > last 3 hours, and now down once again - no one can login using basic > > auth on our sitehttp://tweetphoto.com. > > > It so happens when I responded to your email about 3 hours ago > > everything was working fine - meaning I was able to login to > > TweetPhoto as were other users. Since replying to your second email > > basic authentication onhttp://tweetphoto.comis not working an no one > > can login to their account on our domain. > > > I'm not sure why basic auth is not working when you said only OAuth > > should have been affected. With that said, I have an idea as I've > > spoken to a few Rackspace customers. Is it possible that a range of > > IPs at Rackspace are being blocked/throttled preventing users from > > logging in through basic auth? > > > I'm not sure why basic authentication came back online this morning > > and now it does not work. You asked me to respond to an email Alex > > sent, but I have not seen that. Please let me know what information > > you need to better troubleshoot this issue so we can resume service. > > > As I mentioned in my email to you, I am willing to pay a monthly > > service fee as I'm sure other Twitter Developers are, to keep service > > running to TweetPhoto.com up 100% of the time. > > > Please advise. > > > Best Regards, > > > Sean Callahan > > > On Aug 16, 11:40 am, bosher wrote: > >> Thanks for the update Chad.. > > >> On Aug 16, 10:52 am, Chad Etzel wrote: > > >> > Hi all, > > >> > The API team is actively debugging the OAuth issues as we speak. > >> > Please be patient as we nail down the problems. > > >> > Thanks, > >> > -Chad > > >> > On Sun, Aug 16, 2009 at 1:43 PM, Andrew Badera wrote: > > >> > > On Sun, Aug 16, 2009 at 1:40 PM, bosher wrote: > > >> > >> How is it that all the oAuth apps out there are down, but others like > >> > >> TweetMeMe are not? TweetMeMe works just fine, how is that possible? > > >> > > HTTP Basic Auth still works I believe, as do any pre-problem OAuth > >> > > tokens issued. > > >> > > ∞ Andy Badera > >> > > ∞ This email is: [ ] bloggable [x] ask first [ ] private > >> > > ∞ Google > >> > > me:http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)-Hide > >> > > quoted text - > > >> - Show quoted text -- Hide quoted text - > > - Show quoted text -
[twitter-dev] Re: Platform downtime is expected
Hi Ryan, I just replied to your email and also will post here in case you read this first. Maybe others will have an idea too as why basic auth is not working. Long story short - we were down for 3 days, up for the last 3 hours, and now down once again - no one can login using basic auth on our site http://tweetphoto.com. It so happens when I responded to your email about 3 hours ago everything was working fine - meaning I was able to login to TweetPhoto as were other users. Since replying to your second email basic authentication on http://tweetphoto.com is not working an no one can login to their account on our domain. I'm not sure why basic auth is not working when you said only OAuth should have been affected. With that said, I have an idea as I've spoken to a few Rackspace customers. Is it possible that a range of IPs at Rackspace are being blocked/throttled preventing users from logging in through basic auth? I'm not sure why basic authentication came back online this morning and now it does not work. You asked me to respond to an email Alex sent, but I have not seen that. Please let me know what information you need to better troubleshoot this issue so we can resume service. As I mentioned in my email to you, I am willing to pay a monthly service fee as I'm sure other Twitter Developers are, to keep service running to TweetPhoto.com up 100% of the time. Please advise. Best Regards, Sean Callahan On Aug 16, 11:40 am, bosher wrote: > Thanks for the update Chad.. > > On Aug 16, 10:52 am, Chad Etzel wrote: > > > > > Hi all, > > > The API team is actively debugging the OAuth issues as we speak. > > Please be patient as we nail down the problems. > > > Thanks, > > -Chad > > > On Sun, Aug 16, 2009 at 1:43 PM, Andrew Badera wrote: > > > > On Sun, Aug 16, 2009 at 1:40 PM, bosher wrote: > > > >> How is it that all the oAuth apps out there are down, but others like > > >> TweetMeMe are not? TweetMeMe works just fine, how is that possible? > > > > HTTP Basic Auth still works I believe, as do any pre-problem OAuth > > > tokens issued. > > > > ∞ Andy Badera > > > ∞ This email is: [ ] bloggable [x] ask first [ ] private > > > ∞ Google > > > me:http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)- Hide > > > quoted text - > > - Show quoted text -
[twitter-dev] Re: Issues with the API this morning?
The issue we're seeing at TweetPhoto is that no one can login to their account when using basic auth. Was informed by Twitter support that they are aware of the issue and are looking for a fix. On Aug 17, 8:53 am, Dewald Pretorius wrote: > Lots of issues here (tweetlater) too. High-volume calls are again > blocked by the edge defenses with connection refused. > > Exactly the same as last weekend. > > Dewald > > On Aug 17, 12:19 pm, CodeWarden wrote: > > > > > Are there still issues with the API this morning? We have many of our > > UberTwitter users reporting timeouts when trying to retrieve timelines > > and send tweets. We are not using OAUTH. > > > Any info would be greatly appreciated! > > > -CodeWarden
[twitter-dev] Re: Platform downtime is expected
Yeah, no one can login to http://TweetPhoto.com just tried minutes ago and still no dice. Twitter, do I need to provide anything to you or do something on my end to allow users to login through basic authentication on our site? I tried moments ago and could not login, but was able to login to a competitors site no problem. Please advise. -Sean On Aug 15, 8:21 pm, Jonathan George wrote: > 1. It's been roughly 10 hours. How about an update? > > 2. It'd be great if you would post this to status.twitter.com, in > addition to the developer mailing list. Status is seen by more users, > and the last update you have on it is rather ambiguous. When users > see that the Twitter web interface is up and running, they expect the > apps to be up and running as well. > > best, > jonathan > > On Aug 15, 1:08 pm, Doug Williams wrote: > > > > > Hi all --If you have been monitoring our status blog [1] or been to > > Twitter.com today you have noticed that we are once again experiencing > > problems due to external causes. The issues causing the downtime require > > that we once again take measures to bring the site back online. > > > The first step our operations team must take will likely cause API downtime, > > especially affecting OAuth. We apologize for the inconvenience and we will > > work quickly to reduce the impact to the API. We appreciate your patience > > and I will update you as soon as we know more. > > > Thanks, > > Doug
[twitter-dev] Re: Platform downtime is expected
I was a bit confused about this downtime as the Twitter status blog says it was unexpected, but the post Doug wrote here says it was expected. Nevertheless, standing by and awaiting restoration of the API so users can log into their favorite Twitter apps. -Sean On Aug 15, 11:02 pm, bosher wrote: > Noticing the downtime with oAuth now... > > On Aug 15, 8:05 pm, Ritvvij wrote: > > > > > Phew! thanks a lot.. i spent whole day thinking where I messed up the > > code. :-) > > > On Aug 15, 10:03 pm, goodtest wrote: > > > > Same here. New users can't authorize. After pressing 'Approve', it > > > takes for ever and ends up in a blank-page > > > withhttp://twitter.com/oauth/authorize > > > url. > > > > On Aug 15, 6:51 pm, Ritvvij wrote: > > > > > Hi could this be the reason why? > > > > > On clicking authenticate user, my application moves to twitter. When > > > > the user presses APPROVE, it waits like forever and then goes to a > > > > blank page with url as "http://twitter.com/oauth/authorize"; instead > > > > of my call back URL. ?? > > > > > Please advise. > > > > Till last night my app was working, and since today morning, even > > > > right now, its down. :-( > > > > > On Aug 15, 8:21 pm, Sean Callahan wrote: > > > > > > Thanks for the reply Doug. Any new news? Still not able to login > > > > > using basic auth on TweetPhoto. Do you have any ETA as to when we'll > > > > > be restored? > > > > > > On Aug 15, 1:29 pm, Doug Williams wrote: > > > > > > > Sean,At this time we are monitoring the situation and containing > > > > > > issues as > > > > > > we see them. Let's hold off on restoration requests until things > > > > > > stabilize. > > > > > > > Thanks, > > > > > > Doug > > > > > > > On Sat, Aug 15, 2009 at 1:17 PM, Sean Callahan > > > > > > wrote: > > > > > > > > Thanks for the update Doug. Users on TweetPhoto are not able to > > > > > > > login. > > > > > > > I've added an alert notification on our > > > > > > > homepage,http://TweetPhoto.com, > > > > > > > to make them aware of the issues linking to the Twitter status > > > > > > > blog. > > > > > > > Will you need our IPs again to whitelist them or are you good to > > > > > > > go. > > > > > > > Please let me know how I can be of service. > > > > > > > > -Sean > > > > > > > > On Aug 15, 12:37 pm, Sam Street wrote: > > > > > > > > I haven't experienced any downtime or lack of connectivity so > > > > > > > > far. > > > > > > > > > On Aug 15, 7:16 pm, dougw wrote: > > > > > > > > > > Looks like I forgot the link to the status blog. > > > > > > > > > > [1] > > > > > > >http://status.twitter.com/post/163603406/working-on-unexpected-downtime > > > > > > > > > > Thanks, > > > > > > > > > Doug > > > > > > > > > > On Aug 15, 11:08 am, Doug Williams wrote: > > > > > > > > > > > Hi all --If you have been monitoring our status blog [1] or > > > > > > > > > > been to > > > > > > > > > > Twitter.com today you have noticed that we are once again > > > > > > > experiencing > > > > > > > > > > problems due to external causes. The issues causing the > > > > > > > > > > downtime > > > > > > > require > > > > > > > > > > that we once again take measures to bring the site back > > > > > > > > > > online. > > > > > > > > > > > The first step our operations team must take will likely > > > > > > > > > > cause API > > > > > > > downtime, > > > > > > > > > > especially affecting OAuth. We apologize for the > > > > > > > > > > inconvenience and we > > > > > > > will > > > > > > > > > > work quickly to reduce the impact to the API. We appreciate > > > > > > > > > > your > > > > > > > patience > > > > > > > > > > and I will update you as soon as we know more. > > > > > > > > > > > Thanks, > > > > > > > > > > Doug
[twitter-dev] Re: Platform downtime is expected
Thanks for the reply Doug. Any new news? Still not able to login using basic auth on TweetPhoto. Do you have any ETA as to when we'll be restored? On Aug 15, 1:29 pm, Doug Williams wrote: > Sean,At this time we are monitoring the situation and containing issues as > we see them. Let's hold off on restoration requests until things stabilize. > > Thanks, > Doug > > On Sat, Aug 15, 2009 at 1:17 PM, Sean Callahan wrote: > > > > > > > Thanks for the update Doug. Users on TweetPhoto are not able to login. > > I've added an alert notification on our homepage,http://TweetPhoto.com, > > to make them aware of the issues linking to the Twitter status blog. > > Will you need our IPs again to whitelist them or are you good to go. > > Please let me know how I can be of service. > > > -Sean > > > On Aug 15, 12:37 pm, Sam Street wrote: > > > I haven't experienced any downtime or lack of connectivity so far. > > > > On Aug 15, 7:16 pm, dougw wrote: > > > > > Looks like I forgot the link to the status blog. > > > > > [1] > >http://status.twitter.com/post/163603406/working-on-unexpected-downtime > > > > > Thanks, > > > > Doug > > > > > On Aug 15, 11:08 am, Doug Williams wrote: > > > > > > Hi all --If you have been monitoring our status blog [1] or been to > > > > > Twitter.com today you have noticed that we are once again > > experiencing > > > > > problems due to external causes. The issues causing the downtime > > require > > > > > that we once again take measures to bring the site back online. > > > > > > The first step our operations team must take will likely cause API > > downtime, > > > > > especially affecting OAuth. We apologize for the inconvenience and we > > will > > > > > work quickly to reduce the impact to the API. We appreciate your > > patience > > > > > and I will update you as soon as we know more. > > > > > > Thanks, > > > > > Doug
[twitter-dev] Re: Platform downtime is expected
Thanks for the update Doug. Users on TweetPhoto are not able to login. I've added an alert notification on our homepage, http://TweetPhoto.com, to make them aware of the issues linking to the Twitter status blog. Will you need our IPs again to whitelist them or are you good to go. Please let me know how I can be of service. -Sean On Aug 15, 12:37 pm, Sam Street wrote: > I haven't experienced any downtime or lack of connectivity so far. > > On Aug 15, 7:16 pm, dougw wrote: > > > > > Looks like I forgot the link to the status blog. > > > [1]http://status.twitter.com/post/163603406/working-on-unexpected-downtime > > > Thanks, > > Doug > > > On Aug 15, 11:08 am, Doug Williams wrote: > > > > Hi all --If you have been monitoring our status blog [1] or been to > > > Twitter.com today you have noticed that we are once again experiencing > > > problems due to external causes. The issues causing the downtime require > > > that we once again take measures to bring the site back online. > > > > The first step our operations team must take will likely cause API > > > downtime, > > > especially affecting OAuth. We apologize for the inconvenience and we will > > > work quickly to reduce the impact to the API. We appreciate your patience > > > and I will update you as soon as we know more. > > > > Thanks, > > > Doug
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
Alex, Did not see this post and posted a new message. Still receiving lots of errors and no one can login on our site, tweetphoto.com, right now along with a handful of others (that I've tried myself). Just wanted to give you a heads up. Thanks! Sean On Aug 11, 1:11 pm, Alex Payne wrote: > Our operations staff has informed me that the attack ceased several minutes > ago. Site performance should be returning to normal. > > On Tue, Aug 11, 2009 at 12:23, Alex Payne wrote: > > We're currently experiencing another wave of Distributed Denial of Service > > (DDoS) attacks against our system. Expect periodic slowness and errors until > > the attack passes or is countered by our operations team and hosting > > provider. Updates will be provided as we get them. > > Thanks for your patience. > > > -- > > Alex Payne - Platform Lead, Twitter, Inc. > >http://twitter.com/al3x > > -- > Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Seeing same login issues right now as when DDoD happened
I've tried logging into a handful of sites built around the Twitter API without success. I'm seeing the same login issues right now as when the DDoD happened. Twitter is aware of the downtime issue on their status page, http://status.twitter.com, but are they aware of the API issues (e.g., being able to login)? Sean
[twitter-dev] Re: OK Seriously People
Agree with what you said. Very well put. It is affecting most all of us. Our photo sharing service (TweetPhoto) is tied into 20 apps whose users aren't able to upload photo onto our platform. I've communicated by adding an alert to our homepage about the issues which broadcasts the message and hopefully helps manage user expectations. Twitter, you'll figure it out and find a solution. I'm also confident you'll keep us in the loop going foward. Thanks! Sean On Aug 9, 11:05 am, David Fisher wrote: > A few of you are acting like real children and a few of you still have > your heads screwed on right. > > I'm confident they are doing everything they can. Chill and enjoy your > weekend. They'll get it sorted out. > > What did you guys do in 2007? Twitter was down all the time then. Your > blood pressure must have been through the roof with weekly visits to a > shrink if you responded this way every time it went down. > > dave > > On Aug 9, 1:48 pm, Neil Ellis wrote: > > > > > Nice story Adam, however the band are actually trying to run a > > business, not doing this for love/free. I can assure you the investors > > in Twitter will be looking to turn profit. Of course if the band are > > laid up then the danger is the hotdog man (and all his customers) will > > go to another band that are still playing and have fans. > > > That's why I'm 100% confident all that can be done is being done, cos > > plenty of people at Twitter will know how fickle a user base can be. > > > Good luck guys, I know what these situations are like and it's hard on > > you all - I actually hope you guys are getting some rest because it > > doesn't sound like this is a 100 yard sprint. > > > I also hope someone is making sure the ops/devs aren't reading this > > list (or getting emails etc) - stress doesn't help productivity in my > > experience. Knowing what is at stake does. > > > Again good luck chaps, I know how the trenches feel :-) > > > And of course it does suck for the rest of us too, alas that is > > business. > > > ATB > > Neil > > > On 9 Aug 2009, at 18:24, Adam Cloud wrote: > > > > ***Scenario*** > > > > A band broadcasts their music on a radio station all the time, and > > > people are able to freely tune into it, or go buy their music. They > > > go and play in a city park for free every day just because it's a > > > much nicer experience for the listener then to be just sitting at > > > home listening on their radio. > > > > You as an up and coming entrepreneur go buy a hotdog & drink stand > > > and setup camp in that park to make some cash off of the flow of > > > people who come to see this free event every day. You being there, > > > giving the ability for people to eat & drink without leaving the > > > park allows for more of this bands songs to be heard, in effect > > > increasing the chance that their music might be purchased. So you're > > > essentially helping them, by taking advantage of them for your > > > business. > > > > The band gets in a car crash, and alot of equipment is damaged to > > > the point of not being able to be used, along with their main source > > > of transportation. The band starts working to find and replace all > > > that is damaged in their equipment and for their car. > > > > Now you can imagine that little hotdog stand guy standing on their > > > doorstep while they recover yelling profanities and how they should > > > be skipping the shipping company who's delivering their parts and > > > get their parts themselves to save time. Yelling that they shouldn't > > > be sleeping, they should be working on their band van right now to > > > make sure it can take them back to the park so he can make some > > > money. "People aren't coming to my stand anymore!!! They're going to > > > fast food restaurants and going home. WTF i sold my wife for this > > > stand!!!" > > > > Now of course, this little hotdog stand man may not have really sold > > > his wife, depending upon which one of you people who are still up in > > > arms about this was put in his place, but i think you get my points. > > > > The band could easily move to a venue that has their own hotdog/ > > > drink stand making your services not necessary, but instead of doing > > > that and capitalizing on the profit they could get from that, > > > they're still planning on going back to the same park they do their > > > free shows at, and allowing you to continue earning your money. > > > > And this concludes storytime. :) > > > > Happy sunday! (Relax!) > > > > On Sun, Aug 9, 2009 at 10:58 AM, Terry Jones wrote: > > > > > "Stuart" == Stuart writes: > > > Stuart> * I can't believe you lot don't realise that constantly > > > demanding > > > Stuart> status updates, while certainly important to you, is little > > > more > > > Stuart> than a distraction for those who are actually fighting the > > > good > > > Stuart> fight. > > > > I woke up this morni
[twitter-dev] Basic Authentication is down again on our site
Hi Guys, After the original DDoS attack our service, TweetPhoto.com, was blocked. After communicating my IP addresses an waiting about 48 hours it vegan working Friday afternoon. All of a sudden yesterday afternooon no one could login to our site. I wonder why our site was restored Friday in terms o users being able to login and now yesterday and today no one can login to our site? I tried logging into a couple competitors sites and was able to login without a problem. Can you please help me out a d get my service restored again? Best Regards, Sean Callahan
[twitter-dev] Re: Introducing Chad Etzel, Twitter Platform Support
Kudos to you Chad. Keep up the good work! Sean On Jul 31, 4:39 pm, Sam Street wrote: > Welcome :) > > On Jul 31, 9:59 pm, Doug Williams wrote: > > > > > Hi all -- > > We are excited to announce that Chad Etzel has joined our team part-time to > > support the developer community. He is the one man show behind TweetGrid [1] > > amongst other projects [2]. We reached out to Chad to join our team after > > his continual and valuable participation in the community made his passion > > for the Platform evident. The Platform team is not the only Twitter team > > that noticed his value. On a recent trip to our local coffee shop [3], a > > search engineer shared that Chad often notices search defects and suggests > > fixes consistently ahead of most other developers. > > > He is one of the most experienced Twitter API developers in the community > > and we feel this experience will serve developers' interests well. Chad will > > be helping to answer requests that enter our support channels [3] to bolster > > our support to developer community. He will be working remotely from his > > home in North Carolina. You can follow him on Twitter > > athttp://twitter.com/jazzychad. > > > We are happy to have Chad on our team an look forward to continuing to build > > support as a pillar of our offering .The API is hiring passionate developers > > and evangelists so if you are interested in getting involved, please let us > > know. > > > 1.http://tweetgrid.com > > 2.http://jazzychad.net > > 3.http://twitpic.com/a99zj(@noradioand @al3x in frame) > > > Thanks, > > Doug- Hide quoted text - > > - Show quoted text -
[twitter-dev] Re: New blocks still happening
Users on our site Jesse provide username and password and still can't login. It has been like that all day. I feel your pain and wish we could get back online quicker. On Aug 6, 6:16 pm, Jesse Stay wrote: > This is also another nick against OAuth. My users can't even log in right > now because we're relying on OAuth for login. > Jesse > > > > On Thu, Aug 6, 2009 at 8:45 PM, Dewald Pretorius wrote: > > > I have seen the same thing. > > > So, if you have white listed IPs that are still showing a rate limit > > of 20,000, DO NOT use them right now. > > > After a few minutes of use their rate limits are cut down to 150 per > > hour. > > > Dewald > > > On Aug 6, 8:58 pm, Tinychat wrote: > > > So, like everyone else I was receiving 408's from all our production > > > servers. Wasnt sure what was causing it, but it turned out to be that > > > twitter is blocking the IPs. Ok, must be related to the ddos stuff > > > from earlier on- Must have gotten caught in the crossfire. > > > > So I go ahead and use some development servers to start sending > > > requests- All is fine, for about a hour. They are blocked now. So to > > > anyone out there, there is no point using a new IP- It will get > > > blocked within a hour or so. I guess we have to wait for twitters host > > > to fix it, or use actionscript/ajax to have the end user request the > > > data himself (Which is what I am going to do) so its always a unique IP- > > > Hide quoted text - > > - Show quoted text -
[twitter-dev] Re: Why is Biz saying things are "back in action"?
Yeah Jesse, I hear you and am super bummed out. My service, TweetPhoto.com, is also down in terms of users being able to login through basic auth. It's been like that all day. No one has been able to upload photos. I emailed Doug at Twitter and he requested my server's IP address which I provided. I guess they are slowly trying to bring apps back online. I just wish this happened a little sooner. I feel totally helpless at the moment. What are your thoughts? On Aug 6, 6:25 pm, Jesse Stay wrote: > Why is Biz saying things are "back in action" when apps like mine, and many > other very large names are still broken from it. Sending this message to > users sends a false message to them stating they should expect we should be > up as well. At a very minimum, please state the API is still having issues > so users can know what to expect: > > http://blog.twitter.com/2009/08/update-on-todays-dos-attacks.html > > Jesse
[twitter-dev] New TweetPhoto Open APIs released - Photo Sharing API (Basic & Advanced)
TweetPhoto Open API: http://groups.google.com/group/tweetphoto/web What is included in the Open Photo Sharing API on TweetPhoto: Getting Started with the TweetPhoto API All Write Operations (HTTP POST/PUT/DELETE) Pagination Privileged Operations Basic Upload API (Upload and UploadAndPost) Advanced Upload API (Upload and UploadAndPost) Sample C# Upload and Post Sample iPhone Code for Uploading a Photo Add and Delete User Favorites Add User Comment Add User Photo View Delete User Comment Set User Settings Get Public Stream Photos Get Viewed Photos in Public Stream Get Commented Photos in Public Stream Get Favorite Photos in Public Stream Get User Profile Get User Settings Get Photos Uploaded by a User Get Who Has Viewed a User's Photos or a Specific Photo Get Comments for a User Get Favorites for a User Get Friends for a User Get Photo Details Get Image Paths Embedding Images from Pic.gd URLs Available Atom and RSS Feeds Fetch Image from TweetPhoto URL Signin and Provision
[twitter-dev] TweetPhoto Open API Just Released (Photo Sharing Platform for Twitter)
The TweetPhoto Open API is now available to the Twitter developer community. It is the most expansive photo sharing API available within the Twitter eco-system. You can view the Open API at http://groups.google.com/group/tweetphoto/web Here you can get your API key here http://www.tweetphoto.com/developer.php Please let me know if you have any questions. Best Regards, Sean Callahan
