[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 sam...@gmail.com wrote: I haven't experienced any downtime or lack of connectivity so far. On Aug 15, 7:16 pm, dougw d...@twitter.com 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 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] White Listing request
Hello, I'm working on a new twitter service and I was wondering if I can request white listing while I'm developing the service. Thanks,
[twitter-dev] call back issues
Hi, development env: ruby on rails oauth: 0.3.5 gem used: twitter_oauth My code to call twitter is client = TwitterOAuth::Client.new( :consumer_key = Attribute::CONSUMER_KEY, :consumer_secret = Attribute::CONSUMER_SECRET) request_token = client.request_token(:oauth_callback = 'http://abc/ authorization/') redirect_to request_token.authorize_url After this, the control goes to http://twitter.com/oauth/authorize?oauth_token=k* Here the user puts his twitter userid password pressed APPROVE and gets redirected to http://twitter.com/oauth/authorize instead of my call back URL. Can someone guide why?
[twitter-dev] Re: MyTwitterButler.com Legal issues Update 2
The scariest part about all of this, frankly, is less the trademark stuff, and more the fact that he is being punished for violating Twitter's terms and services. As near as I can tell, his app just follows users who tweet certain keywords. It doesn't even UNFOLLOW them (thus potentially churning), it just follows people. Since there are API calls for those actions, many of us have built rich apps around follow. Indeed, Twitter DOES support mass following... if not, why would batch following be in their roadmap (http://apiwiki.twitter.com/V2-Roadmap#Following )... To now see another app taken down because of supposed API violations around mass following is very scary. And what's even MORE scary is the selectivity of it. Why was this little guy taken down? What about, say, the popular downloadable XYZ app which apparently does what tweetbutler does and then some? Do they have some more formal relationship with Twitter? Or do their other apps somehow inculcate them against violating TS? It's a minefield out there, and that's VERY VERY scary. Who knows if the API calls you make today might violate terms and services tomorrow? Perhaps you can count your lucky stars if you have casual email correspondence with a Twitter engineer... maybe that's what's needed to fend off trouble? And too bad for those guys over in England, like this guy, who perhaps didn't have such a relationship!
[twitter-dev] Re: Platform downtime is expected
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 seancalla...@gmail.comwrote: 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 sam...@gmail.com wrote: I haven't experienced any downtime or lack of connectivity so far. On Aug 15, 7:16 pm, dougw d...@twitter.com 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 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] If you see 417 Expectation Failed this post might help
I started to occasionally get a 417 response from Twitter when my
application was using cURL to fetch an OAuth Request Token.
The response would contain
417 Expectation Failed
The expectation given in the Expect request-header field could not be
met by this server.
The client sent
Expect: 100-continue
but we only allow the 100-continue expectation.
I found the answer here:
http://www.shoemoney.com/2008/12/29/lib-curl-twitter-api-expect-100-continue-pain-and-how-to-fix-it/
I thought it would be useful to post it to the group here in case
anyone else is searching these posts for a reference to this issue.
Why did I get the 417 response?
Apparently cURL started adding the header Expect: 100-continue when
my POST exceeded 1024 bytes.
Why was my POST so large?
I was specifying a callback URL with some long query arguments.
What was the quick fix?
In Perl, the solution was to add an empty Expect header:
my @myheaders=(
Expect:
);
$curl-setopt(CURLOPT_HTTPHEADER, \...@myheaders);
The link I referenced above provided the PHP solution:
curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
Hopefully this might save someone a few hours down the road ...
- Scott
@scott_carter
[twitter-dev] Re: php regex for twitter password
Depending on your deployment scenario, you could let Google do the heavy lifting for you ;) https://www.google.com/accounts/RatePassword?Passwd=poopy On Sat, Aug 15, 2009 at 10:43 AM, Sam Streetsam...@gmail.com wrote: http://pastebin.com/m4fd058a4 This code will be able to determine whether a password is weak, ok or strong based on whether it contains lowercase, uppercase + numbers hope thats what you were after -Sam @sampicli http://twicli.com On Aug 15, 7:33 am, 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. -- Kevin Mesiab CEO, Mesiab Labs L.L.C. http://twitter.com/kmesiab http://mesiablabs.com http://retweet.com
[twitter-dev] Re: I must be stupid.
This library worked perfectly for me
http://github.com/jmathai/twitter-async/tree/master
On Aug 15, 6:28 am, Adam Shannon a...@ashannon.us wrote:
On Fri, Aug 14, 2009 at 5:37 PM, Chad Etzel c...@twitter.com wrote:
Hi Adam,
If you really want to learn this yourself, the best method is to read
through the oAuth spec here:
http://oauth.net/core/1.0a
This explains exactly how to create the signatures, etc...
-Chad
On Fri, Aug 14, 2009 at 6:34 PM, Adam Shannona...@ashannon.us wrote:
On Fri, Aug 14, 2009 at 5:30 PM, Peter Denton petermden...@gmail.com
wrote:
Hi Adam,
If you want you can email me off list and I can help you use Abrahams.
Its
really about as simple as something as going to be that you can trust
will
work. Else, you might end up creating a lot of issues without knowing
it.
Regards
Peter
On Fri, Aug 14, 2009 at 3:25 PM, Julio Biason julio.bia...@gmail.com
wrote:
On Sat, Aug 15, 2009 at 7:25 AM, Adam Shannona...@ashannon.us wrote:
foreach ($oauth['parms'] as $parm) {
$request_uri = $request_uri . $parm;
}
Well, you didn't state the results you're getting (which error) so I'm
just guessing here. If I'm not mistaken, PHP uses a hash for array
indexes and, thus, it may be adding the elements in the $request_uri
in the wrong order. I can't remember how to do that in PHP, but in
Python it would be something like:
for key in sort(oauth['params'].keys()):
request_uri += oauth['params'][key]
--
Julio Biason julio.bia...@gmail.com
Twitter:http://twitter.com/juliobiason
@Julio
Thanks, the error is:
Failed to validate oauth signature and token.
Also, do the attributes need to be in some specified order?
@Peter
I would really like to teach myself how to do this rather then just
taking a
framework and relying on blackbox operations.
--
- Adam Shannon (http://ashannon.us)
Many thanks, I've read some of the spec before but I shall read the entire
thing tomorrow.
--
- Adam Shannon (http://ashannon.us)
[twitter-dev] Re: How do you store the social graph locally?
Your implementation here has much to do with how you intend to use the social graph. Are you simply caching, or do you intend to identify metrics by analyzing the shape of the relationships over time? If you're simply creating a local cache, blowing away the existing store and serializing the response from the api call is sufficient, since you cannot divide the results except by page. If you intend to get a little fancier, there are plenty of algorithms for diff'ing the results. Your saving grace is that the result set is a list of integers. If you take a little time to sort results, you will be able to perform your diffs swiftly. my two cents, not adjusted for inflation. On Sat, Aug 15, 2009 at 10:24 AM, Arik Fraimovicharik...@gmail.com wrote: On Aug 15, 10:56 pm, Kevin Mesiab ke...@mesiablabs.com wrote: If you store them as blobs, we're going to revoke your compiler privileges. Good thing that lately I was mainly doing PHP or Python, so no compiler privileges were needed - only parser Any other comments on the question in hand? Thanks, -- Arik Fraimovich follow me on twitter: http://twitter.com/arikfr -- Kevin Mesiab CEO, Mesiab Labs L.L.C. http://twitter.com/kmesiab http://mesiablabs.com http://retweet.com
[twitter-dev] Re: How do you store the social graph locally?
If you store them as blobs, we're going to revoke your compiler privileges. :P On Sat, Aug 15, 2009 at 4:24 AM, Arik Fraimovicharik...@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 -- Kevin Mesiab CEO, Mesiab Labs L.L.C. http://twitter.com/kmesiab http://mesiablabs.com http://retweet.com
[twitter-dev] Seeking Beta Tester Developers for my API
Hi all, I'm looking for a few developers to help me test the API I have built for http://twicli.com (content sharing user tagging) The API's work as you would expect with each content type (photo, video, audio) having an 'upload' and 'uploadAndTweet' method. The backend of the API is actually fine, I just don't have an app to test it with. I have simulated sending requests using PHP but I'm unsure whether the results will be the same when the photo/video data is sent via iPhone or Adobe AIR. Does anyone know what format a photo posted via an app is sent in? Binary data? I don't want to release the API publicly without actually testing it first so any help is appreciated and I'll offer free advertising on both www.picli.com and www.twicli.com I'm also working on various get methods aswell as post. Seemingly most content sharing apps I've seen only seem to offer methods to upload content through their API rather than request data about a specific piece of content. I plan to build a method that will deliver detailed information including users who have been tagged into the photo (for example). Anyway, if anyone's willing to help that would be fantastic and I will return the favour. -Sam http://twitter.com/sampicli
[twitter-dev] Re: Seeking Beta Tester Developers for my API
Hi Sam, (*Speaking strictly as a non-twitter employee and completely as a developer*) I'd like to play with it. I'm working on a new product myself (unrelated to content sharing), so my testing might not be immediate, but this certainly looks interesting. Thanks, -Chad On Sat, Aug 15, 2009 at 5:04 PM, Sam Streetsam...@gmail.com wrote: Hi all, I'm looking for a few developers to help me test the API I have built for http://twicli.com (content sharing user tagging) The API's work as you would expect with each content type (photo, video, audio) having an 'upload' and 'uploadAndTweet' method. The backend of the API is actually fine, I just don't have an app to test it with. I have simulated sending requests using PHP but I'm unsure whether the results will be the same when the photo/video data is sent via iPhone or Adobe AIR. Does anyone know what format a photo posted via an app is sent in? Binary data? I don't want to release the API publicly without actually testing it first so any help is appreciated and I'll offer free advertising on both www.picli.com and www.twicli.com I'm also working on various get methods aswell as post. Seemingly most content sharing apps I've seen only seem to offer methods to upload content through their API rather than request data about a specific piece of content. I plan to build a method that will deliver detailed information including users who have been tagged into the photo (for example). Anyway, if anyone's willing to help that would be fantastic and I will return the favour. -Sam http://twitter.com/sampicli
[twitter-dev] Open Auth
Hi Twitter API Team, We are considering not implementing OAuth in our desktop application. The interaction seems unintuitive and redundant for users who have already granted our application 'trust' by installing it. Are we still to expect basic auth to go away? Is it possible to be granted a source attribute without OAuth implementation? -- Kevin Mesiab CEO, Mesiab Labs L.L.C. http://twitter.com/kmesiab http://mesiablabs.com http://retweet.com
[twitter-dev] Re: Seeking Beta Tester Developers for my API
Dangit, didn't mean to blast the group... sorry for the noise.. -Chad On Sat, Aug 15, 2009 at 5:13 PM, Chad Etzeljazzyc...@gmail.com wrote: Hi Sam, (*Speaking strictly as a non-twitter employee and completely as a developer*) I'd like to play with it. I'm working on a new product myself (unrelated to content sharing), so my testing might not be immediate, but this certainly looks interesting. Thanks, -Chad On Sat, Aug 15, 2009 at 5:04 PM, Sam Streetsam...@gmail.com wrote: Hi all, I'm looking for a few developers to help me test the API I have built for http://twicli.com (content sharing user tagging) The API's work as you would expect with each content type (photo, video, audio) having an 'upload' and 'uploadAndTweet' method. The backend of the API is actually fine, I just don't have an app to test it with. I have simulated sending requests using PHP but I'm unsure whether the results will be the same when the photo/video data is sent via iPhone or Adobe AIR. Does anyone know what format a photo posted via an app is sent in? Binary data? I don't want to release the API publicly without actually testing it first so any help is appreciated and I'll offer free advertising on both www.picli.com and www.twicli.com I'm also working on various get methods aswell as post. Seemingly most content sharing apps I've seen only seem to offer methods to upload content through their API rather than request data about a specific piece of content. I plan to build a method that will deliver detailed information including users who have been tagged into the photo (for example). Anyway, if anyone's willing to help that would be fantastic and I will return the favour. -Sam http://twitter.com/sampicli
[twitter-dev] Authenticating / release of IDs usernames
Hi all, I came across a strange issue today with a few users in my app that still uses basic auth: 1. User signs up to app with username / password 2. App verifies against verify_credentials 3. On success, the returned id is stored. 4. User changes their screen_name, and that screen name is released to be used by others 5. User creates a new account, and uses the old username with same password 6. App continues to authenticate using username / password At thsi point, my app was processing the direct messages feed, and I performed a 'just in case' check on the recipient_id and the stored user_id. That's when some exceptions occurred, where the stored user_id did not match the recipient_id. So I'm wondering - how have people protected against this?
[twitter-dev] Re: Authenticating / release of IDs usernames
I recommend switching to OAuth where verify_credentials seems to be handled in conjunction with the oauth tokens rather than user/pass. Here's how I use it: 1. User authorizes for the first time 2. Twitter user ID, Screen name, password (and various style data) is stored in my 'twitter_users' table From that point on, when the user authorizes in the future each field is compared to the cached values in the database. If any are different.. the twitter_users table is updated with up to date info. It's always best to use twitter user id as an identifier rather than username. I suggest checking to see if id matches your stored ID each time a user logs in. If it's different (username has been reset and used by a new account) create a new row. Hope this helped in any way -Sam @sampicli http://twicli.com On Aug 15, 10:18 pm, stasisme...@googlemail.com stasisme...@googlemail.com wrote: Hi all, I came across a strange issue today with a few users in my app that still uses basic auth: 1. User signs up to app with username / password 2. App verifies against verify_credentials 3. On success, the returned id is stored. 4. User changes their screen_name, and that screen name is released to be used by others 5. User creates a new account, and uses the old username with same password 6. App continues to authenticate using username / password At thsi point, my app was processing the direct messages feed, and I performed a 'just in case' check on the recipient_id and the stored user_id. That's when some exceptions occurred, where the stored user_id did not match the recipient_id. So I'm wondering - how have people protected against this?
[twitter-dev] Re: Seeking Beta Tester Developers for my API
Cool app. I'll help you test it as a user. Just checking it out. Dale On Sat, Aug 15, 2009 at 2:04 PM, Sam Street sam...@gmail.com wrote: Hi all, I'm looking for a few developers to help me test the API I have built for http://twicli.com (content sharing user tagging) The API's work as you would expect with each content type (photo, video, audio) having an 'upload' and 'uploadAndTweet' method. The backend of the API is actually fine, I just don't have an app to test it with. I have simulated sending requests using PHP but I'm unsure whether the results will be the same when the photo/video data is sent via iPhone or Adobe AIR. Does anyone know what format a photo posted via an app is sent in? Binary data? I don't want to release the API publicly without actually testing it first so any help is appreciated and I'll offer free advertising on both www.picli.com and www.twicli.com I'm also working on various get methods aswell as post. Seemingly most content sharing apps I've seen only seem to offer methods to upload content through their API rather than request data about a specific piece of content. I plan to build a method that will deliver detailed information including users who have been tagged into the photo (for example). Anyway, if anyone's willing to help that would be fantastic and I will return the favour. -Sam http://twitter.com/sampicli -- Dale Merritt Fol.la MeDia, LLC
[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 d...@twitter.com 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 seancalla...@gmail.comwrote: 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 sam...@gmail.com wrote: I haven't experienced any downtime or lack of connectivity so far. On Aug 15, 7:16 pm, dougw d...@twitter.com 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 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
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 seancalla...@gmail.com 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 d...@twitter.com 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 seancalla...@gmail.comwrote: 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 sam...@gmail.com wrote: I haven't experienced any downtime or lack of connectivity so far. On Aug 15, 7:16 pm, dougw d...@twitter.com 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 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] Feed page sometimes not actually returning a feed
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] Re: call back issues
Someone please assist. On Aug 15, 3:54 pm, Ritvvij ritvi...@gmail.com wrote: can someone please help?? On Aug 15, 3:19 pm, Ritvvij ritvi...@gmail.com wrote: Hi, development env: ruby on rails oauth: 0.3.5 gem used: twitter_oauth My code to call twitter is client = TwitterOAuth::Client.new( :consumer_key = Attribute::CONSUMER_KEY, :consumer_secret = Attribute::CONSUMER_SECRET) request_token = client.request_token(:oauth_callback = 'http://abc/ authorization/') redirect_to request_token.authorize_url After this, the control goes tohttp://twitter.com/oauth/authorize?oauth_token=k*... Here the user puts his twitter userid password pressed APPROVE and gets redirected tohttp://twitter.com/oauth/authorize instead of my call back URL. Can someone guide why?
[twitter-dev] Re: Open Auth
Looks nice. Seems like a Digg for twitter almost. Look forward to seeing it in action. On Sat, Aug 15, 2009 at 9:18 PM, Kevin Mesiab ke...@mesiablabs.com wrote: Thanks, here's a little sneak preview (attached). On Sat, Aug 15, 2009 at 3:13 PM, Jesse Stayje...@staynalive.com wrote: Considering Twitter's recent move, you guys have a GREAT URL ( retweet.com). Can't wait to see what you guys do with that. Jesse -- Josh
