RE: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
Dewald, it's because you have amateurs running the zoo that are learning as they go. Honestly my opinion is that it's Twitters rights to change the rules as they go - it's their network and their right to do so, but it's also my right as an investor in application development to not invest any more time or money on Twitter until they bring in a management layer that has experience I building ecosystems and knows how to encourage sustainable development. Can you imagine if salesforce pulled a stunt like this? Cheers, Dean -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development- t...@googlegroups.com] On Behalf Of Dewald Pretorius Sent: Monday, 24 May 2010 9:27 PM To: Twitter Development Talk Subject: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING Liz, You are 100% correct in summarizing the problem. Not only were those businesses built with the full knowledge of Twitter, Twitter even had specific rules governing sponsored tweets (had to be clearly marked as sponsored, etc.). I'm really baffled by this decision of Twitter, because I don't understand how they expect to have integrity and trust with developers while doing this type of stuff. Right now we are all being pointed to Annotations as the holy grail of new development. But how do we know that they won't yet again change a rule in the future that will kill businesses that were built on top of Annotations? On May 24, 3:56 pm, Liz nwjersey...@gmail.com wrote: Peter, I think the problem is that business have been created, received funding and developed over the past year, with the full knowledge of Twitter, and this just undercuts destroys them. I think people can understand the rationale (and the desire for Twitter to eliminate competition) but this is a policy decision that should have been made over a year ago. Twitter should have included this in an earlier terms of service instead of giving an implicit okay to services like Sponsored Tweets which has turned into a successful company. It also seems disingenuous that the blog post says that a guiding principle of Twitter is that We don't seek to control what users tweet. And users own their own tweets. and allow adult-oriented content and photos but for some reason, users can't Tweet ads. That sounds like control of content to me. Liz
[twitter-dev] Re: Users Search OAuth
You access it in the same way you access any other resource over oAuth, I use this end point over oAuth all the time. On May 26, 1:20 am, max ihas...@gmail.com wrote: Hi, I was messing around with the users search REST API (http:// apiwiki.twitter.com/Twitter-REST-API-Method:-users-search) and I was curious how the transition towards OAuth-only will change this method call. Can I access this resource with OAuth (and how?)? Or will BASIC Auth be available for this call for a while? Thanks.
[twitter-dev] Twitter Search API stops working intermittently
We have requested for Search API whitelisting to increase the limit to 1QPS but we are still facing issue and search stops working intermittently. We are using the search API to search and stream results. Please let us know what shall we do
[twitter-dev] Posting a link on twitter using Flash
Hi, I have a flash website and a button on it which says Share Link. I would like the user to press that button and post a tweet on his page. How can I do this ? I have been successful in creating a Twitter anywhere application and tested it on my server. It works fine and I have been able to render and use a TweetBox succesfully. But I want to do it via flash. Is there anyway to do this ? If I could call the script with parameters that the Tweet button on TweetBox calls, then I guess I could achieve it. I looked into the twitterscript API for actionscript but it doesn't seem to provide this functionality as of now. Or am i wrong ? Thanks for your help smaira
[twitter-dev] Twitter search API
Hello all, The search API is giving me strange results, for instance http://search.twitter.com/search.atom?q=BBC1+OR+Cash+in+the+Atticresult_type=recent vs http://search.twitter.com/search.atom?q=BBC1result_type=recent Shouldn't all the results from the second URL also be available in first URL? Or am I doing something wrong!
[twitter-dev] Status 401 on Streaming filter API with OAuth
Hi, I am in trouble with OAuth authentication of Streaming filter method with multi tracking words. I tryed status/filter method with track parameters. When I added one key word to track parameter, ex. track=noki, the returned status was 200(Authed). On the other hand, I got status 401 on two key words like track=noki,twitter or track=noki twitter the url encode may cause this problem but my lib. worked fine on REST APIs like status update. Is this my OAuth library bug or Twitter? Here is Auth header example. The tokens used to make sample header is: consumer_token = consumer_token consumer_secret = consumer_secret access_token = access_token access_secret = access_secret METHOD: POST URL: http://stream.twitter.com/1/statuses/filter.json PARAM: track=noki makes oauth_consumer_key=consumer_token, oauth_token=access_token, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274866253, oauth_nonce=69d53e881b216276c58a5368ad8038ea, oauth_version=1.0, oauth_signature=DEwB5M6sA1%2BKq2Xy%2FYx3nttm%2BGg%3D This works fine. but PARAM: track=noki,twitter makes oauth_consumer_key=consumer_token, oauth_token=access_token, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274866475, oauth_nonce=a448e7901d17808677bc46f6a2a180e7, oauth_version=1.0, oauth_signature=tRnND6u0mbQ%2BVLzAeGxQHvM%2FP3M%3D but does not work. Thank you. -- Norio Suzuki
[twitter-dev] Problem with the API Console
Hello everyone, I'm new to the twitter API and found the API Conlose (http:// dev.twitter.com/console) very handy to try requests and understand what you can do with it, but I'm kind of stuck with the impossibility to set up parameters : For example, I try to retrive the last tweets of a particular user I choose GET statuses/user_timeline with json protocol and in the parameters and values fields I set id and radiohead as the user screen name. The result I get is my own timeline. That is the default result when you set no parameters at all and the parameters don't show up in the generated request either. Am I missing something ? A basic search on Google and this website, and the reading of the FAQ didn't show up anything interesting. Does anyone else experience this problem ? Thanks.
Re: [twitter-dev] Problem with the API Console
Hi Daniel, There are still some bugs here and there with the API console that we haven't had a chance to clean up yet. Another alternative you can use to explore the API from a web-based console is the great API console Apigee provides at http://app.apigee.com/console Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, May 26, 2010 at 4:47 AM, Daniel danybo...@gmail.com wrote: Hello everyone, I'm new to the twitter API and found the API Conlose (http:// dev.twitter.com/console) very handy to try requests and understand what you can do with it, but I'm kind of stuck with the impossibility to set up parameters : For example, I try to retrive the last tweets of a particular user I choose GET statuses/user_timeline with json protocol and in the parameters and values fields I set id and radiohead as the user screen name. The result I get is my own timeline. That is the default result when you set no parameters at all and the parameters don't show up in the generated request either. Am I missing something ? A basic search on Google and this website, and the reading of the FAQ didn't show up anything interesting. Does anyone else experience this problem ? Thanks.
Re: [twitter-dev] Re: Twitter OAuth Timestamps
You're not likely to find the requirement explicitly spelled out in the OAuth specification, but Twitter, along with many other OAuth providers, use the timestamp as an additional check point that the request is timely. This is especially important in the token negotiation steps where elements of the request are transitory and shouldn't be held in memory or stored for longer than is necessary. Some providers are even stricter about timestamp variance than we are. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 25, 2010 at 7:36 PM, Eric Woodward e...@nambu.com wrote: Thanks. I did look through the archives before posting but did not find anything. I will look harder next time. I still don't see where in the OAuth specifications it says this comparison is necessary, but I will continue to look around. --ejw Eric Woodward Email: e...@nambu.com On May 25, 5:49 pm, Brian Smith br...@briansmith.org wrote: This is known and expected behavior. There have been other threads about it in the last couple of weeks. If you get a 401 response, you should compare the Date header of Twitter's response to the current system time. If it is significantly off then you should warn the user so they can fix it and/or calculate the difference and add that offset to all your timestamps. More details are available in the mailing list archive. Regards, Brian -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter- development-t...@googlegroups.com] On Behalf Of Eric Woodward Sent: Tuesday, May 25, 2010 7:40 PM To: Twitter Development Talk Subject: [twitter-dev] Twitter OAuth Timestamps I have confirmed a problem with xAuth/OAUth that I believe resides within Twitter OAuth implementation that has been a thorn in our side for a while. I say *believe* because I do not claim to know for sure, thus this post. I assume no one at Twitter will be inclined to do me any favours, but please answer for the sake of the users in general, and other developers in here that do a better job of not publicly expressing their opinions of what Twitter has been doing to its ecosystem. If a user's desktop time is off by a significant margin, say 30m, we have confirmed that a valid username/password via an xAuth request will fail. This has been very painful to track down since those working on Nambu tend to have the desktop time set correctly, and only a handful users complain legitimately, with credibility. This tweet started us on to a solution: http://twitter.com/imhassan/status/14639986090. It is not affecting just Nambu. I cant find anything in the OAuth specs to suggest this comparison to the actual time should take place, so I assume Twitter is just going ahead and comparing the submitted timestamp to the actual time, and rejecting the request (for perhaps a good reason), or it is a bug. We are getting a 401 on a valid request with an inaccurate timestamp. This issue is hinted at here:http://weblog.bluedonkey.org/?p=959. Anyway, we are putting a workaround in place, so if no one at Twitter responds, no worries, Nambu will work going forward. Other developers, be aware that this issue exists. This is very annoying to me because users with inaccurate time settings have tried to verify their accounts in Nambu, failed, and then use the official Twitter application for OSX (aka Tweetie), which works because it is still on HTTP Basic authentication, and declared Nambu to be broken. Twitter, please clarify which part of the process is indeed broken, and what you expect to see regarding timestamps on your end. I assume that by the time Twitter for OSX is updated to use xAuth you will have put a solution in place for this, or will at some point soon afterward as users complain. It would be nice if you outlined that solution for the rest of us when the time comes, so perhaps we can improve on what we have come up with. I apologize in advance if I missed something obvious in the docs somewhere. I am not an expert on OAuth by any means, and have not studied this issue per se. I have only been trying to resolve the issue for us to move on to something more important. Our OAuth implementation works fine otherwise. Well, as well as the rest of the Twitter API works, anyway. Cheers. --ejw Eric Woodward Email: e...@nambu.com
Re: [twitter-dev] Friends and followers
Probably a naming mistake made early on that would have been too much effort to change later on. Clearly though, mutual following indicates Friends more that the unidirectional follow does. In my system, we say following and friends like you suggest. A bit confusing, but I think easier than coming up with a new word for mutual following. You can see it here: http://madison.imby.info/p/Philip.Crawford On Tue, May 25, 2010 at 10:43 PM, Miles Parker milespar...@gmail.com wrote: This question is sort of pedantic, but I'm wondering why the API refers to friends instead of followers. The API say's that friends == following, but I understand (e.g. see this nice little article http://andrewchenblog.com/2009/03/16/friends-versus-followers-twitters-elegant-design-for-grouping-contacts/) that friends are mutual followers, that is: 1. I follow you (following) - 2. You follow me (follower) - 3. We follow each other (friends) - 4. Nada ø So would it be correct to substitute following for friends WRT to API? To keep it straight on my side, I'm going to have to come up with a word that means friends in the sense of 3 above. -- imby - in my back yard An Experiment in Local Professional Networking http://madison.imby.info/p/Philip.Crawford
Re: [twitter-dev] re: intermittent 401 and 502 during oauth process
400 errors usually mean the request was malformed in some way. Can you give some examples of the URLs you are trying to access and the method by which you're requesting? Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 25, 2010 at 11:09 PM, Bhushan Garud garud.bhus...@gmail.com wrote: Hi All, I have got 400 error while accessing users public tweets. Can you please help me to resolve this error? Thanks regards, Bhushan On Wed, May 19, 2010 at 11:29 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Correct. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, May 19, 2010 at 10:18 AM, Dossy Shiobara do...@panoptic.com wrote: Does this result in a response of Failed to validate oauth signature and token as well? On 5/19/10 11:26 AM, Taylor Singletary wrote: Hi James, Yes, right now we're throwing these kind of errors when our servers are stressed. We hope to have things more stable soon. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, May 19, 2010 at 7:48 AM, wibblefish docherty.ja...@gmail.com mailto:docherty.ja...@gmail.com wrote: Hi All, I have just started to put together a small Twitter application but every so often I am seeing either a 401 Unauthorized or 502 Bad Gateway when acquiring a request token. Would it be normal to see this during twitter 'over capacity' periods? Cheers James -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
[twitter-dev] Re: Problem with the API Console
Thanks a lot !
RE: [twitter-dev] Problem with the API Console
Daniel wrote: Hello everyone, For example, I try to retrive the last tweets of a particular user I choose GET statuses/user_timeline with json protocol and in the parameters and values fields I set id and radiohead as the user screen name. The result I get is my own timeline. That is the default result when you set no parameters at all and the parameters don't show up in the generated request either. It seems that the console ignores the parameters, at least if the method is GET. I recommend using twurl instead. Twurl was easier to install than I expected and it seems to work great, even on Windows. Regards, Brian
[twitter-dev] Spam Reduce
Hey, I have noticed a lot of bots on twitter that analyze tweets based on location and the tweet and shoot the user with their campaign tweets.Why cant we analyze the tweets by detecting if the same tweet is tweeted to diff users and then block the user from spamming with 3rd party ads?? Aditya Vikram Thoomati @adivik2000
[twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
The more I think about this situation, the less I like it. At first I was happy that the service I work on was not banned by this ToS change. Even though we use twitter data for monetisation, we don't insert data into timelines. However, when I look at the services that have now been banned, I can't see any warning signs other than that they were competing with Twitter for monetising their data. This is what my service does. Even though it's not currently banned, doesn't it make sense to abandon development now? The best I can hope for it that it *isn't* wildly successful, so Twitter doesn't consider it competition... Every time I read Twitter's explanation for the situation, it reads as we know our monetisation strategy can't compete with third parties in the short term, so we're banning all competition. Hardly conducive to fostering the best solutions, particularly when Twitter will always have the upper hand with their official monetisation platform and analytics for resonance, anyway. What's even worse is the the new ToS is *still* completely ambiguous. Until I saw Peter's post here I had no idea that the ban was only in the publishing end, not insertion. Of course all this makes sense from Twitter's perspective, but for third parties... that just leaves us on an ever changing playing field with invisible goals. I could have lived with rules and rev share additions, but completely banning competition... not so much. Concerned. James PS what's the point of this paragraph from the blog post? We understand that for a few of these companies, the new Terms of Service prohibit activities in which they’ve invested time and money. We will continue to move as quickly as we can to deliver the Annotations capability to the market so that developers everywhere can create innovative new business solutions on the growing Twitter platform. a slap in the face? We understand that we've wasted your time and money, so here's the next thing for you to waste time and money on. No guarantees, no apologies. On May 26, 6:07 pm, Dean Collins d...@cognation.net wrote: Dewald, it's because you have amateurs running the zoo that are learning as they go. Honestly my opinion is that it's Twitters rights to change the rules as they go - it's their network and their right to do so, but it's also my right as an investor in application development to not invest any more time or money on Twitter until they bring in a management layer that has experience I building ecosystems and knows how to encourage sustainable development. Can you imagine if salesforce pulled a stunt like this? Cheers, Dean -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development- t...@googlegroups.com] On Behalf Of Dewald Pretorius Sent: Monday, 24 May 2010 9:27 PM To: Twitter Development Talk Subject: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING Liz, You are 100% correct in summarizing the problem. Not only were those businesses built with the full knowledge of Twitter, Twitter even had specific rules governing sponsored tweets (had to be clearly marked as sponsored, etc.). I'm really baffled by this decision of Twitter, because I don't understand how they expect to have integrity and trust with developers while doing this type of stuff. Right now we are all being pointed to Annotations as the holy grail of new development. But how do we know that they won't yet again change a rule in the future that will kill businesses that were built on top of Annotations? On May 24, 3:56 pm, Liz nwjersey...@gmail.com wrote: Peter, I think the problem is that business have been created, received funding and developed over the past year, with the full knowledge of Twitter, and this just undercuts destroys them. I think people can understand the rationale (and the desire for Twitter to eliminate competition) but this is a policy decision that should have been made over a year ago. Twitter should have included this in an earlier terms of service instead of giving an implicit okay to services like Sponsored Tweets which has turned into a successful company. It also seems disingenuous that the blog post says that a guiding principle of Twitter is that We don't seek to control what users tweet. And users own their own tweets. and allow adult-oriented content and photos but for some reason, users can't Tweet ads. That sounds like control of content to me. Liz
Re: [twitter-dev] Twitter search API
The first one should likely be BBC1 OR Cash in the Attic which translates to (BBC1) OR (Cash AND in AND the AND Attic) instead of BBC1 OR Cash in the Attic which translates to (BBC1) OR (CASH) AND (in) AND (the) AND (Attic) Jonathan On Wed, May 26, 2010 at 1:43 AM, Nick nvan...@gmail.com wrote: Hello all, The search API is giving me strange results, for instance http://search.twitter.com/search.atom?q=BBC1+OR+Cash+in+the+Atticresult_type=recent vs http://search.twitter.com/search.atom?q=BBC1result_type=recent Shouldn't all the results from the second URL also be available in first URL? Or am I doing something wrong!
[twitter-dev] Re: statuses/update 403 error
Agreed. If the API is going to overload an error code, Twitter needs to enumerate the error details and provide those details in a consistent machine readable form. On May 25, 1:52 am, akaii chibiak...@gmail.com wrote: There seem to be a variety of possible causes for getting an 403 error in responses to a calling statuses/update... you could be duplicating a tweet or hitting the update limit for an hour or for the day. How can you tell which one these errors actually occurred? The only 2 ways I can think of is to try and parse the error message, or to follow up the request with a query about whether you've hit any limits. The problem with checking the error message is that: 1) It's fragile. If the twitter dev team decides to change the error msg, the solution breaks. 2) I'd have to know the error message first... and the specific error messages for hitting the update limit don't seem to be documented anywhere that I can see. Not in the wiki for sure. Which means that I'd have to hit the limit to find out directly what the messages are... not exactly practical, especially for the 1000 per day limit. It would take me a minimum of 7 hours to hit that limit, since I'd get capped by the hourly limit first. The problem with a follow-up request is that: I can't seem to find a way to get current remaining tweets available to the user before hitting the status update limit in the api. There's one for rate limiting: account/rate_limit_status But where's the corresponding api for the status update limits? What should I do about this? Is there some third, better way to find out which specific error resulted from the update attempt?
[twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
I hope some answers are forthcoming, James. Twitter doesn't seem very talkative.
Re: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
Hello Everyone, We recently updated our Advertising FAQ to answer many of the questions that you may have. http://bit.ly/twitter-ad-faq Taylor On Wed, May 26, 2010 at 9:15 AM, Liz nwjersey...@gmail.com wrote: I hope some answers are forthcoming, James. Twitter doesn't seem very talkative.
[twitter-dev] Re: Follower count over time
Peter, I appreciate the suggestion, but am looking to provide the functionality naively in our client as we may end up competing with their service. What I need is what gives them the ability to provide that data (if they do). We are all using the same Twitter API, but I can't figure out a way to do it. Thanks! Ryan On May 21, 3:18 pm, Peter Denton petermden...@gmail.com wrote: Ryan, you might want to check out twittercounter and their api. They have some cool data around follower growth. On Fri, May 21, 2010 at 11:51 AM, Ryan Bell ryan.j.b...@gmail.com wrote: Hi, How do I get # of followers over time? I've seen several sites that list a graph that shows your follower count over time. ex) 4/1/10 you had 200 followes...5/1/2010 you had 247 followersand so on. I would love to add this feature to my Twitter site, but can't find the data that I would need in order to do it. Does the API provide information on any of the following? 1. # of followers at a particular time? 2. Time in which a follower began following you? If the API doesn't provide this info, then how are other sites doing this? I doubt its from checking daily as the moment you sign up with a site that has this feature, they have your follower graph over time for at least 12 months of history. Thanks in advance!!! Ryan
[twitter-dev] Post from C#
I am a new to programming, what I want to do is post a comment to my twitter page using C#. Something simple amd direct, I have started my C# app with the Twitterizer api. Is this api a good place to start? I just want to contact my Twitter page and post a message. Thanks AL.
[twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
Taylor, Read this part of that FAQ: Paid Tweets injected into any timeline on a service that leverages the Twitter API (other than Promoted Tweets). This applies to any Twitter stream, whether user based, search based, or other. Do you realize how confusing that is? 1) Does it mean I can publish a paid tweet via the API? (I know I can, but someone who just reads the FAQ won't be able to figure that out.) 2) Does it mean I can inject tweets into any displayed timeline, as long as they are not paid tweets? If so, it means I can insert entries that look exactly like tweets, except they did not come from Twitter and they contain my affiliate link. You guys really need to sit down and read all these things through the eyes of people who are not privy to your internal discussions, decisions, and understanding of the matter. And then write your TOS and FAQs so that everyone can understand them. On May 26, 1:20 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hello Everyone, We recently updated our Advertising FAQ to answer many of the questions that you may have.http://bit.ly/twitter-ad-faq Taylor On Wed, May 26, 2010 at 9:15 AM, Liz nwjersey...@gmail.com wrote: I hope some answers are forthcoming, James. Twitter doesn't seem very talkative.
[twitter-dev] Re: duplicate tweet behavior has changed within the last few days
We're always working to improve our duplicate tweet detection routines, and as such there's no hard equation you can follow for issuing duplicate tweets reliably. I'm a big advocate for expressing these kind of limits in a way you can interpret programatically but in this case the target is moving. By indicating the time window when a duplicate of the recently submitted tweet could be resubmitted, we would be opening an abuse vector. Including something unique in the string might be your best bet to get around this. On May 22, 11:19 pm, Mr Blog mrblogdot...@gmail.com wrote: My GaragebBot tweets when doors are opened or closed:http://twitter.com/connectedthings The tweets are of the form: tweet 1: Door 2 opened tweet 2: Door 2 closed manually tweet 3: Door 1 opened tweet 4: Door 2 opened tweet 5: Door 2 closed automatically tweet 6: Door 1 closed manually The behavior up until a few days ago was duplicates were defined as tweet N+1 being identical to the prior tweet N, but now there appears to be some kind of cache where tweet 4 above fails with a 403 duplicate tweet error even though it is not a duplicate of the most recent tweet (but is the same message as tweet 1, but a different in time, so thus meaningful). In this case, the garage only tweets about 6 different messages and it has been doing so for several years, with great success, but now almost all tweets are being rejected as duplicates. I could change it to put some random garbage at the end of each new tweet, but that doesn't seem very elegant.
Re: [twitter-dev] Encrypted data over Twitter
Just curious. Which laws would be violated?
Re: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
If you have specific questions about the policy, we have an email address you can send them to: twitter_...@twitter.com I unfortunately don't have answers for you beyond what's presented in the FAQ and the Terms of Service. Taylor On Wed, May 26, 2010 at 9:35 AM, Dewald Pretorius dpr...@gmail.com wrote: Taylor, Read this part of that FAQ: Paid Tweets injected into any timeline on a service that leverages the Twitter API (other than Promoted Tweets). This applies to any Twitter stream, whether user based, search based, or other. Do you realize how confusing that is? 1) Does it mean I can publish a paid tweet via the API? (I know I can, but someone who just reads the FAQ won't be able to figure that out.) 2) Does it mean I can inject tweets into any displayed timeline, as long as they are not paid tweets? If so, it means I can insert entries that look exactly like tweets, except they did not come from Twitter and they contain my affiliate link. You guys really need to sit down and read all these things through the eyes of people who are not privy to your internal discussions, decisions, and understanding of the matter. And then write your TOS and FAQs so that everyone can understand them. On May 26, 1:20 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hello Everyone, We recently updated our Advertising FAQ to answer many of the questions that you may have.http://bit.ly/twitter-ad-faq Taylor On Wed, May 26, 2010 at 9:15 AM, Liz nwjersey...@gmail.com wrote: I hope some answers are forthcoming, James. Twitter doesn't seem very talkative.
Re: [twitter-dev] Encrypted data over Twitter
Quoting bujanga buja...@gmail.com: Just curious. Which laws would be violated? There are numerous US laws governing encryption technologies. I'm not familiar with them in detail but mostly they attempt to restrict access to the technologies to just our closest allies.
Re: [twitter-dev] Encrypted data over Twitter
I think you're referring to ITAR, most of which was repealed in 1997. Until 1996–1997, ITAR classified strong cryptography as arms and prohibited their export from the U.S. Times have changed quite a bit since then. I don't speak for our terms of service group, and this is by no means an official statement, but I do think that passing encrypted traffic in public tweets would be fairly antisocial and against the spirit of the service. -john On Wed, May 26, 2010 at 10:09 AM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Quoting bujanga buja...@gmail.com: Just curious. Which laws would be violated? There are numerous US laws governing encryption technologies. I'm not familiar with them in detail but mostly they attempt to restrict access to the technologies to just our closest allies.
[twitter-dev] geo enabled tweets in the twitter stream
Hi, I am using the twitter stream api to access the sample of public tweets. For each tweet I need to know the latitude and longitude location from where the tweet was sent. I am looking up that information in the geo tag/field. But I observed that even if the geo_enabled field is set to true, the geo field is set to null for many tweets. Will appreciate if you can help me understand why this is the case. Also will appreciate if you can help me figure out if there is a better way to find the latitude and longitude location from where the tweet was sent by the user. thanks and I greatly appreciate your help with this! gm
Re: [twitter-dev] geo enabled tweets in the twitter stream
Most users don't geotag their tweets. If they don't opt-in, the information isn't available. -John On Wed, May 26, 2010 at 10:34 AM, gm gmans...@gmail.com wrote: Hi, I am using the twitter stream api to access the sample of public tweets. For each tweet I need to know the latitude and longitude location from where the tweet was sent. I am looking up that information in the geo tag/field. But I observed that even if the geo_enabled field is set to true, the geo field is set to null for many tweets. Will appreciate if you can help me understand why this is the case. Also will appreciate if you can help me figure out if there is a better way to find the latitude and longitude location from where the tweet was sent by the user. thanks and I greatly appreciate your help with this! gm
[twitter-dev] Re: New social events on User Streams
I had to remove unfollow messages until we can sort out a complicated issue. The block and unblock messages remain. Sorry for the regression -- we're trying to move quickly. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Mon, May 24, 2010 at 9:41 PM, John Kalucki j...@twitter.com wrote: User Streams now delivers unfollowing, block and unblock events from (created by) the signed-in user. This allows an application to update its state when the user makes a change on another client instance. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc.
[twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
Sponsored Tweets at least announced that the content was advertising. I think this language will just lead to advertising without proper disclosure by the user (which was used in keeping with the FTC ruling on this issue). Some celebs bloggers will still accept money Tweet about products, just without indicating publicly that they've been paid. Also, you say We don't seek to control what users Tweet but that's exactly what you are doing by preventing users from Tweeting advertisement should they wish to. I know you can set whatever rules you like regardless of how they affect people or developers but don't make a ban on using Tweets for certain kinds of content and then say that you're not trying to control the content. Clearly, that is what you're doing. That's what a ban is, exerting your control over content. In my opinion, you've picked the wrong target. I'm also not sure how paid Tweets by individual users is any different from commercial/organization accounts using Twitter to offer discounts, specials, sales, etc. Why does the advertising ban apply to individuals and not to companies? Liz Pullen
Re: [twitter-dev] Re: Twitter OAuth Timestamps
http://tools.ietf.org/html/draft-hammer-oauth-10#section-3.3 On Wed, May 26, 2010 at 05:55, Taylor Singletary taylorsinglet...@twitter.com wrote: You're not likely to find the requirement explicitly spelled out in the OAuth specification, but Twitter, along with many other OAuth providers, use the timestamp as an additional check point that the request is timely. This is especially important in the token negotiation steps where elements of the request are transitory and shouldn't be held in memory or stored for longer than is necessary. Some providers are even stricter about timestamp variance than we are. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 25, 2010 at 7:36 PM, Eric Woodward e...@nambu.com wrote: Thanks. I did look through the archives before posting but did not find anything. I will look harder next time. I still don't see where in the OAuth specifications it says this comparison is necessary, but I will continue to look around. --ejw Eric Woodward Email: e...@nambu.com On May 25, 5:49 pm, Brian Smith br...@briansmith.org wrote: This is known and expected behavior. There have been other threads about it in the last couple of weeks. If you get a 401 response, you should compare the Date header of Twitter's response to the current system time. If it is significantly off then you should warn the user so they can fix it and/or calculate the difference and add that offset to all your timestamps. More details are available in the mailing list archive. Regards, Brian -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter- development-t...@googlegroups.com] On Behalf Of Eric Woodward Sent: Tuesday, May 25, 2010 7:40 PM To: Twitter Development Talk Subject: [twitter-dev] Twitter OAuth Timestamps I have confirmed a problem with xAuth/OAUth that I believe resides within Twitter OAuth implementation that has been a thorn in our side for a while. I say *believe* because I do not claim to know for sure, thus this post. I assume no one at Twitter will be inclined to do me any favours, but please answer for the sake of the users in general, and other developers in here that do a better job of not publicly expressing their opinions of what Twitter has been doing to its ecosystem. If a user's desktop time is off by a significant margin, say 30m, we have confirmed that a valid username/password via an xAuth request will fail. This has been very painful to track down since those working on Nambu tend to have the desktop time set correctly, and only a handful users complain legitimately, with credibility. This tweet started us on to a solution: http://twitter.com/imhassan/status/14639986090. It is not affecting just Nambu. I cant find anything in the OAuth specs to suggest this comparison to the actual time should take place, so I assume Twitter is just going ahead and comparing the submitted timestamp to the actual time, and rejecting the request (for perhaps a good reason), or it is a bug. We are getting a 401 on a valid request with an inaccurate timestamp. This issue is hinted at here:http://weblog.bluedonkey.org/?p=959. Anyway, we are putting a workaround in place, so if no one at Twitter responds, no worries, Nambu will work going forward. Other developers, be aware that this issue exists. This is very annoying to me because users with inaccurate time settings have tried to verify their accounts in Nambu, failed, and then use the official Twitter application for OSX (aka Tweetie), which works because it is still on HTTP Basic authentication, and declared Nambu to be broken. Twitter, please clarify which part of the process is indeed broken, and what you expect to see regarding timestamps on your end. I assume that by the time Twitter for OSX is updated to use xAuth you will have put a solution in place for this, or will at some point soon afterward as users complain. It would be nice if you outlined that solution for the rest of us when the time comes, so perhaps we can improve on what we have come up with. I apologize in advance if I missed something obvious in the docs somewhere. I am not an expert on OAuth by any means, and have not studied this issue per se. I have only been trying to resolve the issue for us to move on to something more important. Our OAuth implementation works fine otherwise. Well, as well as the rest of the Twitter API works, anyway. Cheers. --ejw Eric Woodward Email: e...@nambu.com -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Post from C#
Thanks for the link. I also found this page: http://apiwiki.twitter.com/OAuth-Examples AL. On May 26, 9:29 am, Al aa1...@gmail.com wrote: I am a new to programming, what I want to do is post a comment to my twitter page using C#. Something simple amd direct, I have started my C# app with the Twitterizer api. Is this api a good place to start? I just want to contact my Twitter page and post a message. Thanks AL.
[twitter-dev] Re: Post from C#
Thanks for the link. AL. On May 26, 10:26 am, Andrew Badera and...@badera.us wrote: http://www.twitterizer.net/wiki/Main_Page Also, GIYF. http://www.twitterizer.net/wiki/Main_Page ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Wed, May 26, 2010 at 12:29 PM, Al aa1...@gmail.com wrote: I am a new to programming, what I want to do is post a comment to my twitter page using C#. Something simple amd direct, I have started my C# app with the Twitterizer api. Is this api a good place to start? I just want to contact my Twitter page and post a message. Thanks AL.
Re: [twitter-dev] Re: Post from C#
Cool. Just keep in mind a lot of the .NET OAuth stuff, especially on the Twitter side, is somewhat out of date or incomplete. --ab On Wed, May 26, 2010 at 2:51 PM, Al aa1...@gmail.com wrote: Thanks for the link. I also found this page: http://apiwiki.twitter.com/OAuth-Examples AL. On May 26, 9:29 am, Al aa1...@gmail.com wrote: I am a new to programming, what I want to do is post a comment to my twitter page using C#. Something simple amd direct, I have started my C# app with the Twitterizer api. Is this api a good place to start? I just want to contact my Twitter page and post a message. Thanks AL.
[twitter-dev] Annotations Hackfest
Hey everyone, This week the Twitter Engineering team announced they are running an annotation Hackfest. The event will be this weekend (29-30 May) at Twitter HQ (795 Folsom St. San Francisco) and is free to attend. Places are limited so if you want to attend sign up today! If you are in the Bay Area this is a great opportunity to hack with Annotations and meet other Twitter developers. I'll be around for the event so if you want to share ideas and experiences with using the APIs, or just want to have a chat, come and say hi. More details and the signup form are on the Engineering team blog: http://engineering.twitter.com/2010/05/annotations-hackfest.html Best, Matt
Re: [twitter-dev] Re: No oauth_verifier in custom URI (Desktop)
Hi Jeena, You should now be able to dynamically declare custom URI schemes in your oauth_callback on the request_token step and it will properly redirect. Let me know if you run into any issues! Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 8:50 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Jeena, We have a fix queued for deploy sometime in the next week or so. I'll let you know when it's available. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Sun, May 16, 2010 at 2:47 AM, Jeena jeenaparad...@gmail.com wrote: Something new on this topic? /Jeena
Re: [twitter-dev] TwitterOAuth, two authentication calls, one works, one fails... why?
Are the scripts on the same server? Same version of PHP? Are they using the same accounts access tokens? Same consumer token? Abraham On Sun, May 23, 2010 at 18:07, Jonathan jhsa...@jhsachs.com wrote: I've been trying to get my application to work with TwitterOAuth for several weeks now. Here’s a brief history: I need to authorize user requests of three different types. For that purpose I’ve got two scripts (I’ll call them #1 and #2), and #2 is invoked in two places. Several weeks ago I got script #1 to work with an old version of TwitterOAuth, which did not support specifying a callback URL for each call. I then tried to migrate to a newer version (beta-0.2.0), which would support specifying a callback URL, and script #1 ceased to work. Everything seemed OK up to the point where I tested the access token by performing a verify_credentials operation; then I got back an error that said “could not authenticate you.” I had no luck identifying the problem, so today I fell back to the old version of TwitterOAuth. Now script #1 works again, but script #2 does not. It returns the same error, “could not authenticate you.” I've inserted echo statements in both scripts to show the parameters and result of every call to TwitterOAuth. The sequences of calls are identical, and as far as I can tell the parameters and results are identical in every respect that they should be. Yet one call succeeds and the other fails. I've been beating may head against this thing for weeks, and I'm stumped. I'm open to any sort of advice on what the problem might be, or how to identify it, or how to work around it without identifying it. -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
RE: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
Taylor - any reason why you aren't posting the direct url for the twitter page? Seem suspect you don't want to be nailed down in a google cache on the specifics? Regards, Dean Collins Cognation Inc d...@cognation.net +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development- t...@googlegroups.com] On Behalf Of Taylor Singletary Sent: Wednesday, 26 May 2010 6:21 PM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING Hello Everyone, We recently updated our Advertising FAQ to answer many of the questions that you may have. http://bit.ly/twitter-ad-faq Taylor On Wed, May 26, 2010 at 9:15 AM, Liz nwjersey...@gmail.com wrote: I hope some answers are forthcoming, James. Twitter doesn't seem very talkative.
[twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
Taylor, Perhaps you should ask someone to add the http://bit.ly/twitter-ad-faq link as a further reading reference into the 2. Advertising Around Twitter Content section of the API TOS. Stuff is very fragmented at the moment, and you have to accidentally discover pages on separate domains just to get the full picture. The same goes for further reading on other sections of the API TOS as well. On May 26, 1:20 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hello Everyone, We recently updated our Advertising FAQ to answer many of the questions that you may have.http://bit.ly/twitter-ad-faq Taylor On Wed, May 26, 2010 at 9:15 AM, Liz nwjersey...@gmail.com wrote: I hope some answers are forthcoming, James. Twitter doesn't seem very talkative.
Re: [twitter-dev] Annotations Hackfest
Quoting themattharris thematthar...@twitter.com: Hey everyone, This week the Twitter Engineering team announced they are running an annotation Hackfest. The event will be this weekend (29-30 May) at Twitter HQ (795 Folsom St. San Francisco) and is free to attend. Places are limited so if you want to attend sign up today! If you are in the Bay Area this is a great opportunity to hack with Annotations and meet other Twitter developers. I'll be around for the event so if you want to share ideas and experiences with using the APIs, or just want to have a chat, come and say hi. More details and the signup form are on the Engineering team blog: http://engineering.twitter.com/2010/05/annotations-hackfest.html Best, Matt When will the annotations previews be open for hacking to the general developer community? Not all of us can afford to drop everything we're working on and come to a hackathon.
Re: [twitter-dev] Re: TWITTER BANS 3rd PARTY ADVERTISING
Dewald: I'll make that recommendation; I agree that relevant information should be grouped together as much as possible. Dean: The link to the support center FAQ on this topic is very clumsy and long; there are still a number of email clients out there that don't handle long links very well, besides the convenience of having a single URL that I can memorize easily when pointing it out to folks. For those concerned about URL shortening, you can access that FAQ at http://support.twitter.com/groups/35-business/topics/127-frequently-asked-questions/articles/142161-advertisers#20100525 Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, May 26, 2010 at 1:23 PM, Dewald Pretorius dpr...@gmail.com wrote: Taylor, Perhaps you should ask someone to add the http://bit.ly/twitter-ad-faq link as a further reading reference into the 2. Advertising Around Twitter Content section of the API TOS. Stuff is very fragmented at the moment, and you have to accidentally discover pages on separate domains just to get the full picture. The same goes for further reading on other sections of the API TOS as well. On May 26, 1:20 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hello Everyone, We recently updated our Advertising FAQ to answer many of the questions that you may have.http://bit.ly/twitter-ad-faq Taylor On Wed, May 26, 2010 at 9:15 AM, Liz nwjersey...@gmail.com wrote: I hope some answers are forthcoming, James. Twitter doesn't seem very talkative.
[twitter-dev] Re: duplicate tweet behavior has changed within the last few days
Thanks for the response, Taylor. I do appreciate it. There is some irony in the fact that I have to inject some superfluous drivel into a perfectly legitimate non-duplicate tweet to appease the Twitter spam filters - more collateral damage hitting innocent, legitimate users - very indicative of the state of the Twitterverse. Thanks again. On May 26, 9:39 am, Taylor Singletary taylorsinglet...@twitter.com wrote: We're always working to improve our duplicate tweet detection routines, and as such there's no hard equation you can follow for issuing duplicate tweets reliably. I'm a big advocate for expressing these kind of limits in a way you can interpret programatically but in this case the target is moving. By indicating the time window when a duplicate of the recently submitted tweet could be resubmitted, we would be opening an abuse vector. Including something unique in the string might be your best bet to get around this. On May 22, 11:19 pm, Mr Blog mrblogdot...@gmail.com wrote: My GaragebBot tweets when doors are opened or closed:http://twitter.com/connectedthings The tweets are of the form: tweet 1: Door 2 opened tweet 2: Door 2 closed manually tweet 3: Door 1 opened tweet 4: Door 2 opened tweet 5: Door 2 closed automatically tweet 6: Door 1 closed manually The behavior up until a few days ago was duplicates were defined as tweet N+1 being identical to the prior tweet N, but now there appears to be some kind of cache where tweet 4 above fails with a 403 duplicate tweet error even though it is not a duplicate of the most recent tweet (but is the same message as tweet 1, but a different in time, so thus meaningful). In this case, the garage only tweets about 6 different messages and it has been doing so for several years, with great success, but now almost all tweets are being rejected as duplicates. I could change it to put some random garbage at the end of each new tweet, but that doesn't seem very elegant.
[twitter-dev] Search api returning results based on walking shortened URLS: causing problems.
So we have customer that is searching, for example, for hotels.com. So we use the search api and we get from Twitter a tweet that has no such text in it, but it turns out that the shortened URL contains the string 'hotels.com': Here's the tweet: Siam Bayview Hotel Pattaya, Beach Rd. from THB 2,010 incl breakfast Special Rate http://bit.ly/295HOI Thailand hotels He're the walked bit.ly url: http://www.r24.org/patong-beach-hotels.com/pattaya/siambayview/ In this case, this match isn't good. They don't want r24.org stuff, they want hotels.com stuff... On the other hand, it's great when it really shows hotels.com stuff.. I'm not sure what the 'right thing to do is at this moment, as I'm reacting to the customer's urgency and problem in getting unrelated stuff showing up in their search... I'm not sure how I should address this: 1. recommend that twitter do some sort of mod to the search api ( I don't have a good idea at the moment about what you should do: make such url walking optional? etc?) 2. do some sort of processing on our end, and communicating about better about what search does to our customers So: a. What's ya'll thoughts on this one? b. I believe that you (twitter) walk some shorteners but not all of them: e.g. bit.ly urls and your own shortener What is the current list that you do walk? This is related to entity parsing discussion here: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/9b869a9fe4d4252e/861a2aa59b563f33?lnk=gstq=search+url#861a2aa59b563f33 Thanks, Jeffrey Greenberg tweettronics.com
[twitter-dev] Re: Search api returning results based on walking shortened URLS: causing problems.
I've seen the same thing with some of my own searches, and I just figured the search algo was broken, because it returns results that have absolutely nothing to do with the phrase you searched for. On May 26, 6:24 pm, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: So we have customer that is searching, for example, for hotels.com. So we use the search api and we get from Twitter a tweet that has no such text in it, but it turns out that the shortened URL contains the string 'hotels.com': Here's the tweet: Siam Bayview Hotel Pattaya, Beach Rd. from THB 2,010 incl breakfast Special Ratehttp://bit.ly/295HOIThailand hotels He're the walked bit.ly url: http://www.r24.org/patong-beach-hotels.com/pattaya/siambayview/ In this case, this match isn't good. They don't want r24.org stuff, they want hotels.com stuff... On the other hand, it's great when it really shows hotels.com stuff.. I'm not sure what the 'right thing to do is at this moment, as I'm reacting to the customer's urgency and problem in getting unrelated stuff showing up in their search... I'm not sure how I should address this: 1. recommend that twitter do some sort of mod to the search api ( I don't have a good idea at the moment about what you should do: make such url walking optional? etc?) 2. do some sort of processing on our end, and communicating about better about what search does to our customers So: a. What's ya'll thoughts on this one? b. I believe that you (twitter) walk some shorteners but not all of them: e.g. bit.ly urls and your own shortener What is the current list that you do walk? This is related to entity parsing discussion here:http://groups.google.com/group/twitter-development-talk/browse_thread... Thanks, Jeffrey Greenberg tweettronics.com
[twitter-dev] New opt-in API features available today, May 26th: entities, retweets in timelines, custom oauth_callback schemes
Hi Developers, We released some new features today that I'll summarize briefly here. *Entities* Raffi's already introduced the concept of entities to you in a previous post: http://bit.ly/boHXYv You can now retrieve entities for tweets by specifying a include_entities=true parameter to statuses/home_timeline, statuses/user_timeline, statuses/friends_timeline, and statuses/mentions API calls to receive additional per-tweet payloads dissecting parse-able elements from the tweet body like @mentions, links, and hashtags. It's really cool! Some examples of how entities are represented can be found here: http://dev.twitter.com/pages/tweet_entities *Retweets in Timelines* * *Many developers have asked for merged timelines including native retweets; for backwards-compatibility reasons this hasn't been possible in the past. Now you can include a include_rts=true parameter to statuses/user_timeline, statuses/friends_timeline, and statuses/mentions API calls to receive retweets inline in the payload. *OAuth callbacks with non-standard URI schemes* While you still can't set your default oauth_callback in your client application record to a URI schemes that aren't of the http or https variety, you can now dynamically set your oauth_callback on the request_token step of the OAuth dance to custom URI schemes. This is useful when your application is a web browser itself, or has the capability of registering custom URI schemes on the host operating system; a great, almost friction-free solution for those weary of the out-of-band OAuth flow. Since these features are new, we would appreciate any comments, suggestions, or notes on any bugs you discover while using them. Some relevant updated documentation: http://dev.twitter.com/doc/get/statuses/mentions http://dev.twitter.com/doc/get/statuses/friends_timeline http://dev.twitter.com/doc/get/statuses/home_timeline http://dev.twitter.com/doc/get/statuses/public_timeline Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
[twitter-dev] Re: Annotations Hackfest
Great question. We're really excited to see what developers do with annotations during the hackfest. In some ways the hackfest can be thought of as an early test of annotations and will let us know what we have left to do before we release them to the developer community. The plan, if things go well at the hackfest, is to have a general developer release this summer.
RE: [twitter-dev] New opt-in API features available today, May 26th: entities, retweets in timelines, custom oauth_callback schemes
How are characters indexed in the indices values of entities? My guess would be that they are indexed as Unicode code points--not bytes—and that the indexes refer to the text before entity expansion (“amp;” - “”) is done. Is that correct? Like I mentioned in the previous thread, it would be very useful if we could use the entities construct when posting. First, it would help to mitigate problems when replying to somebody that has changed their username since the tweet you are replying to. Also, it would allow an application to clarify what is exactly in a URL. For example, “Check out http://example.org/foo.” should have the URL parsed without the trailing period, but currently Twitter considers the period to be part of the URL. From other observations it seems like Twitter has already built a short-link expansion service that is used internally. Will expanded links be exposed via this entities mechanism anytime soon? Regards, Brian From: Taylor Singletary Entities Raffi's already introduced the concept of entities to you in a previous post: http://bit.ly/boHXYv You can now retrieve entities for tweets by specifying a include_entities=true parameter to statuses/home_timeline, statuses/user_timeline, statuses/friends_timeline, and statuses/mentions API calls to receive additional per-tweet payloads dissecting parse-able elements from the tweet body like @mentions, links, and hashtags. It's really cool! Some examples of how entities are represented can be found here: http://dev.twitter.com/pages/tweet_entities
Re: [twitter-dev] Re: Annotations Hackfest
I realize it may not be logistically possible just yet, but you may also want to throw some consideration for an additional hackfest for those closer to the east coast. (Eg-NYC) Sent from my Verizon Wireless BlackBerry -Original Message- From: themattharris thematthar...@twitter.com Date: Wed, 26 May 2010 15:30:07 To: Twitter Development Talktwitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: Annotations Hackfest Great question. We're really excited to see what developers do with annotations during the hackfest. In some ways the hackfest can be thought of as an early test of annotations and will let us know what we have left to do before we release them to the developer community. The plan, if things go well at the hackfest, is to have a general developer release this summer.
Re: [twitter-dev] Re: Annotations Hackfest
Quoting BJ Weschke bwesc...@btwtech.com: I realize it may not be logistically possible just yet, but you may also want to throw some consideration for an additional hackfest for those closer to the east coast. (Eg-NYC) This is 2010, right? There's this thing called the Internet, right? IRC still works, right? Why the Hell can't Twitter have hackathons over the Internet, the same way all the open source projects do? For cryin' out loud! Linux, PostgreSQL, Perl, Python, Ruby ... you name it ... *every* major open source hacker-built piece of software is put together around the world over the Internet, with major contributors in most nations. Why should annotations be developed and tested only in San Francisco or New York? Sent from my Verizon Wireless BlackBerry -Original Message- From: themattharris thematthar...@twitter.com Date: Wed, 26 May 2010 15:30:07 To: Twitter Development Talktwitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: Annotations Hackfest Great question. We're really excited to see what developers do with annotations during the hackfest. In some ways the hackfest can be thought of as an early test of annotations and will let us know what we have left to do before we release them to the developer community. The plan, if things go well at the hackfest, is to have a general developer release this summer.
[twitter-dev] Re: Follower count over time
Use the spritzer to sample tweets, but you only need to sample follower_count data per user over time. On May 26, 9:33 am, Ryan Bell ryan.j.b...@gmail.com wrote: Peter, I appreciate the suggestion, but am looking to provide the functionality naively in our client as we may end up competing with their service. What I need is what gives them the ability to provide that data (if they do). We are all using the same Twitter API, but I can't figure out a way to do it. Thanks! Ryan On May 21, 3:18 pm, Peter Denton petermden...@gmail.com wrote: Ryan, you might want to check out twittercounter and their api. They have some cool data around follower growth. On Fri, May 21, 2010 at 11:51 AM, Ryan Bell ryan.j.b...@gmail.com wrote: Hi, How do I get # of followers over time? I've seen several sites that list a graph that shows your follower count over time. ex) 4/1/10 you had 200 followes...5/1/2010 you had 247 followersand so on. I would love to add this feature to my Twitter site, but can't find the data that I would need in order to do it. Does the API provide information on any of the following? 1. # of followers at a particular time? 2. Time in which a follower began following you? If the API doesn't provide this info, then how are other sites doing this? I doubt its from checking daily as the moment you sign up with a site that has this feature, they have your follower graph over time for at least 12 months of history. Thanks in advance!!! Ryan
Re: [twitter-dev] Re: Annotations Hackfest
On Wed, May 26, 2010 at 4:05 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: This is 2010, right? There's this thing called the Internet, right? IRC still works, right? Yes but IRC works too well.
Re: [twitter-dev] Re: New social events on User Streams
John, Any chance it moves so quickly than time is left to look at the issue I've posted? Subject was 'UserStream : bug with oauth connection' On Wed, May 26, 2010 at 11:08 AM, John Kalucki j...@twitter.com wrote: I had to remove unfollow messages until we can sort out a complicated issue. The block and unblock messages remain. Sorry for the regression -- we're trying to move quickly.
[twitter-dev] Bulk Conversion using xAuth
Hi All, Is there any PHP script which I can take a look at to migrate users from basic auth to oauth? I've received temporary xAuth access and want to get it done within the less than 7 days (can this be extended) window granted. Thanks! Best, Y
[twitter-dev] Re: Bulk Conversion using xAuth
Ah. It looks like Abraham's twitteroauth has a getXAuthToken method for doing exactly what I need. So I guess a better question is if I'm doing this for a few hundred users, would I run into a rate limit of any kind? Would I need to somehow throttle these in any way? Best, Y On May 26, 11:34 pm, YCBM youcannotb...@gmail.com wrote: Hi All, Is there any PHP script which I can take a look at to migrate users from basic auth to oauth? I've received temporary xAuth access and want to get it done within the less than 7 days (can this be extended) window granted. Thanks! Best, Y
[twitter-dev] Re: Bulk Conversion using xAuth
Ah. It looks like Abraham's twitteroauth has a getXAuthToken method for doing exactly what I need. So I guess a better question is if I'm doing this for a few hundred users, would I run into a rate limit of any kind? Would I need to somehow throttle these in any way? Best, Y On May 26, 11:34 pm, YCBM youcannotb...@gmail.com wrote: Hi All, Is there any PHP script which I can take a look at to migrate users from basic auth to oauth? I've received temporary xAuth access and want to get it done within the less than 7 days (can this be extended) window granted. Thanks! Best, Y
Re: [twitter-dev] Re: Bulk Conversion using xAuth
On Wed, May 26, 2010 at 11:44 PM, YCBM youcannotb...@gmail.com wrote: Ah. It looks like Abraham's twitteroauth has a getXAuthToken method for doing exactly what I need. So I guess a better question is if I'm doing this for a few hundred users, would I run into a rate limit of any kind? Would I need to somehow throttle these in any way? Best, Y When I did it, I just added a 1 second sleep in between each token grab and it worked fine. -damon -- http://twitter.com/damon http://blog.damonc.com
Re: [twitter-dev] Re: New social events on User Streams
I'll be looking at the OAuth issue(s) this week ---Mark http://twitter.com/mccv On Wed, May 26, 2010 at 5:36 PM, Fabien Penso fabienpe...@gmail.com wrote: John, Any chance it moves so quickly than time is left to look at the issue I've posted? Subject was 'UserStream : bug with oauth connection' On Wed, May 26, 2010 at 11:08 AM, John Kalucki j...@twitter.com wrote: I had to remove unfollow messages until we can sort out a complicated issue. The block and unblock messages remain. Sorry for the regression -- we're trying to move quickly.
Re: [twitter-dev] Status 401 on Streaming filter API with OAuth
I'll take a look at this issue this week. There are a few other issues in the same vein floating around. ---Mark http://twitter.com/mccv On Wed, May 26, 2010 at 2:54 AM, noki noris...@gmail.com wrote: Hi, I am in trouble with OAuth authentication of Streaming filter method with multi tracking words. I tryed status/filter method with track parameters. When I added one key word to track parameter, ex. track=noki, the returned status was 200(Authed). On the other hand, I got status 401 on two key words like track=noki,twitter or track=noki twitter the url encode may cause this problem but my lib. worked fine on REST APIs like status update. Is this my OAuth library bug or Twitter? Here is Auth header example. The tokens used to make sample header is: consumer_token = consumer_token consumer_secret = consumer_secret access_token = access_token access_secret = access_secret METHOD: POST URL: http://stream.twitter.com/1/statuses/filter.json PARAM: track=noki makes oauth_consumer_key=consumer_token, oauth_token=access_token, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274866253, oauth_nonce=69d53e881b216276c58a5368ad8038ea, oauth_version=1.0, oauth_signature=DEwB5M6sA1%2BKq2Xy%2FYx3nttm%2BGg%3D This works fine. but PARAM: track=noki,twitter makes oauth_consumer_key=consumer_token, oauth_token=access_token, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274866475, oauth_nonce=a448e7901d17808677bc46f6a2a180e7, oauth_version=1.0, oauth_signature=tRnND6u0mbQ%2BVLzAeGxQHvM%2FP3M%3D but does not work. Thank you. -- Norio Suzuki
[twitter-dev] Annotations Hackfest Update - join in remotely!
Hey all, Just wanted to update everyone and let you know that we are going to be extending the Annotations hackfest to anyone interested, regardless of whether or not you are able to make it to SF. We'll be providing a preview of Annotations to anyone interested with the caveat that it might get torn down again after the weekend is over if we feel like we need to make some changes based on the feedback from the weekend. Unfortunately the actual judging will only be possible for people that are able to make it to the office, but we wanted to make sure developers around the world were able to participate and provide feedback on this EARLY preview of Annotations. Your hard work will still get featured with everyone else's in the blog or wherever we end up putting links to all that was accomplished over the weekend. We will also be trying to setup video uplinks so we can all get to meet each other virtually, regardless of where you are geographically. So get your webcams ready. You'll still need to submit through the form in the blog post ( http://engineering.twitter.com/2010/05/annotations-hackfest.html) as we need the twitter handles of people on your team so we can enable Annotations for you. Please be sure to note in the description that you will be a remote team and where you will be tuning in from. We are incredibly excited to see what everyone comes up with. See you there physically or virtually. Best, Ryan
