[twitter-dev] Re: Open Auth
On Sat, Aug 15, 2009 at 22:26, Kevin Mesiab ke...@mesiablabs.com wrote: The interaction seems unintuitive and redundant for users who have already granted our application 'trust' by installing it. I can't understand this notion. Every single day users are sheep enough to do stupid things - they just need to be guided to do so. And then they will follow. Every single day (especially the normal users) install dozens of apps on facebook without even thinking about that box in the middle nor reading it. And 'the experienced ones' who teach the sheeps make sure that never use your password gets drilled into their heads. Before there was no alternative. Now there is a better way.From now it is password? BAD. Using without password and authorize with twitter: good! Yes, they have granted you the trust of installing it, but could you please set the mindset to the goal? as part of our x step installation step, this is what is going to happen: - download app - install app - test app - now the fun part: making sure you get the best ou tof this experience and connect it with twitter itself, and this is how it looks. We are using the secure process where you do not need to enter anywhere your password. we never ask for your password, because we are the good guys! - do this - do that and tada! you can start using our app! thanks for trusting us! Where is the problem? It only is unintuitve when you make it as such. of course the above is too complicated, so the real steps only should be 3 easy steps to go - download, install, connect, use! or something like it. But as long as you treat it as the ugly way you don't want to use, you will not make it easy on you. Nicole -- Jetzt im Buchhandel: Twitter - Mit 140 Zeichen zum Web 2.0 Amazon: http://tinyurl.com/6at9c5 http://mit140zeichen.de - http://twitter.com/m140z Kontakt: http://twitter.com/NicoleSimon https://www.xing.com/profile/Nicole_Simon skype: nicole.simon / mailto:nicole.si...@mit140zeichen.de phone: +49 451 899 75 03 / mobile: +49 179 499 7076
[twitter-dev] Re: Seeking Beta Tester Developers for my API
That was my main feedback as well so far. On Sun, Aug 16, 2009 at 2:25 AM, Beier beier...@gmail.com wrote: Sam, it's a cool app, but my first test result is that you may want to redesign your UI. It looks too similar to Twitter site, it may confuse users and Twitter won't like it. You want to build a good relationship with Twitter and this is the wrong start. Your app is quite unique in the space and I'm sure you can come up with an unique UI. -- Dale Merritt Fol.la MeDia, LLC
[twitter-dev] Re: Platform downtime is expected
I was trying to be patient with this, but seeing that no one is complaining, I'm afraid I might be alone here. One of SimplyTweet's server had not been able to access the API *at all*. Even /rate_limit_status (nothing to do with OAuth) timeout every time. Is this expected? No response when I tweeted @twitterapi, as usual. wget http://twitter.com/account/rate_limit_status.xml? screen_name=hboon -- Hwee-Boon On Aug 16, 4:40 pm, Costa Rica ticoconid...@gmail.com wrote: Hello I am perceiving search API downtime as well http://search.twitter.com/search?q=Indonesiareturns results, but the XML, ATOM, JSON are returning me a blank page... TCI On Aug 15, 12:08 pm, Doug Williams d...@twitter.com 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
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 d...@twitter.com 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: Feed page sometimes not actually returning a feed
http://status.twitter.com/post/163603406/working-on-unexpected-downtime On Aug 15, 8:37 pm, Jon Leighton j...@jonathanleighton.com wrote: Hiya, I am displaying a twitter feed on a website. Unfortunately sometimes when my website requests the feed, it doesn't get a feed, but the following instead: HTML HEAD META HTTP-EQUIV=Refresh CONTENT=0.1 META HTTP-EQUIV=Pragma CONTENT=no-cache META HTTP-EQUIV=Expires CONTENT=-1 TITLE/TITLE /HEAD BODYP/BODY /HTML It happens somewhat erratically. Any ideas? Cheers
[twitter-dev] When is whitelisting necessary?
Hello, I am new to Twitter API and I am trying to understand whether I should apply for whitelisting my application. The documentation says: IP whitelisting takes precedence to account rate limits. GET requests from a whitelisted IP address made on a user's behalf will be deducted from the whitelisted IP's limit, not the users. Therefore, IP-based whitelisting is a best practice for applications that request many users' data. However if for example 200 users are accessing twitter through my application in one hour, and each access from my app to twitter is done with the relevant end user as the twitter authenticated user, I can do 200*150=3 API calls in one hours without whitelisting the IP address, which is more than the 2 I could do with whitelisting. Can anyone give a counter example where whitelisting is absolutely necessary? Thank you, Boaz
[twitter-dev] Re: Open Auth
When a user signs up at TwitPic, for instance, the same credentials they used for Twitter are now valid for use in uploading media. This lets users enjoy a bit of a mash-up with a single sign-on. Is this also true when authorized via openAuth? -- Kevin Mesiab CEO, Mesiab Labs L.L.C. http://twitter.com/kmesiab http://mesiablabs.com http://retweet.com
[twitter-dev] Re: When is whitelisting necessary?
Necessary, for example, if you use a particular account to notify your users of a certain event (sending them notifications). Large apps with high traffic might need to send over 150 alerts from the bot account per hour. Im thinking it's also used for apps that try to deliver tweets in 'realtime' by requesting the REST API very frequently rather than use the streaming APIs. Perhaps it's also used to make multiple requests to /users/show via a cronjob that makes sure all the user's of the site have an up to date profile image and background image cached. (If a user changes their profile picture on Twitter, your cached URL 404's) Anyway I've only used whitelisting for the first (notifying users when they are tagged into photos - or when they are invited to events on twappening.com) -Sam @sampicli http://twicli.com On Aug 16, 12:16 pm, boaz sapirb...@gmail.com wrote: Hello, I am new to Twitter API and I am trying to understand whether I should apply for whitelisting my application. The documentation says: IP whitelisting takes precedence to account rate limits. GET requests from a whitelisted IP address made on a user's behalf will be deducted from the whitelisted IP's limit, not the users. Therefore, IP-based whitelisting is a best practice for applications that request many users' data. However if for example 200 users are accessing twitter through my application in one hour, and each access from my app to twitter is done with the relevant end user as the twitter authenticated user, I can do 200*150=3 API calls in one hours without whitelisting the IP address, which is more than the 2 I could do with whitelisting. Can anyone give a counter example where whitelisting is absolutely necessary? Thank you, Boaz
[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 jonat...@jdg.net 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 d...@twitter.com 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] OAuth on client side
Hi, I was wondering is there a way to implement OAuth and Twitter functionality without server going out to twitter.com? We have servers that are closed to external websites. Yet the client side application should be Twitter Enabled. Is that possible?
[twitter-dev] Re: Platform downtime is expected
Can't agree more with 2. Please guys, you need to convey a consistant and *visible* message to your users. On 16 août, 05:21, Jonathan George jonat...@jdg.net 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 d...@twitter.com 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: How do you store the social graph locally?
We're using MongoDB and store them as arrays of integers as provided by the API. That makes for some simple yet powerful queries: http://www.mongodb.org/display/DOCS/Advanced+Queries#AdvancedQueries-ValueinanArray Wynn Netherland twitter: pengwynn http://floxee.com http://tweetcongress.org On Sat, Aug 15, 2009 at 9:24 AM, Arik Fraimovich arik...@gmail.com wrote: I was wondering how you store a local cache of the social graph methods results locally in your applications. One obvious solution is to create a two column table of the relations, but in such case how do you update it? Just prune everything of the user you're updating and inserting from the beginning? The other solution is to store the results of the API calls as blobs to the DB and parse them everytime in code instead of by SQL queries. The problem I can see with that is duplication of data, less ability to do smart stuff with the data and other issues. Would love to hear how you implemented it in your apps and other ideas related. Thanks, -- Arik Fraimovich follow me on twitter: http://twitter.com/arikfr -- Wynn Netherland twitter: pengwynn
[twitter-dev] Re: When is whitelisting necessary?
http://groups.google.co.in/group/twitter-development-talk/browse_thread/thread/e75daf87a23a0a61# On Sun, Aug 16, 2009 at 7:37 PM, Sam Street sam...@gmail.com wrote: Necessary, for example, if you use a particular account to notify your users of a certain event (sending them notifications). Large apps with high traffic might need to send over 150 alerts from the bot account per hour. Im thinking it's also used for apps that try to deliver tweets in 'realtime' by requesting the REST API very frequently rather than use the streaming APIs. Perhaps it's also used to make multiple requests to /users/show via a cronjob that makes sure all the user's of the site have an up to date profile image and background image cached. (If a user changes their profile picture on Twitter, your cached URL 404's) Anyway I've only used whitelisting for the first (notifying users when they are tagged into photos - or when they are invited to events on twappening.com) -Sam @sampicli http://twicli.com On Aug 16, 12:16 pm, boaz sapirb...@gmail.com wrote: Hello, I am new to Twitter API and I am trying to understand whether I should apply for whitelisting my application. The documentation says: IP whitelisting takes precedence to account rate limits. GET requests from a whitelisted IP address made on a user's behalf will be deducted from the whitelisted IP's limit, not the users. Therefore, IP-based whitelisting is a best practice for applications that request many users' data. However if for example 200 users are accessing twitter through my application in one hour, and each access from my app to twitter is done with the relevant end user as the twitter authenticated user, I can do 200*150=3 API calls in one hours without whitelisting the IP address, which is more than the 2 I could do with whitelisting. Can anyone give a counter example where whitelisting is absolutely necessary? Thank you, Boaz
[twitter-dev] Re: Platform downtime is expected
Same for us, please let us know if there is anything we can provide / do to restore oAuth access to our app. Some other comp. web-based apps work 100%, so this is kind of embarrassing... Many thanks in advance. On 16 août, 17:41, Sean Callahan seancalla...@gmail.com wrote: Yeah, no one can login tohttp://TweetPhoto.comjust 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 jonat...@jdg.net 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 d...@twitter.com 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
Doug: 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. Do you guys have any news on the Oauth outage? We can still not authenticate our users (tweetfunnel.com). thanks, Johan
[twitter-dev] Re: Platform downtime is expected
Me neither On Aug 16, 12:32 pm, johan pretorius johan.pretor...@gmail.com wrote: Doug: 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. Do you guys have any news on the Oauth outage? We can still not authenticate our users (tweetfunnel.com). thanks, Johan
[twitter-dev] Re: Platform downtime is expected
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? On Aug 16, 10:35 am, Ritvvij ritvi...@gmail.com wrote: Me neither On Aug 16, 12:32 pm, johan pretorius johan.pretor...@gmail.com wrote: Doug: 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. Do you guys have any news on the Oauth outage? We can still not authenticate our users (tweetfunnel.com). thanks, Johan
[twitter-dev] Re: Platform downtime is expected
On Sun, Aug 16, 2009 at 1:40 PM, bosherbhellm...@gmail.com 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)
[twitter-dev] Re: Platform downtime is expected
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 Baderaand...@badera.us wrote: On Sun, Aug 16, 2009 at 1:40 PM, bosherbhellm...@gmail.com 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)
[twitter-dev] Re: Open Auth
Hi Kevin, With basic auth, its nice because you can use those credentials anywhere. I *was* working on a collaboration site, until I heard basic auth was going away, because I was able to use credentials for dozens of services around a single profile. I asked the same question about oAuth, i.e. can I validate with oAuth and then allow these users to show tokens to other oAuth enabled services and let them proceed. The answer I got *then* was no. Hopefully this will change, as the other path presented so many cool options. Anyway, retweet.com looks very cool. Peter On Sun, Aug 16, 2009 at 6:07 AM, Kevin Mesiab ke...@mesiablabs.com wrote: When a user signs up at TwitPic, for instance, the same credentials they used for Twitter are now valid for use in uploading media. This lets users enjoy a bit of a mash-up with a single sign-on. Is this also true when authorized via openAuth? -- Kevin Mesiab CEO, Mesiab Labs L.L.C. http://twitter.com/kmesiab http://mesiablabs.com http://retweet.com
[twitter-dev] Re: When is whitelisting necessary?
I think the number of So how does whitelisting really work? threads that have taken place, and continue to take place on this list indicate a lack of clarity in documentation. Perhaps someone from Twitter can take the task of updating the rate limiting docs to more explicitly spell out how it actually works? Boaz - as the thread Srikanth referenced states, official word from Twitter is that you get 20,000 calls per hour *per user* from your whitelisted IP. (Of course, it's not that cut and dried - POSTs are different than GETs are different than searches, but in a nutshell you can expect to make 20,000 authenticated GETs per user per hour regardless of how many simultaneous users are on your site if your IP is whitelisted; they're not all sharing a single pool of 20,000 requests.) I'll leave it to you to decide if you need that or not. Most apps that are just acting as a client probably don't, but there are some edge cases where it's useful. For a long time I had no intentions of having Ambeur whitelisted, but now there's a feature I want to offer my users that I'll need it for, so I've applied. And no, I'm not telling you what the feature is. ;) On Aug 16, 1:22 pm, srikanth reddy srikanth.yara...@gmail.com wrote: http://groups.google.co.in/group/twitter-development-talk/browse_thre... On Sun, Aug 16, 2009 at 7:37 PM, Sam Street sam...@gmail.com wrote: Necessary, for example, if you use a particular account to notify your users of a certain event (sending them notifications). Large apps with high traffic might need to send over 150 alerts from the bot account per hour. Im thinking it's also used for apps that try to deliver tweets in 'realtime' by requesting the REST API very frequently rather than use the streaming APIs. Perhaps it's also used to make multiple requests to /users/show via a cronjob that makes sure all the user's of the site have an up to date profile image and background image cached. (If a user changes their profile picture on Twitter, your cached URL 404's) Anyway I've only used whitelisting for the first (notifying users when they are tagged into photos - or when they are invited to events on twappening.com) -Sam @sampiclihttp://twicli.com On Aug 16, 12:16 pm, boaz sapirb...@gmail.com wrote: Hello, I am new to Twitter API and I am trying to understand whether I should apply for whitelisting my application. The documentation says: IP whitelisting takes precedence to account rate limits. GET requests from a whitelisted IP address made on a user's behalf will be deducted from the whitelisted IP's limit, not the users. Therefore, IP-based whitelisting is a best practice for applications that request many users' data. However if for example 200 users are accessing twitter through my application in one hour, and each access from my app to twitter is done with the relevant end user as the twitter authenticated user, I can do 200*150=3 API calls in one hours without whitelisting the IP address, which is more than the 2 I could do with whitelisting. Can anyone give a counter example where whitelisting is absolutely necessary? Thank you, Boaz
[twitter-dev] Re: Platform downtime is expected
The API team is actively debugging the OAuth issues as we speak. This is what worries very much. I can't even do this without timing out: curl http://twitter.com/account/rate_limit_status.xml? screen_name=hboon I have no API access *at all*. -- Hwee-Boon
[twitter-dev] Re: Platform downtime is expected
Thanks for the update Chad.. On Aug 16, 10:52 am, Chad Etzel jazzyc...@gmail.com 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 Baderaand...@badera.us wrote: On Sun, Aug 16, 2009 at 1:40 PM, bosherbhellm...@gmail.com 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)
[twitter-dev] Re: php regex for twitter password
Do you mean to verify proper length and character composition? I don't know of publicized documentation other then passwords have minimum length of 6 characters. Abraham On Sat, Aug 15, 2009 at 01:33, Xpineapple kenned...@gmail.com wrote: I could probably play with regex all day and get no where (and so far am). While I could make some progress, I don't know all the rules for a good password. My intent is to ensure server (and service) are safe. With that in mind, can anyone provide a fair enough regex example of sanatizing a password for twitter service? Thanx. -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: php regex for twitter password
At least 6 At least one capital letter At least one non-capital letter At least on numeric [Stronger] At least 8 At least one non-alphanumeric I'd love to provide a RegEx ... only : a) I live in the .NET world not PHP, and, b) There are TONS -- BAJILLIONS -- of password regexes available on the interwebs that describe every frickin' reasonable permutation of such. ∞ Andy Badera ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera) On Sat, Aug 15, 2009 at 2:33 AM, Xpineapplekenned...@gmail.com wrote: I could probably play with regex all day and get no where (and so far am). While I could make some progress, I don't know all the rules for a good password. My intent is to ensure server (and service) are safe. With that in mind, can anyone provide a fair enough regex example of sanatizing a password for twitter service? Thanx.
[twitter-dev] Re: Platform downtime is expected
Not sure if this will help or not, regarding oAuth Sign in With Twitter Works - Sign in With Twitter works if the user isn't logged into Twitter and has to enter their LP on Twitter Doesn't Work - If the user is already signed into Twitter, clicks Allow, it just hangs... On Aug 16, 11:40 am, bosher bhellm...@gmail.com wrote: Thanks for the update Chad.. On Aug 16, 10:52 am, Chad Etzel jazzyc...@gmail.com 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 Baderaand...@badera.us wrote: On Sun, Aug 16, 2009 at 1:40 PM, bosherbhellm...@gmail.com 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)
[twitter-dev] Re: Platform downtime is expected
Can you at the very least PLEASE publish something on status.twitter.com about the API being down and/or very unresponsive at times, so that I have a link where I can refer my users, so that they can see I am not shitting them? Dewald
[twitter-dev] Re: Platform downtime is expected
We've asked the keeper-o-the-blog to post something to that effect. Hopefully it will appear soon. -Chad On Sun, Aug 16, 2009 at 4:42 PM, Dewald Pretoriusdpr...@gmail.com wrote: Can you at the very least PLEASE publish something on status.twitter.com about the API being down and/or very unresponsive at times, so that I have a link where I can refer my users, so that they can see I am not shitting them? Dewald
[twitter-dev] Re: Platform downtime is expected
Can you confirm if OAuth access is the only known issue? I feel silly repeating the same question over and over again: Even / rate_limit_status calls are timing out on my server. I have no API access *at all*. -- Hwee-Boon On Aug 17, 5:21 am, Chad Etzel jazzyc...@gmail.com wrote: We've asked the keeper-o-the-blog to post something to that effect. Hopefully it will appear soon. -Chad On Sun, Aug 16, 2009 at 4:42 PM, Dewald Pretoriusdpr...@gmail.com wrote: Can you at the very least PLEASE publish something on status.twitter.com about the API being down and/or very unresponsive at times, so that I have a link where I can refer my users, so that they can see I am not shitting them? Dewald
[twitter-dev] Re: Platform downtime is expected
Everyone, Please see the updated post on status.twitter.com - http://status.twitter.com/post/164410057/trouble-with-oauth-and-api-clients. We are continuing to assess the issue and will report back when we know more. Thanks for your patience, Ryan On Sun, Aug 16, 2009 at 2:32 PM, Hwee-Boon Yarhweeb...@gmail.com wrote: Can you confirm if OAuth access is the only known issue? I feel silly repeating the same question over and over again: Even / rate_limit_status calls are timing out on my server. I have no API access *at all*. -- Hwee-Boon On Aug 17, 5:21 am, Chad Etzel jazzyc...@gmail.com wrote: We've asked the keeper-o-the-blog to post something to that effect. Hopefully it will appear soon. -Chad On Sun, Aug 16, 2009 at 4:42 PM, Dewald Pretoriusdpr...@gmail.com wrote: Can you at the very least PLEASE publish something on status.twitter.com about the API being down and/or very unresponsive at times, so that I have a link where I can refer my users, so that they can see I am not shitting them? Dewald
[twitter-dev] Oauth timeout?
Hi guys, I'm still getting oauth timeout issues (on twitters side). Repro steps in safari 3.1: 1. go to twitterplaces.com 2. press 'Allow' 3. press 'Allow' 4. wait for eternity... If I restart safari, clear cookies and try again then it usually works. I'd sure like to have this fixed, because it's preventing my friends from signing in. :) Ben (i'm cloning foursquare)
[twitter-dev] Re: Oauth timeout?
1. Read http://groups.google.com/group/twitter-development-talk/browse_thread/thread/4655448e637baa81 2. Wait On Aug 16, 5:52 pm, benn bno...@gmail.com wrote: Hi guys, I'm still getting oauth timeout issues (on twitters side). Repro steps in safari 3.1: 1. go to twitterplaces.com 2. press 'Allow' 3. press 'Allow' 4. wait for eternity... If I restart safari, clear cookies and try again then it usually works. I'd sure like to have this fixed, because it's preventing my friends from signing in. :) Ben (i'm cloning foursquare)
[twitter-dev] Re: Platform downtime is expected
Thanks Ryan, but unfortunately that does not help me. It does not tell my users that most, if not all calls to the API are being rejected with connection refused. In other words, from my perspective, the API is completely down / inoperative / unresponsive. My issue has nothing to do with OAuth. Dewald On Aug 16, 7:41 pm, Ryan Sarver rsar...@twitter.com wrote: Everyone, Please see the updated post on status.twitter.com -http://status.twitter.com/post/164410057/trouble-with-oauth-and-api-c We are continuing to assess the issue and will report back when we know more. Thanks for your patience, Ryan On Sun, Aug 16, 2009 at 2:32 PM, Hwee-Boon Yarhweeb...@gmail.com wrote: Can you confirm if OAuth access is the only known issue? I feel silly repeating the same question over and over again: Even / rate_limit_status calls are timing out on my server. I have no API access *at all*. -- Hwee-Boon On Aug 17, 5:21 am, Chad Etzel jazzyc...@gmail.com wrote: We've asked the keeper-o-the-blog to post something to that effect. Hopefully it will appear soon. -Chad On Sun, Aug 16, 2009 at 4:42 PM, Dewald Pretoriusdpr...@gmail.com wrote: Can you at the very least PLEASE publish something on status.twitter.com about the API being down and/or very unresponsive at times, so that I have a link where I can refer my users, so that they can see I am not shitting them? Dewald
[twitter-dev] Re: Platform downtime is expected
From my side, it looks as if Operations are once again not allowing volume white-listed API traffic through the defenses. It's almost as if last weekend did not happen, and no lessons were learned from it. I am not once again going to throw my toys out of the cot. It was only on Friday that I found my favorite rubber duck underneath my mom's bed. Dewald PS. Please ask them to fix it ASAP. The way things are going now, it is neither easy, nor attractive to provide services that use the Twitter API.
[twitter-dev] Re: Platform downtime is expected
Anyone having troubles also with profile image / background update API endpoints? I'm getting 500 errors so I'm guessing the error is on twitter's end. Just want to be sure its not my code. Josh
[twitter-dev] Re: OAuth on client side
How do you expect to use Twitter if you can't get to Twitter? On Sun, Aug 16, 2009 at 09:00, JONNiE` arse...@gmail.com wrote: Hi, I was wondering is there a way to implement OAuth and Twitter functionality without server going out to twitter.com? We have servers that are closed to external websites. Yet the client side application should be Twitter Enabled. Is that possible? -- Internets. Serious business.
[twitter-dev] Re: OAuth on client side
On Sun, Aug 16, 2009 at 11:00 AM, JONNiE`arse...@gmail.com wrote: Hi, I was wondering is there a way to implement OAuth and Twitter functionality without server going out to twitter.com? We have servers that are closed to external websites. Yet the client side application should be Twitter Enabled. Is that possible? laconi.ca? XMPP? Facebook? ∞ Andy Badera ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)
[twitter-dev] Re: MyTwitterButler.com Legal issues Update 2
On Sun, Aug 16, 2009 at 3:57 AM, Nicole Simonnee...@gmail.com wrote: It is going to be interesting if they try to go after twit - as far as I know this is a trademark which belongs to leo laporte and the trademark department only has so many classes available. not exactly knowing the US system but I do assume 'that computery or internet one' is already taken by twit / leo laport. No, the Twit trademark doesn't cover most of the Twitter-related use of it[1]. Although some uses (such as TwitVid) may be considered trademark infringement under the Twit trademark. [1] http://tess2.uspto.gov/bin/showfield?f=docstate=4002:5a6vq8.2.1 -- Matt Freedman http://mattfreedman.ca/
[twitter-dev] Re: My Issue with the ReTweet API and my solutions
On Sat, Aug 15, 2009 at 10:00:30AM +0100, Paul Kinlan wrote: Hi Guys, When I saw the original message stating that the retweet API I was about to say straight away that I despise the idea, but I thought I would refrain - give it some thought. I still despise the idea and I have to make it known the reasons why I think it is a very very bad idea and in the long term will negatively affect Twitter as a communications platform for the future. 1. You are embedding a user developed based meme into the Twitter infrastructure - the popularity of RT itself may wane after some point. Users are very fickle, they change their minds, take a stand and don't listen to them - you know your platform and I am pretty sure you know that this is a bit of a hack.  Let users use they system how they want, they will evolve how they use it, constraints via an API 1. Twitter already has the capability to do smarter things that completely negate the need for this API if they just change the current API a little Not every app will use RT API (especially legacy ones) and not every user will use it and as such Twitter and this list will get lots of questions why certain RT's are accessible by the retweet API.  Again, RT's are a user concept, and is very easy for them not use. Whilst I use TweetDeck, I really dislike the amount of utility buttons it has and the amount of options it has - introducing another API for another function is tantamount to the same thing, you are asking us app developers to include more options in our apps.  The great thing about a RT is that I just hit reply and type RT at the front. A big thing that people have requested is that quite often there is not any room in the very limited 140 characters to add comment to a retweet, this doesn't seem to solve that problem. Authority of a user based on a RT and credit to the originator is a misnomer, no one actually needs it, very very few people care about - and when they do care about not getting the credit for the original tweet you have to ask why do they care? and why should we care? again it is still very easy to bypass.  If you have a problem with it, as per the Twitter TOS you are the copyright holder of your content. My honest vote is not to pollute the Twitter API with a special RT capability, rather: * Enhance Favorites and the favorites API, allow me to get a list of everyone's favorites, allow me to see a list of people who favorited a tweet.  If you look at the proposal for RT API it is doing something similar to this. The entire UX for Favorites makes a lot more sense than retweet - infact you can go as far as saying if you like something favorite (star) it, if you really like your favorite - Forward (RT). * Allow me to get a list of a users favorites (similar to the Likes feed in FriendFeed) - this type of concept is so powerful, I can discover people who share very similar likes.  I can also do Best of Day very easily Enhance in_reply_to, allow me to see all tweets that reply to this tweet in an object returned by the current api ( that is so I don't have to keep re-querying the search API), further more allow me to request N levels deep of replies to a given tweet (yes this is similar to threaded comments) So by enhancing Replies and favorites you can remove the need for special RT API because you can combine both parts of the API to get at the originator of a popular tweet, have notification and visual queues of popular tweets. thus keeping the twitter API simple. I agree on everything Paul Kinlan here so clearly expressed. +1 to enhancing the replies and favs first. -- | : Marteen | : CA49 DEE9 7F5B A373 5121 2F82 1047 1BB9 83EC D3C9 |__
[twitter-dev] Re: Platform downtime is expected
I agree. Its hard to convince people to use twitter API if it goes down for days and that too this frequently :( On Aug 16, 4:35 pm, Dewald Pretorius dpr...@gmail.com wrote: From my side, it looks as if Operations are once again not allowing volume white-listed API traffic through the defenses. It's almost as if last weekend did not happen, and no lessons were learned from it. I am not once again going to throw my toys out of the cot. It was only on Friday that I found my favorite rubber duck underneath my mom's bed. Dewald PS. Please ask them to fix it ASAP. The way things are going now, it is neither easy, nor attractive to provide services that use the Twitter API.
[twitter-dev] Re: Platform downtime is expected
Dewald, What exact issues are you having? Can you please provide packet dumps or more information so we can debug? Thanks, Ryan On Sun, Aug 16, 2009 at 4:18 PM, Dewald Pretoriusdpr...@gmail.com wrote: Thanks Ryan, but unfortunately that does not help me. It does not tell my users that most, if not all calls to the API are being rejected with connection refused. In other words, from my perspective, the API is completely down / inoperative / unresponsive. My issue has nothing to do with OAuth. Dewald On Aug 16, 7:41 pm, Ryan Sarver rsar...@twitter.com wrote: Everyone, Please see the updated post on status.twitter.com -http://status.twitter.com/post/164410057/trouble-with-oauth-and-api-c We are continuing to assess the issue and will report back when we know more. Thanks for your patience, Ryan On Sun, Aug 16, 2009 at 2:32 PM, Hwee-Boon Yarhweeb...@gmail.com wrote: Can you confirm if OAuth access is the only known issue? I feel silly repeating the same question over and over again: Even / rate_limit_status calls are timing out on my server. I have no API access *at all*. -- Hwee-Boon On Aug 17, 5:21 am, Chad Etzel jazzyc...@gmail.com wrote: We've asked the keeper-o-the-blog to post something to that effect. Hopefully it will appear soon. -Chad On Sun, Aug 16, 2009 at 4:42 PM, Dewald Pretoriusdpr...@gmail.com wrote: Can you at the very least PLEASE publish something on status.twitter.com about the API being down and/or very unresponsive at times, so that I have a link where I can refer my users, so that they can see I am not shitting them? Dewald
[twitter-dev] Re: Platform downtime is expected
Please test your OAuth apps to see if you are still having issues. We have made a number of changes in the network and they should be operational again. Please let me know if you are still having any other problems. Ryan On Sun, Aug 16, 2009 at 3:41 PM, Ryan Sarverrsar...@twitter.com wrote: Everyone, Please see the updated post on status.twitter.com - http://status.twitter.com/post/164410057/trouble-with-oauth-and-api-clients. We are continuing to assess the issue and will report back when we know more. Thanks for your patience, Ryan On Sun, Aug 16, 2009 at 2:32 PM, Hwee-Boon Yarhweeb...@gmail.com wrote: Can you confirm if OAuth access is the only known issue? I feel silly repeating the same question over and over again: Even / rate_limit_status calls are timing out on my server. I have no API access *at all*. -- Hwee-Boon On Aug 17, 5:21 am, Chad Etzel jazzyc...@gmail.com wrote: We've asked the keeper-o-the-blog to post something to that effect. Hopefully it will appear soon. -Chad On Sun, Aug 16, 2009 at 4:42 PM, Dewald Pretoriusdpr...@gmail.com wrote: Can you at the very least PLEASE publish something on status.twitter.com about the API being down and/or very unresponsive at times, so that I have a link where I can refer my users, so that they can see I am not shitting them? Dewald
[twitter-dev] Re: Platform downtime is expected
Oauth integration started working for me. On Aug 16, 7:51 pm, goodtest goodtest...@gmail.com wrote: I agree. Its hard to convince people to use twitter API if it goes down for days and that too this frequently :( On Aug 16, 4:35 pm, Dewald Pretorius dpr...@gmail.com wrote: From my side, it looks as if Operations are once again not allowing volume white-listed API traffic through the defenses. It's almost as if last weekend did not happen, and no lessons were learned from it. I am not once again going to throw my toys out of the cot. It was only on Friday that I found my favorite rubber duck underneath my mom's bed. Dewald PS. Please ask them to fix it ASAP. The way things are going now, it is neither easy, nor attractive to provide services that use the Twitter API.
[twitter-dev] Re: Platform downtime is expected
Ryan, I am having exactly the same issue as last Saturday and early Sunday. Low volume API calls go through, but the moment you make a lot of calls from the same IP address, you are completely blocked and get connection refused. Operations need to do the same that they did last Sunday, when they allowed high volume calls from white-listed IP addresses through the defenses. Dewald On Aug 16, 10:11 pm, Ryan Sarver rsar...@twitter.com wrote: Dewald, What exact issues are you having? Can you please provide packet dumps or more information so we can debug? Thanks, Ryan
[twitter-dev] Re: My Issue with the ReTweet API and my solutions
I just wanted to point out a few counterpoints to Paul's arguments. I think it's important that they are brought up and I hope they are taken at face value and not construed in any way as a personal attack. 1. The mentions API evolved from the @reply convention and originally was also a 'user developed based meme' that Twitter decided to incorporate into their site and API. The mentions API is now a key part of the Twitter landscape and I don't think anyone can imagine Twitter without that API. The retweet convention has been used by the twitter community for as long as I have been a part of it. I don't see the community 'changing its mind about it' anytime soon. 2. Virtually all third-party clients support some method of retweeting. This new API would not add clutter to a client's functionality as the method is already supported. In fact, it would serve to standardize the retweet method, which is a good thing as clients format retweets differently. (Even TweetDeck has a retweet button. Not sure why you don't just use it instead of 'hitting reply and typing RT at the front'.) As a third-party developer, I am bummed at the thought of having to rebuild my app to support the new 'timelines' that Twitter is requiring clients to support, but for the sake of evolution of the platform, I am happy to see the progress. I also somewhat agree that the solution to adding comments and crediting the originating authority is hacky and will not satisfy everyone's retweet needs, it brings it closer. And I fully support progress . . . as long as it's in the right direction. No matter how small. Will http://twitter.com/wymesei http://twitterneni.com On Aug 15, 7:00 pm, Paul Kinlan paul.kin...@gmail.com wrote: Hi Guys, When I saw the original message stating that the retweet API I was about to say straight away that I despise the idea, but I thought I would refrain - give it some thought. I still despise the idea and I have to make it known the reasons why I think it is a very very bad idea and in the long term will negatively affect Twitter as a communications platform for the future. 1. You are embedding a user developed based meme into the Twitter infrastructure - the popularity of RT itself may wane after some point. Users are very fickle, they change their minds, take a stand and don't listen to them - you know your platform and I am pretty sure you know that this is a bit of a hack. Let users use they system how they want, they will evolve how they use it, constraints via an API 1. Twitter already has the capability to do smarter things that completely negate the need for this API if they just change the current API a little 2. Not every app will use RT API (especially legacy ones) and not every user will use it and as such Twitter and this list will get lots of questions why certain RT's are accessible by the retweet API. Again, RT's are a user concept, and is very easy for them not use. 3. Whilst I use TweetDeck, I really dislike the amount of utility buttons it has and the amount of options it has - introducing another API for another function is tantamount to the same thing, you are asking us app developers to include more options in our apps. The great thing about a RT is that I just hit reply and type RT at the front. 4. A big thing that people have requested is that quite often there is not any room in the very limited 140 characters to add comment to a retweet, this doesn't seem to solve that problem. 5. Authority of a user based on a RT and credit to the originator is a misnomer, no one actually needs it, very very few people care about - and when they do care about not getting the credit for the original tweet you have to ask why do they care? and why should we care? again it is still very easy to bypass. If you have a problem with it, as per the Twitter TOS you are the copyright holder of your content. My honest vote is not to pollute the Twitter API with a special RT capability, rather: - Enhance Favorites and the favorites API, allow me to get a list of everyone's favorites, allow me to see a list of people who favorited a tweet. If you look at the proposal for RT API it is doing something similar to this. The entire UX for Favorites makes a lot more sense than retweet - infact you can go as far as saying if you like something favorite (star) it, if you really like your favorite - Forward (RT). - Allow me to get a list of a users favorites (similar to the Likes feed in FriendFeed) - this type of concept is so powerful, I can discover people who share very similar likes. I can also do Best of Day very easily - Enhance in_reply_to, allow me to see all tweets that reply to this tweet in an object returned by the current api ( that is so I don't have to keep re-querying the search API),
[twitter-dev] If my site was being rate limited, would I get this error? Error #110: Connection timed out
Hi all,
We are developing a social network and part of the functionality is to
allow the user to enter their twitter user name and display their
public twitter feed on their profile.
I am using Zend Framework and until recently, our testing was working
just fine. A user could simply enter their user name and we would
retrieve and display their timeline.
Now, we are getting a connection timeout Error #110: Connection timed
out
Is this possibly because we are being rate limited? I doubt it because
we have no users yet.. just our own internal testing.. but I can't see
why this would just stop working.
This is the line of code we are using
$client = new Zend_Http_Client('http://twitter.com/statuses/
user_timeline.json?screen_name=' . $user-
twitter_id .'count=50page=1');
$response = $client-request();
So we're basically just retrieving a json feed.
Any ideas?
Thanks in advance
[twitter-dev] Re: Platform downtime is expected
Is anyone at Twitter going to look at this and get back with an update or answer? On Aug 16, 10:40 pm, Dewald Pretorius dpr...@gmail.com wrote: Ryan, I am having exactly the same issue as last Saturday and early Sunday. Low volume API calls go through, but the moment you make a lot of calls from the same IP address, you are completely blocked and get connection refused. Operations need to do the same that they did last Sunday, when they allowed high volume calls from white-listed IP addresses through the defenses. Dewald On Aug 16, 10:11 pm, Ryan Sarver rsar...@twitter.com wrote: Dewald, What exact issues are you having? Can you please provide packet dumps or more information so we can debug? Thanks, Ryan
[twitter-dev] Re: OAuth on client side
I can use Twitter from CLient Side... What I am trying to avoid is calling Twitter from Server side 2009/8/17 JDG ghil...@gmail.com How do you expect to use Twitter if you can't get to Twitter? On Sun, Aug 16, 2009 at 09:00, JONNiE` arse...@gmail.com wrote: Hi, I was wondering is there a way to implement OAuth and Twitter functionality without server going out to twitter.com? We have servers that are closed to external websites. Yet the client side application should be Twitter Enabled. Is that possible? -- Internets. Serious business.
[twitter-dev] Re: If my site was being rate limited, would I get this error? Error #110: Connection timed out
Most likely its probably just a temporary issue going on with twitter's
servers.
It will probably clear up on its own once twitter becomes stable again.
On Sun, Aug 16, 2009 at 9:35 PM, mapes911 mapes...@gmail.com wrote:
Hi all,
We are developing a social network and part of the functionality is to
allow the user to enter their twitter user name and display their
public twitter feed on their profile.
I am using Zend Framework and until recently, our testing was working
just fine. A user could simply enter their user name and we would
retrieve and display their timeline.
Now, we are getting a connection timeout Error #110: Connection timed
out
Is this possibly because we are being rate limited? I doubt it because
we have no users yet.. just our own internal testing.. but I can't see
why this would just stop working.
This is the line of code we are using
$client = new Zend_Http_Client('http://twitter.com/statuses/
user_timeline.json?screen_name=http://twitter.com/statuses/%0Auser_timeline.json?screen_name='
. $user-
twitter_id .'count=50page=1');
$response = $client-request();
So we're basically just retrieving a json feed.
Any ideas?
Thanks in advance
--
Josh
