Re: [twitter-dev] Email address Search
Twitter does not allow access to email addresses at all. On 9 May 2010 11:56, Vaibhav Agrawal iam.vaibhavagra...@gmail.com wrote: Hello Team, Is there any way to search friends/profiles on the basis of 'email address' only? We were trying to write an application and for that we have thought of using the email address as the basic search criteria. ( As first name, last name can be easily be duplicate in nature and we therefore want the search to return 'only one profile' or 'none'). It will be of great help from your side if you can suggest some solution. Thanks in advance, Cheers!
[twitter-dev] Followers / Following numbers.
There appears to be a problem, these have disappeared??
Re: [twitter-dev] Followers / Following numbers.
Saw your tweet after sending email. Sorry to disturb. On 10 May 2010 18:10, Taylor Singletary taylorsinglet...@twitter.comwrote: Hi Nigel, This is related to a bug discovered this morning -- it will be resolved shortly. More information: http://status.twitter.com/post/587210796/follow-bug-discovered-remedied Thanks, Taylor On Mon, May 10, 2010 at 10:06 AM, Nigel Legg nigel.l...@gmail.com wrote: There appears to be a problem, these have disappeared??
Re: [twitter-dev] Re: About update limits
Large recruitment consultancies seem to get very close to that limit, tweeting out details of vacancies. Can be quite useful to follow for a short while. On 30 April 2010 01:40, Dewald Pretorius dpr...@gmail.com wrote: I can't think of a use or requirement that would need more than 1,000 tweets per day. Unless you're promoting teeth whitening affiliate links that absolutely must be sent at a rate of one tweet every 30 seconds, because we all know how quickly the teeth of some followers turn yellow. On Apr 29, 8:45 pm, Brian Sutorius bsutor...@twitter.com wrote: To clarify, statuses/update is not affected by rate-limit whitelisting as it's a POST call and we don't maintain a separate whitelist for boosting the daily tweet limit above 1000. While we do not give out the specifics around the sub-limits, they *are* administered on a per-account basis and if you stay around your approximation of 20 tweets per half-hour you should be fine. Brian Sutorius On Apr 29, 6:07 am, Raffi Krikorian ra...@twitter.com wrote: the numbers are roughly broken up over the day. and the limit applies to an account. and yes - there is a whitelisting for status/updates -- please e-mail a...@twitter to ask for it. On Thu, Apr 29, 2010 at 5:26 AM, akaii chibiak...@gmail.com wrote: This is what the FAQ has to say about status update limits: Updates: 1,000 per day. The daily update limit is further broken down into smaller limits for semi-hourly intervals. Retweets are counted as updates. I'm a little unclear as to what exactly is meant by further broken down into smaller limits for semi-hourly intervals. Is the 1000 per day limit divided evenly between the 48 half hours each day (around 20 or so tweets per half an hour?). Also, I'm assuming this limit applies to each unique account? Is this limit absolutely fixed? Or is there some equivalent to whitelisting for status/update limits as well? Thanks... -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] dev.twitter.com usability - FAIL
Personally thought the new pages were a vast improvement on the old ones in terms of finding what I need. Usability is in the way the user thinks, I suppose. On 28 April 2010 15:11, Josh Roesslein jroessl...@gmail.com wrote: Yeah one improvement may be to place the API hurl tool into each API documentation page with all parameter pre-filled so it is ready to be experiment with to see how the responses look. This also helps avoid out of date info if the responses should change. Josh On Tue, Apr 27, 2010 at 4:21 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks for the feedback, Jonathon. We're working to address all these pain points on an ongoing basis. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 27, 2010 at 2:17 PM, Jonathon Hill jhill9...@gmail.comwrote: The new dev.twitter.com website that launched at Chirp a few weeks ago is very nice and attractive but there are several major usability issues: * The new API documentation does not provide return values of the API calls. The old wiki provided this information, along with usage notes that are not present either on the new site. * It is difficult to look up API endpoints required for a given type of functionality. If you don't remember the exact endpoint to look for, it can be frustrating trying to find the right one. This would easily be fixed using a more descriptive list of endpoints, and/or more visual contrast between headings and list items. * I tend to overlook the endpoint description in the blue header section. My eyes expect it in the white area below. Please move it, and make it stand out more. * The Supported formats, Supported request methods, Requires Authentication, and Rate Limited sections use up an awful lot of vertical space on the page unnecessarily. Making each one of these a heading also dilutes the visual hierarchy on the page and takes away from more detailed and important information on the page, from a reference standpoint. I think these would be more effectively presented as a list under a Metadata heading, or as a small table. * The API console is very restricted without login and registration of an app. I think this is a mistake. Login should be required only for those calls that require authentication. * The API console would be much easier to use if there were parameter hints for each call on the page somewhere. Prepopulating the parameter list would be awesome! These are all things that have been kindof in my face as I've tried to use dev.twitter.com in my day to day development work. I would be delighted if you would address these issues. Thanks! Jonathon Hill Company52 http://company52.com @compwright
Re: [twitter-dev] Re: Early look at Annotations
Been following the conversation; very interesting to see, even today, the devlopment of ideas around potential standards from the community of developers. To see the trends, most used, etc will definitely help us work towards the namespaces and keys with the most utility for ourselves and our users. On 16 April 2010 22:17, Marcel Molina mar...@twitter.com wrote: I've talked to the analytics team. Three main metrics we're going to work to surface on something like dev.twitter.com initially (and maybe even an API so you all can build experiences/explorers around annotations): 1) All time most used namespaces/keys. 2) Trending namespace/keys. 3) Most widely adopted namespace/keys (i.e. not necessarily the most used but the ones used by the highest number of different client applications) On Fri, Apr 16, 2010 at 1:43 PM, Marcel Molina mar...@twitter.com wrote: This is a great idea for how to bootstrap and fuel the adoption and consensus on namespaces and key names. I'm going to talk to our analytics team and see if we can surface analytics on the most used namespaces and those namespace's most used keys. On Fri, Apr 16, 2010 at 1:05 PM, Jaanus jaa...@gmail.com wrote: Another 2c: you should think about publishing numbers/stats for annotations. Easiest to start on the level of namespaces. Publish stats about popularity of namespaces: how many tweets and how many users use which namespaces. And don't do that's a good idea and there are still many moving parts and we are thinking of it for the future, do this is absolutely vital for the community from day 1 :) This would be a good measure for community to inform what namespaces to support, what works and what doesn't, etc. J -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- Marcel Molina Twitter Platform Team http://twitter.com/noradio -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
Re: [twitter-dev] Re: Early look at Annotations
I'd say keep it all on dev.twitter.com - minimise sites to visit. On 16 April 2010 22:44, Raffi Krikorian ra...@twitter.com wrote: i expect we'll put a page up on dev.twitter.com that will allow people to list out namespaces, keys, etc. all for the community. On Fri, Apr 16, 2010 at 2:41 PM, Robby Grossman ro...@freerobby.comwrote: Thanks for all of the info, Marcel. Cool stuff! How would people feel about a wiki for developers to share thoughts on how to use/standardize on annotations? That would give us a chance to flesh out some of the namespacing issues that have been raised so that we can hit the ground running when Annotations are launched. I'd be happy to set up a PBWorks page or maybe a Google Doc that can be shared with this list. --Robby On Apr 16, 5:17 pm, Marcel Molina mar...@twitter.com wrote: I've talked to the analytics team. Three main metrics we're going to work to surface on something like dev.twitter.com initially (and maybe even an API so you all can build experiences/explorers around annotations): 1) All time most used namespaces/keys. 2) Trending namespace/keys. 3) Most widely adopted namespace/keys (i.e. not necessarily the most used but the ones used by the highest number of different client applications) On Fri, Apr 16, 2010 at 1:43 PM, Marcel Molina mar...@twitter.com wrote: This is a great idea for how to bootstrap and fuel the adoption and consensus on namespaces and key names. I'm going to talk to our analytics team and see if we can surface analytics on the most used namespaces and those namespace's most used keys. On Fri, Apr 16, 2010 at 1:05 PM, Jaanus jaa...@gmail.com wrote: Another 2c: you should think about publishing numbers/stats for annotations. Easiest to start on the level of namespaces. Publish stats about popularity of namespaces: how many tweets and how many users use which namespaces. And don't do that's a good idea and there are still many moving parts and we are thinking of it for the future, do this is absolutely vital for the community from day 1 :) This would be a good measure for community to inform what namespaces to support, what works and what doesn't, etc. J -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- Marcel Molina Twitter Platform Team http://twitter.com/noradio -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] dev.twitter.com
I just tweeted how much I like it. The console is a great touch. Well done, Taylor all at twitter. On 14 April 2010 23:05, Yogesh Mali yomali1...@gmail.com wrote: Awesome !! Nice work . On Wed, Apr 14, 2010 at 5:00 PM, Peter Denton petermden...@gmail.comwrote: Yeah, very nice work team. Thanks for doing this. On Wed, Apr 14, 2010 at 2:52 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks for the positive feedback! We're working hard on making this always the most up to date resource as possible -- admittedly, there's still some work to do to get everything in agreement with the dynamic world of the wiki. Look for much more to come on this portal. It's going to keep getting more awesome! Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, Apr 14, 2010 at 2:49 PM, Raffi Krikorian ra...@twitter.comwrote: cool - thanks - taylor has been spending a lot of time behind the scenes pushing this forward. he has always felt that having this portal was extremely important for developers, and he made it happen. On Wed, Apr 14, 2010 at 2:38 PM, Atul Kulkarni atulskulka...@gmail.com wrote: +1... this is nice. On Wed, Apr 14, 2010 at 4:27 PM, Dewald Pretorius dpr...@gmail.comwrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Regards, Atul Kulkarni -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Annotation details
I look forward to reading about this, sounds... intriguing. On 14 April 2010 22:50, Raffi Krikorian ra...@twitter.com wrote: we will be releasing data in due time! On Wed, Apr 14, 2010 at 2:05 PM, James Teters jtet...@gmail.com wrote: Just curious if there is any documentation on how annotations will be implemented? Any ideas on size limitations or restrictions for this meta data? -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Promoted Tweets and the API?
Is promotion of tweets going to be part of the algorithm for defining popular tweets - in a twisted world where twitter says it's popular coz they've taken the cash to say it's popular? [sorry, that sounds like rigging charts or something... not quite how I meant it to sound] Awaiting further details. On 13 April 2010 14:48, Duane Roelands duane.roela...@gmail.com wrote: I'm curious about this myself. One of the first things end users are going to ask for is a way to block these ads from their timelines. Don't kid yourself; there's a reason why AdBlock is such a popular Firefox plugin. Secondary question: Is the first step towards paid Twitter accounts, where free users have to receive ads and paid users do not? Straight answers here would be appreciated. On 13 Apr, 05:28, Tim fabianh...@googlemail.com wrote: I've been looking around for information on how the new promoted tweets advertising feature will affect the API, and I've not really found anything. I gather that it's a two phase approach starting with search and then rolling out to timelines, but can anyone here clarify: (a) whether API responses will include promoted tweets, (b) whether these tweets will be identified as ads (c) whether third parties are 'obligated' to present them to users (d) whether there will be an API Terms of Use as a result
Re: [twitter-dev] Re: Promoted Tweets and the API?
At present, search is not on my radar as an API I want to use in development, but I am concerned about the implications for monitoring services based on the search API. On 13 April 2010 15:31, Dewald Pretorius dpr...@gmail.com wrote: Don't be too hasty with that ad blocking code. 1) It sounds as if Twitter will share ad revenue with external apps. 2) It very well might be against (new) API TOS to use the API and block ads (I would do that if I were them). On Apr 13, 10:48 am, Duane Roelands duane.roela...@gmail.com wrote: I'm curious about this myself. One of the first things end users are going to ask for is a way to block these ads from their timelines. Don't kid yourself; there's a reason why AdBlock is such a popular Firefox plugin. Secondary question: Is the first step towards paid Twitter accounts, where free users have to receive ads and paid users do not? Straight answers here would be appreciated. On 13 Apr, 05:28, Tim fabianh...@googlemail.com wrote: I've been looking around for information on how the new promoted tweets advertising feature will affect the API, and I've not really found anything. I gather that it's a two phase approach starting with search and then rolling out to timelines, but can anyone here clarify: (a) whether API responses will include promoted tweets, (b) whether these tweets will be identified as ads (c) whether third parties are 'obligated' to present them to users (d) whether there will be an API Terms of Use as a result- Hide quoted text - - Show quoted text - -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] How to find the frequency of messages exchanged between 2 users
Direct messages are by nature supposed to be private between sender and receiver (and vice versa). My understanding is that they cannot be accessed by anyone apart from those authorised to access them (account holders). If I am worng in this assumption, I have two years worth of scurrilous if not libellous DMs to clear up fast. @mentions are another matter, but there is no api call to find them. On 12 April 2010 21:04, M. Edward (Ed) Borasky zn...@comcast.net wrote: On 04/12/2010 12:20 PM, Abraham Williams wrote: You will have to pull the direct messages and mentions from both users and correlate the data yourself. Abraham Moreover, accessing the direct messages of *two* users involves authenticating as *both* of them. It is highly unlikely you will be permitted to do so by people who don't have a legal contract with you. And that agreement should *clearly* specify * what is permitted and forbidden, and * *penalties* for breaking that agreement. That's the world we now live in - get used to it. This whole click this here button and get nifty stuff for free attitude is starting to unravel. -- M. Edward (Ed) Borasky http://borasky-research.net/m-edward-ed-borasky/ @znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
Re: [twitter-dev] Re: Final Hack Day schedule for Chirp with discount code
I'd love to be there, but I have commitments here I can't get away from at such short notice. Damn. I'll follow on twitter, assuming people use it. ;-) On 11 April 2010 02:23, funkatron funkat...@gmail.com wrote: I actually would consider buying these tickets, but 5 days notice; that's not so good for non-locals. Thanks for trying to make it affordable to mailing list folks, tho. -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.comxmpp%3afunkat...@gmail.com On Apr 10, 9:18 pm, Ryan Sarver rsar...@twitter.com wrote: Hey all, Wanted to let you know that we have finalized the schedule for Hack Day sessions at Chirp. We're really excited about the content and would love to have you there. Also, each session has a Google Moderator section setup so you can get your questions in ahead of time. Be sure to add your questions so the speakers know what to talk to:http://bit.ly/dbpnXZ Hack Day tickets are still available and we're providing a 50% discount for the first 100 registrations from the mailing list. Please don't share this outside of this listhttp://chirp.eventbrite.com/?discount=DEVTALK10 Hopefully see you next week! Best, rs *Quick Agenda for Hack Day* *Apr 14th* - 6pm - Hack Day registration, dinner and drinks - 8pm - Ignite Chirp hosted by Brady Forrest - 9pm+ - Hacking for the night owls *Apr 15th* - 8am - 10am - Registration and breakfast (Registration is open all day) - 10am - Welcome with Ron Conway - 10:15am - 5pm - Sessions start and go all day with a lunch you shouldn't miss - 5pm - App Showcase with Marissa Mayer, Paul Graham and Philip Kaplan. Moderated by Jason Goldman (@goldman) - 9pm - Chirp Party at 1015 Folsom *Hack Day Sessions* *Twitter Streaming API Architecture and What's Next* #chirpstream with John Kalucki *Eating our own Dogfood: Designing Twitter Mobile Web* #chirpmobile with Leland Rechis *We Have Faith In (Most of) You: How Twitter Crafts Policies to Allow Good Apps to Thrive* #chirppolicy with Del Harvey *Office Hours: Twitter Platform Team* with Ryan Sarver, Doug Williams, Raffi Krikorian, Mark McBride, Dana Contreras, Isaac Hepworth, Marcel Molina, Taylor Singletary, Todd Kloots, Wilhelm Bierbaum *Office Hours: Design/UX *with Doug Bowman, Zhanna Shamis, Britt Selvitelle, Patrck Ewing, Mark Trammel, Vitor Lourenço, Mark Otto, Coleen Baik *Integrating @anywhere* #chirpanywhere with Todd Kloots, Dustin Diaz, Dan Webb, Russ D'Sa *Effective Use of the Twitter Search API *#chirpsearch with Eric Jensen *Analyzing Big Data at Twitter* #chirpdata with Kevin Weil *Office Hours: Working at Twitter* @jointheflock with Oliver Ryan, Bernadette Coh, Jamie Narva, Michelle Gale, Morgan Missentzis, Olivia Watkins *Office Hours: The Electronic Frontier Foundation* with Marcia Hofmann, Kurt Opsahl, Cindy Cohn, Fred von Lohmann *Twitter, Media, and Kanye's Exploding Head* #chirpmedia with Chloe Sladden, Robin Sloan *Too many secrets, but never enough: Twitter OAuth *#chirpoauth with Taylor Singletary, Raffi Krikorian *Changing Engines Mid-flight: Moving Twitter from MySQL to Cassandra*#chirpcassandra with Ryan King *Birds of a Feather: Real-Time Search* with Doug Cook *Office Hours: Trademark Policy and Branding Guidelines *with Jillian West, Jeremy Kessel, Francesca Helena, Tim Yip, Bakari Brock *The How and Why of Scala at Twitter* #chirpscala with Alex Payne *What's happening? to What's happening here?* #chirpgeo with Raffi Krikorian *Thinking in Streams: Patterns for Stream Processing* #chirpstream with John Kalucki *Meet and Greet: Founders* with Evan Williams and Biz Stone *Office Hours: Twitter Corp and Business Development* with Elizabeth Weil, Doug Williams, Isaac Hepworth, Bakari Brock, Jessica Verrilli *Billions of Hits: Scaling Twitter* #chirpscale with John Adams *Twitter International* #chirpintl with Matt Sanford *All Aboard? Turning Users into Active Users* #chirponboard with Josh Elman *Meet and Greet: Funding* with David Cohen, Paul Graham, Ron Conway *Birds of a Feather: Media Curation* with Chloe Sladden and Robin Sloan -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Twitter buying Tweetie
My twitter client will be ready in about a month. I hope I have unique enough features to survive. On 11 April 2010 02:27, Arnaud Meunier arnaud.meun...@twitoaster.comwrote: +1 for the metaphors :) We all know what Twitter would like to see. No surprise here, nothing extraordinary, just advices we already were aware of. I mean... Who intended to code another photo sharing service or another desktop client before these annoucements? I guess nobody. Anybody who has been seriously thinking about starting a project around Twitter in the last year already knew he'd have to make something innovative enough to drag attention, customers, whatever he's looking for... In a word, there's nothing new with these annoucements and this acquisation. The only thing new is simply the fact that it's now officially said. Quite annoying for all the old school apps (thinking to existing clients, analytics services, media sharing tools...) Even for some of the new one, by the way, as a part of the applications who's going to emerge will probably wonder what if Twitter decides to make a product of my concept? Inherent risk of a business based (even partly) on an existing platform? Yes! And the thing is I'm very curious to see how Twitter is going to deal with this at Chirp, and what (really new, this time) they're going to announce. For example, a smart monetization policy (around advertising or sponsored tweets) linked to the API could be an answer for most of the old school apps. Arnaud - http://twitter.com/twitoaster Twitoaster - http://twitoaster.com Le 11 avr. 2010 à 01:04, zn...@comcast.net zn...@comcast.net a écrit : - Jesse Stay jesses...@gmail.com wrote: Why are you filling holes in Twitter? Why not rather create your own holes and use Twitter to fill them. When you own the dirt you have control over what grows in that dirt. I think we've pretty much exhausted the holes and dirt metaphor, and I'd like to propose a different one. A business is defined by the answer(s) to the question, Who is going to sell what to whom? So, what are the needs of the Twitter customer base? Raffi has posted some things he'd like to see, and I read the blogs regularly and have some clues as to what people like @scobleizer, @mashable, etc. think Twitter should become. And it all boils down to what real problems people have, what costs them money and time, what they don't know that could hurt them, and so on. Once we know what the problems are, how can the *Twitter* ecosystem solve them? @znmeb -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Details on the Chirp Hack Day Showcase
I'd love to resent, but can't make it to Chirp. Maybe next year. On 9 April 2010 07:11, Doug Williams d...@twitter.com wrote: Hi all -- The Hack Day at Chirp is a remarkable opportunity for the Twitter Platform. It is the first time that the ecosystem and Twitter's extended team will meet under one roof. We are excited to collaborate at such a deep level; answering questions face-to-face while updating the Twitter team on the innovation ongoing in the ecosystem. It is cool to think that the Hack Day will represent the largest pool of ecosystem companies and projects in the same room. To celebrate, we are hosting a Showcase to demo several apps developed during the event in addition to nascent companies beginning to gain traction. Here are some of the ideas we will we will look for: * Commerce: tools for marketers, consumer analytics and consumer insights. * Engagement: platforms for social good and government, leveraging Twitter to drive engagement. * Consumption: tools that surface relevant content, vertical integrations, leveraging geotagged tweets, innovative mobile experiences, user discovery, and media curation. * Infrastructure: tools for developers, and application marketing and distribution. The Showcase will feature demos of select products and a panel to discuss the opportunities explored by these budding projects. The only rules: projects must be less than one years old, must have less than one million dollars in funding and someone must be at the Chirp Hack Day on April 15th to present. To apply to demo at the Hack Day Showcase, please apply here [1] by 3PM on April 15th, 2010. 1. http://bit.ly/chirpshowcase Thanks, Doug http://twitter.com/dougw -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Fred Wilson article on Twitter API
There will always be room for developers on the fringes, and novel ways of using twitter. I would hope that twitter will concentrate on the maintenance and development of the core system, and allow us to add the bells and whistles as required by our own set of users. On 9 April 2010 13:56, Dewald Pretorius dpr...@gmail.com wrote: With Fred being a Twitter board member, and with the enthusiasm for the article that was displayed by Twitter employees: 1) Do we all need to stop right now with developing any further gap filler type of functionality or apps? 2) Is there only a future in the ecosystem for the very minute handful of developers who happen to chance upon the idea of a killer app? 3) Can we now expect Twitter to drive most of us out of business or existence by building into Twitter the functionality that we built into our apps? -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Musings About Twitter Search (was Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available))
Ed, I would like to re-read your blog post, but it's redirecting me through oAuth into Twitoaster??? On 6 April 2010 01:08, M. Edward (Ed) Borasky zn...@comcast.net wrote: On 04/05/2010 09:47 AM, Dewald Pretorius wrote: +1 ^ 10. Very well said, Ed. You're getting an enthusiastic standing ovation and one-man Mexican wave from me. I think as a community, we're letting a golden opportunity for discussion about Twitter Search pass us by while we vent and rant about the inconveniences and about roles and titles. I'm not by any means an expert on search in the large, although I do spend a fair amount of time trying to keep up with the natural language processing and computational linear algebra technologies that power search. But I think the discussion we *should* be having is not about the mechanics of the API, the logistics of API versioning, developer best practices or roles withing the community. I don't even think it should be about business models, although that's certain a part of it. I think the discussion we should be having is about Twitter Search itself - how it should work to meet the needs of the two classes of users I call seekers and sellers. I posted a call for this discussion on my blog a while back, but haven't had many takers. So here it is again: http://borasky-research.net/2010/03/19/seeker-or-seller-what-do-you-think-about-adding-popularity-to-twitter-search-tweetsearchpop/ If there's enough interest, maybe we can put together an unconference session on this at Chirp. -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
On 6 April 2010 17:27, Raffi Krikorian ra...@twitter.com wrote: our search and relevancy algorithms are constantly changing. we take in a slew of signals like engagement or conversation around tweets, and use that to pull it higher in search results. whether we will provide the exact details of how that algorithm works, i'm not sure. its analogous to google page rankings -- the general notion is well known, but the exact details are constantly changing behind the scenes. we're still trying to figure out things internally regarding these top tweets / popular tweets / relevant tweets, but, as always, one could just connect to the streaming API and get true real time tweets for earthquake. Maybe I could, but my 70 year old other couldn't. I also was talking from a users point of view, not a developers, and even for a develper, you might just want the data a little faster than you could knock up the working code to check the streaming API. At the moment, with 3-4 tweets from popular at the top, it's not too much of a problem, but my worry is that twitter intend to roll out the popularity algorithm to larger and larger chunks of search, thus losing the real time search aspect of which it should be proud. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Lists count in User object
List membership is as important as followers in terms of reach of a twitter account (I won't say person, as bots and group-run corporate accounts also have followers and get on lists). If you cannot easily see haw many lists a person is on, you can't see a) how relevant / influential they are to their current followers; and b) the potential reach, beyond the n. followers they already have, that the lists represent. At the moment I permanently follow three lists created by other people, on which more than half the people I don't follow, I'm sure there are plenty of other people (especially tweetdeck users, where it is so easy) who do the same thing. For these reasons, I would say putting the list count in the user object would provide us and our users with very useful additional piece of data. Cheers, Nigel. On 2 April 2010 07:19, Damon C d.lifehac...@gmail.com wrote: I heard somewhere that the list count is supposed to be included in the user object at some point, although I can't remember where I heard that/what the timeline was. Until then, best solution appears to be (I hate to say it) scraping the website. Otherwise, the API calls could get out of hand for users on a ton of lists. Damon On Apr 1, 10:20 pm, Orian Marx (@orian) or...@orianmarx.com wrote: Yeah this was logged in the bug tracker I think the day lists were rolled out to the public, but it looks like it never received an official response and is still marked as a new entry. :( http://code.google.com/p/twitter-api/issues/detail?id=1186 On Apr 1, 5:16 pm, DustyReagan dustyrea...@gmail.com wrote: I was wondering if it'd be possible to get the number of lists a user belongs to returned in the User object. I noticed the list count is displayed beside status, follower, and following counts all over Twitter, looks like the list count may be on the same level as the other counts. I'd like to include the list counts in my application without making additional API calls. Possibility? -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Opt-in beta of Popular Tweets for the Search API now available
Taylor, I have two questions; I thought you answered them in the original thread, but could not find them. 1. How are popular tweets defined? Tweets from accounts with lots of followers, or tweets that have been retweeted the most, or what? 2. And that leads to : you mention having a metadata point for number of times the tweet has been retweeted. Is that as in hitting the Retweet button only, or will copying and pasting, editing and adding value also count? If I retweet you, and 3 of my followers retweet that, with the retweet button I get no credit and don't even know it has happened unless I go into the website. Having a retweets field which only counts the RT button will further entrench this feature which is very damaging to the sense of community and way a lot of people use twitter (certainly over here). Sorry for the rant. Nigel. On 2 April 2010 02:03, @dbbradle dbradl...@gmail.com wrote: Thanks, Taylor and Twitter API team! I know what I'm doing this weekend :) On Apr 1, 5:53 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Folks, As indicated a few weeks ago, we're launching our new *beta* enhancements to search.twitter.com and the Search API today -- it's currently rolling out to our servers. Thank you all for your feedback. *Key API Takeaways*: - During the current phase, receiving popular tweets in your API search results is *OPT-IN*. You will not see the new top results in search unless you specify the *result_typ**e* parameter on your search query string. - The result_type parameter takes one of three values: * *mixed* - receive both popular tweets and most recent tweets for the query. This is the equivalent of the future default behavior. * *popular* - receive only popular tweets for the query. * *recent* - receive only recent results for the query. This is the equivalent of the behavior you've come to expect until present - Each tweet in a search result will now contain a metadata node, with a field called 'result_type' that indicates whether the tweet is popular or recent. In the future, there may be other result_types. The metadata node will eventually contain other fields as well. - In addition to result_type, the metadata node may also include a 'recent_retweets' field indicating the number of retweets the tweet has received recently, rounded to a reasonable integer. - This metadata field will now appear in search results regardless of your OPT-IN status on the popular tweets feature. You don't have to do anything to receive this new metadata along with tweets in search results. In JSON, the metadata field is simply metadata. In XML, you'll see it expressed as twitter:metadata. *Continued Discussion*: To date, Twitter's real-time search has proven to be incredibly valuable. People, businesses and organizations have come to depend on finding out what's being discussed about a particular topic *right now*. We've been really impressed at the integrations many of you have developed using the Search API. Whether it's offering search columns in a Twitter client, mapping #hashtags to search, or deep analysis of trends and brand monitoring, you've shown us what's possible with Twitter search. With this new project, we want to make real-time search even more valuable by surfacing the best tweets about a particular topic, by considering recency, but also the interactions on a tweet. This means analyzing the author's profile, as well as the number times the tweet has been retweeted, favorited, replied, and more. It's an evolving algorithm that we'll be iterating on tuning until practically the end of time. With this initial release, if we detect that there are particularly interesting relevant tweets for a given query, we'll display at most 3 of these tweets at the top of the page. We'll also display the number of times these tweets have been recently retweeted as well. You can check outhttp://search.twitter.comto see our new beta relevancy results now. Using the new features of the API we're launching today, you could build a similar interface for the popular results but we're expecting awesome creative uses of these new result types, not necessarily limited to user-facing features. Explore the new result formats and options in the updated Search API documentation: http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-searchand our original post on the subject: http://groups.google.com/group/twitter-api-announce/browse_thread/thr... Happy Hacking! Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] How to Index Twitter Profiles?
Collect the user object data from selected users? - use the Get User Details API call when they have opted in - to do this, it is important that the user opts in. On 2 April 2010 10:28, muni muni.i...@gmail.com wrote: Hello Folks, I was googling for the twitter directories and found that there are hundreds of Directories available. Does any one has any Idea on how these are building/ populating their DB with the Twitter Profiles from Twitter. Is there any better way of building the Local Database with the Twitter Profiles? Looking for your reply. Thanks, Muni. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Sharing MySQL User Table Schema
Dusty, just took a look at that, good stuff. Wouldn't it be better database design to have separate tables for user and status, and only update user details if they have changed? This design suggests you will have a lot of duplicate data in the database. Just a thought. Nigel. On 2 April 2010 02:26, DustyReagan dustyrea...@gmail.com wrote: Hey Damon! FoF is missing several new and new(ish) fields, particularly because it takes ages to update the DB. I'll add the verified field to gist! Thanks for pointing out the protected field! I think I set it to varchar(5) because Twitter sometimes sends back 'false' and sometimes sends back '1', and most of the time sends back null. (It may send back '0', and 'true' as well, I can't remember.) I save it to the DB the way Twitter sends it, and do the mapping on read. Probably the smart thing to do is, like you said, make it a tinyint(1) then scrub the data before insert. My new strategy to database updates is 1) to do as many as possible in one batch 2) put Friend Or Follow in read-only mode, so it still works, but the DB user cache/table isn't updating. I can stop doing inserts for a few days before anyone seems to really notice. A more better solution would probably be some sorta' hot swap, ie: point the app to a backup copy of the DB, do the updates on the primary DB, then point the app back to the primary DB. It's easier for me to just go read-only for a stint though. Updates are a headache with YesSQL for sure! On Apr 1, 7:15 pm, Damon C d.lifehac...@gmail.com wrote: Curious why you're using a varchar field for protected as opposed to tinyint(1)/boolean? I don't see a verified field either, not sure if that's necessary for FoF. Other than that, most of my stuff is pretty similar although I'm not quite as discerning on the lengths of the fields. I usually just do varchar(255). Do you have a strategy/opinion for when Twitter adds additional fields like geo, verified, etc? This is one of the primary reasons I've been considering leaving YesSQL since I have to shut down my site for hours just to do an ALTER. :( Damon On Apr 1, 4:12 pm, DustyReagan dustyrea...@gmail.com wrote: So, it occurs to me how many developers must be reinventing the MySQL schema for the User object. I've started work on optimizing my database for Friend Or Follow, and thought it'd be cool to share my schema and collaborate with other YesSQL users. Here's where I'm starting: http://dustyreagan.com/twitter-mysql-user-object-table-schema/ Leave comments here or on my blog and I'll update the MySQL in the main post. It'd be nice to have this for other Twitter objects as well. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Retweets of me...
Just been checking out the retweets of me function, using http://api.twitter.com/1/statuses/retweets_of_me.xml, and my own user name and password. Am I missing something? This function does not show who retweeted me or when - just what was retweeted. Another reason to use cut and paste and edit - with RT @nigellegg in it - then the person you are retweeting will see who retweeted them and when. Though I am obviously missing something, as on twitter.com I have found who retweeted me and when. Am I using the wrong function to do this? Cheers, Nigel. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Retweets of me...
So it's two steps to knowing a simple thing... seems a bit clunky. Is there a simpler way of doing this?? On 2 April 2010 16:43, Abraham Williams 4bra...@gmail.com wrote: Once you know which tweets have been retweeted you can use statuses/id/retweeted_by [1] to see who retweeted them. Abraham [1] http://apiwiki.twitter.com/Twitter-REST-API-Method:-GET-statuses-id-retweeted_by On Fri, Apr 2, 2010 at 08:09, Nigel Legg nigel.l...@gmail.com wrote: Just been checking out the retweets of me function, using http://api.twitter.com/1/statuses/retweets_of_me.xml, and my own user name and password. Am I missing something? This function does not show who retweeted me or when - just what was retweeted. Another reason to use cut and paste and edit - with RT @nigellegg in it - then the person you are retweeting will see who retweeted them and when. Though I am obviously missing something, as on twitter.com I have found who retweeted me and when. Am I using the wrong function to do this? Cheers, Nigel. -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Retweets of me...
Long way round, and uses up api calls hmm. On 2 April 2010 17:29, Abraham Williams 4bra...@gmail.com wrote: Not that I know of. Abraham On Fri, Apr 2, 2010 at 08:45, Nigel Legg nigel.l...@gmail.com wrote: So it's two steps to knowing a simple thing... seems a bit clunky. Is there a simpler way of doing this?? On 2 April 2010 16:43, Abraham Williams 4bra...@gmail.com wrote: Once you know which tweets have been retweeted you can use statuses/id/retweeted_by [1] to see who retweeted them. Abraham [1] http://apiwiki.twitter.com/Twitter-REST-API-Method:-GET-statuses-id-retweeted_by On Fri, Apr 2, 2010 at 08:09, Nigel Legg nigel.l...@gmail.com wrote: Just been checking out the retweets of me function, using http://api.twitter.com/1/statuses/retweets_of_me.xml, and my own user name and password. Am I missing something? This function does not show who retweeted me or when - just what was retweeted. Another reason to use cut and paste and edit - with RT @nigellegg in it - then the person you are retweeting will see who retweeted them and when. Though I am obviously missing something, as on twitter.com I have found who retweeted me and when. Am I using the wrong function to do this? Cheers, Nigel. -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Re: Opt-in beta of Popular Tweets for the Search API now available
Thanks Raffi, I won't go near those retweet functions. As for the popularity stuff, will the algorithm you use be open? It wouldn't be good for either side if someone else developed a popularity index which showed different results from yours. On 2 April 2010 18:00, Raffi Krikorian ra...@twitter.com wrote: Taylor, I have two questions; I thought you answered them in the original thread, but could not find them. 1. How are popular tweets defined? Tweets from accounts with lots of followers, or tweets that have been retweeted the most, or what? from taylor's e-mail: With this new project, we want to make real-time search even more valuable by surfacing the best tweets about a particular topic, by considering recency, but also the interactions on a tweet. This means analyzing the author's profile, as well as the number times the tweet has been retweeted, favorited, replied, and more. It's an evolving algorithm that we'll be iterating on tuning until practically the end of time. hope that helps. 2. And that leads to : you mention having a metadata point for number of times the tweet has been retweeted. Is that as in hitting the Retweet button only, or will copying and pasting, editing and adding value also count? If I retweet you, and 3 of my followers retweet that, with the retweet button I get no credit and don't even know it has happened unless I go into the website. Having a retweets field which only counts the RT button will further entrench this feature which is very damaging to the sense of community and way a lot of people use twitter (certainly over here). i'm pretty sure its native RTs only, right now. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Lists count in User object
Good news - especially as I see number of lists a user is on as being an important factor affecting the (potential) popularity of their tweets ;-). On 2 April 2010 17:57, Raffi Krikorian ra...@twitter.com wrote: yup - its on our list. we're working on a series of things behind the scenes which will allow us to have volatile data available in user objects in a scalable manner in the API. as you all probably know, the user object is embedded in the status object, and sometimes those objects become out of sync with reality and the like -- once we fix this, getting list data into the user object is high on the list. On Fri, Apr 2, 2010 at 12:51 AM, Nigel Legg nigel.l...@gmail.com wrote: List membership is as important as followers in terms of reach of a twitter account (I won't say person, as bots and group-run corporate accounts also have followers and get on lists). If you cannot easily see haw many lists a person is on, you can't see a) how relevant / influential they are to their current followers; and b) the potential reach, beyond the n. followers they already have, that the lists represent. At the moment I permanently follow three lists created by other people, on which more than half the people I don't follow, I'm sure there are plenty of other people (especially tweetdeck users, where it is so easy) who do the same thing. For these reasons, I would say putting the list count in the user object would provide us and our users with very useful additional piece of data. Cheers, Nigel. On 2 April 2010 07:19, Damon C d.lifehac...@gmail.com wrote: I heard somewhere that the list count is supposed to be included in the user object at some point, although I can't remember where I heard that/what the timeline was. Until then, best solution appears to be (I hate to say it) scraping the website. Otherwise, the API calls could get out of hand for users on a ton of lists. Damon On Apr 1, 10:20 pm, Orian Marx (@orian) or...@orianmarx.com wrote: Yeah this was logged in the bug tracker I think the day lists were rolled out to the public, but it looks like it never received an official response and is still marked as a new entry. :( http://code.google.com/p/twitter-api/issues/detail?id=1186 On Apr 1, 5:16 pm, DustyReagan dustyrea...@gmail.com wrote: I was wondering if it'd be possible to get the number of lists a user belongs to returned in the User object. I noticed the list count is displayed beside status, follower, and following counts all over Twitter, looks like the list count may be on the same level as the other counts. I'd like to include the list counts in my application without making additional API calls. Possibility? -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Sharing MySQL User Table Schema
Dusty, Sure if you only store the last tweet, that's cool - should have asked before jumping to conclusions. For what I want, it'll definitely be better to have a separate table, and only update what needs changing. When I'm done messing round with OAuth, and sorting out my GUI, I'll be looking at that side of things again - had a whole lot more to do than I thought. On 2 April 2010 19:17, DustyReagan dustyrea...@gmail.com wrote: Nigel, It depends on what you're trying to accomplish. For example, for Friend Or Follow I only store the user's latest tweet. I disregard all other tweets. In that case storing the last status object with the user object makes the most sense, and does not create duplicate rows. If you're storing more than the user's last tweet, absolutely, you should have a 'tweet' table and a 'user' table linked by the user's twitter_id. On Apr 2, 6:55 am, Nigel Legg nigel.l...@gmail.com wrote: Dusty, just took a look at that, good stuff. Wouldn't it be better database design to have separate tables for user and status, and only update user details if they have changed? This design suggests you will have a lot of duplicate data in the database. Just a thought. Nigel. On 2 April 2010 02:26, DustyReagan dustyrea...@gmail.com wrote: Hey Damon! FoF is missing several new and new(ish) fields, particularly because it takes ages to update the DB. I'll add the verified field to gist! Thanks for pointing out the protected field! I think I set it to varchar(5) because Twitter sometimes sends back 'false' and sometimes sends back '1', and most of the time sends back null. (It may send back '0', and 'true' as well, I can't remember.) I save it to the DB the way Twitter sends it, and do the mapping on read. Probably the smart thing to do is, like you said, make it a tinyint(1) then scrub the data before insert. My new strategy to database updates is 1) to do as many as possible in one batch 2) put Friend Or Follow in read-only mode, so it still works, but the DB user cache/table isn't updating. I can stop doing inserts for a few days before anyone seems to really notice. A more better solution would probably be some sorta' hot swap, ie: point the app to a backup copy of the DB, do the updates on the primary DB, then point the app back to the primary DB. It's easier for me to just go read-only for a stint though. Updates are a headache with YesSQL for sure! On Apr 1, 7:15 pm, Damon C d.lifehac...@gmail.com wrote: Curious why you're using a varchar field for protected as opposed to tinyint(1)/boolean? I don't see a verified field either, not sure if that's necessary for FoF. Other than that, most of my stuff is pretty similar although I'm not quite as discerning on the lengths of the fields. I usually just do varchar(255). Do you have a strategy/opinion for when Twitter adds additional fields like geo, verified, etc? This is one of the primary reasons I've been considering leaving YesSQL since I have to shut down my site for hours just to do an ALTER. :( Damon On Apr 1, 4:12 pm, DustyReagan dustyrea...@gmail.com wrote: So, it occurs to me how many developers must be reinventing the MySQL schema for the User object. I've started work on optimizing my database for Friend Or Follow, and thought it'd be cool to share my schema and collaborate with other YesSQL users. Here's where I'm starting: http://dustyreagan.com/twitter-mysql-user-object-table-schema/ Leave comments here or on my blog and I'll update the MySQL in the main post. It'd be nice to have this for other Twitter objects as well. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Popular Tweets
I hate to go back to what I was saying earlier. I understand that the algorithm is still under development, but if we understood what the algorithm for defining a popular tweet was, we would be able to understand why Osman is seeing the results that he has found here. On 2 April 2010 22:48, Osman Ali osman.lx...@gmail.com wrote: Hi: some questions regarding the popular tweets feature. These are all based on a user-end interaction with search.twitter.com. 1. Is popular search moving to home page search at any point or is it just staying on search.twitter.com? I wanted to know if the home page will just be showing recent tweets as it does now. 2. What is the refresh rate if you will of popular tweets over a given time period? What does recent retweets mean because there are instances where that applies to minutes and others where the tweets generating the popularity are hours or even a day old? As in, when does one Tweet replace another tweet as a popular result for a given query. This seems to vary across different search queries with some being more stagnant than others. 3. Is there a drop-off point for the popular results for a given query after the numbers of retweets subside that the results are taken off or do they just stay there indefinitely until replaced? 4. Do you have a way of determining when irrelevant popular tweets have been maliciously set as the result for a given query and will they be actively taken off? Here are some examples. For the past twelve hours or so a search for #nowplaying has yielded the following: http://twitpic.com/1cokv3/full It almost seems as if the use of the popular tweet ranking in this case actually takes away from the real-time search experience by having dated tweets at the top of the queries. Once new results arise for the query, these tweets are gone which gives way to a real-time feed but initially these popular tweets are there and in this case none of the leading tweets that are popular actually have the utility expected from a user (i.e., users seem to use the #nowplaying search as a way to scroll through tweets like #nowplaying Clocks - Coldplay). It seems that for a query like this where users generally just scroll through the list of results as a way to discover new music or even other users and thus generally do not retweet individual tweets that often for the query, there is a level of stagnation where old tweets linger for hours as opposed to more active queries where individual tweets gain attention. Additionally, the popular search ranking in this case has no way or weeding out artificial results that are not query related. The top result from the image above is actually an advertisement being run by a company that contains a link leading to this: http://twitpic.com/1coml8/full A search for instances of the two most popular tweets using the text content of each one to show recent instances where they have been retweeted shows the following results: http://twitpic.com/1colcd/full http://twitpic.com/1com2o/full The most recent tweet of both the first and second most popular tweet is by the same account. Here's a look at that account, which seems to be set up for a very specific purpose. http://twitpic.com/1comde/full There's also this account which retweets the top #nowplaying query. The account is also clearly set up for a very specific purpose and is retweeting a tweet that does not give users the expected query result for a #nowplaying search. http://twitpic.com/1comgd/full This seems to show that the method of curating popular tweets may need to take into account the retweet versus the output rate for a given query otherwise the system can easily be taken advantage of to give users irrelevant results based on similar tactics. That is, for the #nowplaying search, even though thousands of tweets are being outputed by users, not many of them are being retweeted so all it takes is for someone to alter that dynamic as is the case here and because of the refresh rate for the query, irrelevant results can sit at the top for an extended period of time. But in cases where a twitter users with involved followers starts a discussion, the popular tweet ranking not only picks up on that effectively but it also allows new users to the conversation to have a reference point as is the case here (with the user's tweet being listed first and then legitimate popular tweets right after): http://twitpic.com/1coyhy/full And in cases where there is news or an event, it seems that retweeting of a legitimate news source for a query leads to an instance where a news source is immediately available as a result for the query. http://twitpic.com/1cp7sh/full In both of these examples, recent is truly recent as it happens almost instantaneously. However, these are still instances for even the more popular queries where using retweets over a given period of time as a measure
Re: [twitter-dev] Re: What tools do you use?
Working with QTwitLib in Qt on Windows. Developing desktop apps. Any one know whether there is a Qt lib for OAuth? Nigel. On 31 March 2010 16:59, Guille gui...@nianoniano.com wrote: Howdy! I script calls with PHP's Curl library and also user command-line (linux shell) curl command. I've seen some proxies mentioned. The one of my choice is: BurpProxy (@portswigger http://twitter.com/portswigger - http://portswigger.net/proxy/ ) I host my TwiPHPr library project at GitHub (@github http:// twitter.com/github - https://github.com/ ) I code using NetBeans (@netbeans http://twitter.com/netbeans - http://netbeans.org/ ) Whenever I do web applications I develop them using Symfony Framework (@symfony http://twitter.com/symfony - http://www.symfony-project.org/ ) On 30 ene, 21:55, Abraham Williams 4bra...@gmail.com wrote: Lets collect an awesome list of tools and applications we use to help develop with the Twitter API. I'll start the list with a couple that I use: Charles Proxy - @charlesproxy http://twitter.com/charlesproxy - http://www.charlesproxy.com/ Charles is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet. This includes requests, responses and the HTTP headers (which contain the cookies and caching information) Hurl - @hurlit http://twitter.com/hurlit -http://hurl.it/ Hurl makes HTTP requests. Enter a URL, set some headers, view the response, then share it with others. Perfect for demoing and debugging APIs. Hurl is also open source -http://defunkt.github.com/hurl/ TwitterOAuth PHP Library - @oauthlib http://twitter.com/oauthlib - http://github.com/abraham/twitteroauth The first PHP Library to support OAuth for Twitter's REST API. MIT licensed. GitHub - @github http://twitter.com/github -https://github.com/ GitHub is the easiest (and prettiest) way to participate in that collaboration: fork projects, send pull requests, monitor development, all with ease. What tools do you use while developing with the Twitter API? -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] How do I find if a user has protected his/her tweets?
In the user details data, there is a protected flag - true if protected. This is the place to find it. On 29 March 2010 12:40, Dushyant dushyantaror...@gmail.com wrote: Which method can I use to find this? To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Upcoming changes to the way status IDs are sequenced
How will this change affect the since Status_id type calls? I am working on a system that will depend on being able to download mentions once and only once, and was planning on using this function to ensure I got only what I wanted. Cheers, Nigel. On 26 March 2010 20:41, Taylor Singletary taylorsinglet...@twitter.comwrote: Hi Developers, It's no secret that Twitter is growing exponentially. The tweets keep coming with ever increasing velocity, thanks in large part to your great applications. Twitter has adapted to the increasing number of tweets in ways that have affected you in the past: We moved from 32 bit unsigned integers to 64-bit unsigned integers for status IDs some time ago. You all weathered that storm with ease. The tweetapoclypse was averted, and the tweets kept flowing. Now we're reaching the scalability limit of our current tweet ID generation scheme. Unlike the previous tweet ID migrations, the solution to the current issue is significantly different. However, in most cases the new approach we will take will not result in any noticeable differences to you the developer or your users. We are planning to replace our current sequential tweet ID generation routine with a simple, more scalable solution. IDs will still be 64-bit unsigned integers. However, this new solution is no longer guaranteed to generate sequential IDs. Instead IDs will be derived based on time: the most significant bits being sourced from a timestamp and the least significant bits will be effectively random. Please don't depend on the exact format of the ID. As our infrastructure needs evolve, we might need to tweak the generation algorithm again. If you've been trying to divine meaning from status IDs aside from their role as a primary key, you won't be able to anymore. Likewise for usage of IDs in mathematical operations -- for instance, subtracting two status IDs to determine the number of tweets in between will no longer be possible. For the majority of applications we think this scheme switch will be a non-event. Before implementing these changes, we'd like to know if your applications currently depend on the sequential nature of IDs. Do you depend on the density of the tweet sequence being constant? Are you trying to analyze the IDs as anything other than opaque, ordered identifiers? Aside for guaranteed sequential tweet ID ordering, what APIs can we provide you to accomplish your goals? Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] GUIDs?
If the since_id api calls will work against this, it might be a solution... On 26 March 2010 20:58, Donny V. don...@gmail.com wrote: Why don't you just use GUIDs as your id and then just add a timedate attribute stamp and call it a day. That would give you a unique id and also give your tweets an order. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Error 500 messages
I've had very slow responses to API calls today, but all seems to be working. On 26 March 2010 20:47, Cory cory.imdi...@gmail.com wrote: I think that was it, it's been much better now. I was worried because I'm in the middle of development and I thought I broke something! On Mar 25, 11:41 pm, John Kalucki j...@twitter.com wrote: Do these errors coincide with this incident? http://status.twitter.com/post/473971477/high-error-rate-and-page-loa... We threw a lot of 500s during this hour, and the 500s been slightly elevated from baseline since that issue was largely resolved. Ops is grinding down that error rate as I type. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Mar 25, 2010 at 8:42 PM, Cory cory.imdi...@gmail.com wrote: I'm getting a bunch of Error 500 messages from different API calls today - is anyone else experiencing this? It isn't every call, but it's a good 1/3 of them. Sometimes a call will succeed, sometimes it will fail. The method being called doesn't seem to make a difference. I'm using oAuth, not sure if that matters. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Upcoming changes to the way status IDs are sequenced
I hope you're right, but my app design depends on since_id, and before I proceed further I want to be sure that I will not have to rebuild when this new format comes in. On 26 March 2010 21:09, Ray Krueger raykrue...@gmail.com wrote: I would think that this would make no difference for since_id. The purpose of since_id is for us to the API give me the data I need that's happened since this id. Don't assume it's implemented as select * from tweets were id since_id. :) On Mar 26, 4:01 pm, Michael Bleigh mble...@gmail.com wrote: To those voicing concerns about since_id I believe the key word is that they will no longer be *sequential*, something entirely different from them no longer being *increasing*. Since ID is a core part of the Twitter API that I very much doubt will be in jeopardy from this change. Twitter devs feel free to back me up or refute me. :) On Mar 26, 4:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers, It's no secret that Twitter is growing exponentially. The tweets keep coming with ever increasing velocity, thanks in large part to your great applications. Twitter has adapted to the increasing number of tweets in ways that have affected you in the past: We moved from 32 bit unsigned integers to 64-bit unsigned integers for status IDs some time ago. You all weathered that storm with ease. The tweetapoclypse was averted, and the tweets kept flowing. Now we're reaching the scalability limit of our current tweet ID generation scheme. Unlike the previous tweet ID migrations, the solution to the current issue is significantly different. However, in most cases the new approach we will take will not result in any noticeable differences to you the developer or your users. We are planning to replace our current sequential tweet ID generation routine with a simple, more scalable solution. IDs will still be 64-bit unsigned integers. However, this new solution is no longer guaranteed to generate sequential IDs. Instead IDs will be derived based on time: the most significant bits being sourced from a timestamp and the least significant bits will be effectively random. Please don't depend on the exact format of the ID. As our infrastructure needs evolve, we might need to tweak the generation algorithm again. If you've been trying to divine meaning from status IDs aside from their role as a primary key, you won't be able to anymore. Likewise for usage of IDs in mathematical operations -- for instance, subtracting two status IDs to determine the number of tweets in between will no longer be possible. For the majority of applications we think this scheme switch will be a non-event. Before implementing these changes, we'd like to know if your applications currently depend on the sequential nature of IDs. Do you depend on the density of the tweet sequence being constant? Are you trying to analyze the IDs as anything other than opaque, ordered identifiers? Aside for guaranteed sequential tweet ID ordering, what APIs can we provide you to accomplish your goals? Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: JavaScript XAuth library ??????
I notice that the oath.net/code site does not mention any code for working with OAuth / XAuth in C++/Qt. Are there libraries available for this? Regards, Nigel. On 26 March 2010 19:18, tux_advocate_hpu tuxcod...@gmail.com wrote: from the OAuth.net page: http://oauth.net/code/ Scroll down and look for Javascript section. It links to this site: http://oauth.googlecode.com/svn/code/javascript/ I don't think this library sends the appropriate OAuth headers in the HTTP request. Or at least that isn't how I got it working. Instead, it sends all the appropriate stuff as HTTP request variables (either GET or POST, I cannot remember). It does perform the SHA1 stuff and makes the oauth_nonce and oauth_timestamp values for you. On Mar 26, 2:09 pm, mostafa farghaly keepon...@gmail.com wrote: Hi guys i can't wrap my head around OAuth/XAuth for browserless apps is there any JavaScript Library for easy working with XAuth To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: 403 on duplicate post - when?
And a whole load of other people! It's cut down the spam, and that can only be a good thing. On 24 March 2010 01:41, Tim Haines tmhai...@gmail.com wrote: Learnt something here. I knew you couldn't post the same tweet twice in a row. But Twitter is also blocking you from repeating a tweet you posted earlier in the day? So you can't Tweet: A B AThis one won't go through? If this is the case, how far back does it check for duplicates? Guy Kawasaki must hate this. :-) Tim. On Wed, Mar 24, 2010 at 5:28 AM, Mark McBride mmcbr...@twitter.comwrote: Yes, that's a hole in the current logic. I'll work on getting the N-n case handled. ---Mark http://twitter.com/mccv On Tue, Mar 23, 2010 at 6:12 AM, Dewald Pretorius dpr...@gmail.comwrote: Mark, Here is what appears to happen. When you try and duplicate the newest tweet (N), you get the expected new behavior with a 403 and Status is a duplicate. When you try and duplicate tweet N-1, you get the old behavior with 200 OK and the details of tweet N. I have not tested tweet N-2, N-3, etc. On Mar 22, 6:27 pm, Mark McBride mmcbr...@twitter.com wrote: I just tried it and got a 403. Can you give me a screen name you're using, the data posted, and the data returned? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius dpr...@gmail.com wrote: Yes, I just tried it again. URL:https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Most popular tweets in the search API
Agreed - default sould be recentness, popularity - however it is defined -
and we could go into a long sidetrack on that which has nothing to do with
the api, apart from to just say that different people will have different
ideas of how to take the data that comes with a tweet and use ti to
calculate the tweet's popularity - should be something that we, the
developer community, insert following requests from our users, not something
one size fits all handed down from twitter.
I think twitter is fantastic, but sometimes they make a bad decision. This
is one of them.
On 20 March 2010 01:33, S Wang shuanw...@gmail.com wrote:
As someone who's developing some applications right now specifically
involving the search APIs I now have to worry about whether or not I
should pre-emptively include the result_type parameter so my app
doesn't become non-functioning when the changes are pushed to the
site. Why do the popular tweets have to be the default behavior in the
API?
On Mar 19, 7:42 am, funkatron funkat...@gmail.com wrote:
So this would change the default behavior of the search API, which is
currently to return recent results?
If so, I think that's a bad idea. Better to offer the option than to
change existing behavior when possible.
--
Ed Finklerhttp://funkatron.com
Twitter:@funkatron
AIM: funka7ron
ICQ: 3922133
XMPP:funkat...@gmail.com xmpp%3afunkat...@gmail.com
On Mar 19, 10:37 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Developers!
The Search team is working on a beta project that returns the most
popular
tweets for a query, rather than only the most recent tweets. This is a
beta
project, but an important first step to surface the most popular tweets
for
users searching Twitter.
You can expect many improvements as we tune and tweak our algorithms,
but we
want to give everyone a heads up so we can go over the implications for
those consuming the search API.
--- New attribute in the payload ---
First of all there will be a new attribute in search result payloads.
Since
some tweets are popular for a given query while others are simply the
most
recent results that match the query, we are adding a metadata section
to
specify the type of result that a given result represents.
So for a popular tweet the result_type in the metadata section will
have
the value popular.
Example of a result with a popular tweet:
{
results:
[
{
profile_image_url:
http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon,15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
id:9153622261,
from_user_id:106309,
geo:null,
iso_language_code:en,
source:lt;a href=quot;http://www.atebits.com/;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: popular
}
}
/* etc ... */
}
Results that are not popular and represent simply recent query matches
will
have the result_type in the metadata section with a value of
recent.
Example of a recent result:
{
results:
[
{
profile_image_url:
http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg;,
created_at:Mon, 15 Feb 2010 23:42:45 +,
from_user:timhaines,
to_user_id:97776,
text:@noradio Nice spot.,
id:9160218997,
from_user_id:159881,
to_user:noradio,
geo:null,
iso_language_code:it,
source:lt;a href=quot;http://www.atebits.com/;
rel=quot;nofollowquot;gt;Tweetielt;/agt;,
metadata:
{
result_type: recent
}
},
/* etc ... */
}
--- Results with popular tweets aren't ordered chronologically ---
Until the popular tweet feature all search results have been sorted
chronologically, most recent results at the top. If a search query has
any
popular results, those will be returned at the top, even if they are
older
than the other results.
Example of a non-chronologically ordered set of results including
popular
results:
{
results:
[
{
profile_image_url:
http://a1.twimg.com/profile_images/668144840/Elizabeth_Web_normal.jpg;,
created_at:Mon, 15 Feb 2010 19:55:18 +,
from_user:Elizabeth,
to_user_id:null,
text:It's the Griswold family trip to Joshua Tree Park!
@rsarver @Devon @Jess @noradio @kevinweil,
Re: [twitter-dev] massive #fail - auto profile popups
I actually quite like them, though I use tweetdeck most of the time. On 19 March 2010 06:26, neal rauhauser nrauhau...@gmail.com wrote: The automated profile popups are a profound source of #fail. Anyone using an Atom based machine is basically twiddling their thumbs for 30% of the time they're trying to use the web interface. Chrome users already had this feature with the bit.ly expander and it did much, much more. There really needs to be a No Silly Automated Profile Popup [ ] check box available in account config. If this had been the Twitter interface when I started I'd have 5 followers, 10 tweets, and I'd have been idle for 600+ days. -- mailto:n...@layer3arts.com // GoogleTalk: nrauhau...@gmail.com GV: 202-642-1717 To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Twitter Project using the API (Paid)
Please let me know where this site is so I don't even consider going there. This is just spamming, surely? On 19 March 2010 17:01, TheN2S thenext2sh...@gmail.com wrote: John, Thanks for pointing that out! I will have a chat with my team and see how we can avoid this conflict. We do have another simple project that we want to get off its feet! Lets say we premiere an exclusive new song on our site. However to get to the song, users must login through twitter/facebook. While they login they are automatically set to follow @ouraccount and it automatically posts a status update on their account Currently checking out the brand new song for Sinatra! http://link.com;. Once that is done, the user is forwarded to the appropriate page that they originally intended to. If they don't sign in, they miss out on the release. This doesnt seem to be going against any terms of service... right? Once again, contact us if you are able to complete this project: http://bit.ly/9CSUc0 (all css/html is handled by us. We simply need the motor to power up the project. We take care of all the aesthetics.) On Mar 19, 9:27 am, John Kalucki j...@twitter.com wrote: This sounds a lot like @reply spam: http://help.twitter.com/forums/10711/entries/64986 If you are replying to followers, maybe that's OK, and maybe it isn't. But, if you are @replying to everyone, you will be suspended. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Mar 18, 2010 at 8:26 PM, TheN2S thenext2sh...@gmail.com wrote: I am looking for a twitter developer that is able to use the API to respond back to tweets containing a specific quote. Lets say for example an artist YXZ has just done a rendition of New York by Frank Sinatra. We want to @reply every user that mentions York Sinatra in their tweet with a customized reply such as I see you like Sinatra's original New York song.. but have you checked out ZYX's new version? It's a simple concept, and it has been done already. Please also be aware that twitter has an API limit that we don't want to disturb. We are in need of a developer to move this project forward. Please contact us back using this form:http://bit.ly/9CSUc0 Thanks! (= To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: Introduce yourself!
I'll follow Quy's lead. I have been providing social media training / support to companies for the last year, earlier this year I identified a number of services/features that desktop clients should have, and have today successfully used my client, developed in C++ with QTwitlib, to read from and post to Twitter. After some further development, the client will be released (Windows only till someone provides me Mac Linux machines) as open-source. I've been following the discussion here for a couple of weeks, it has helped me understand the API better. Cheers all, Nigel. On 19 March 2010 18:19, Quy quyten...@gmail.com wrote: My name is Quy Le (@quytennis) and I used to be a software engineer but now I'm product manager at a high-tech company. I've been using the Twitter API for the past 3 months on a Twitter project that hopefully will go live in a few weeks. I've been using PHP/mySQL/ memcached to build my site but it has been a slow process since I have a day job and I'm relearning some of the new technology since I haven't touched a piece of code in over 8-9 years. (Designing for IE6 sucks). The feature I would love the most is a conversation API so it's easy to show conversations based on a tweet. Quy On Feb 19, 1:20 pm, Abraham Williams 4bra...@gmail.com wrote: We have not had an introductions thread in a long time (or ever that I could find) so I'm starting one. Don't forget to add an answer to the tools thread [1](Gmail link [2]) as well. I'm Abraham Williams, I've been working with the Twitter API and this group since early 2008. I do mostly freelance Drupal and Twitter API integration and personal projects. I love seeing the creative projects developers build or integrate with the API and look forward to meeting many of you at Chirp. TwitterOAuth [3] the first PHP library to support OAuth is built and maintained by me, and will hopefully see a new release soon. I also built a fun Chrome extension [4] that integrates common friends and followers into Twitter profiles. The feature I would most like added to the API is a conversation method to get replies to a specific status. So. Who are you, what do you do, what have you built, and what feature do you most want to see added? @Abraham [1] http://groups.google.com/group/twitter-development-talk/browse_thread... [2]https://mail.google.com/mail/#inbox/12680cd0fa59011e [3] https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogo... [4]http://code.google.com/p/twitter-api/issues/detail?id=142 -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
