[twitter-dev] Inconsistent Accuracy of Phrase Searches
Hi all, I'm hacking on an app that relies heavily on phrase searching, and have gotten very inconsistent results. Most search queries with phrases work as advertised. See: http://search.twitter.com/search?q=&ands=&phrase=%222day+let%27s+dream+with+our+eyes+wide+open!%22&ors=¬s=&tag=&lang=all&from=&to=&ref=&near=&within=15&units=mi&since=&until=&rpp=10 or http://search.twitter.com/search?q=&ands=&phrase="2day+let's+dream+with+our+eyes+wide+open!"&ors=¬s=&tag=&lang=all&from=&to=&ref=&near=&within=15&units=mi&since=&until=&rpp=10 Others, however, seem to ignore the fact that I'm looking for a phrase. See: http://search.twitter.com/search?q=%22rabble%2C+rabble%2C+rabble%2C+rabble.%22 or http://search.twitter.com/search?q=%22i+need+new+socks!%22 I thought perhaps there is a minimum length or word requirement for a phrase, but some very short ones seem to work just fine. See: http://search.twitter.com/search?q=%22it%27s+happy+hour%22 Has anybody run into this? Any workarounds (besides further processing the text from the calling application)? Cheers, Robby -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: @anywhere Drupal and WordPress Plugins?
Nice! I made a stand-alone version for people who prefer the barebones approach. Not approved at Wordpress.org yet but it's up at github: http://github.com/freerobby/at-anywhere-for-Wordpress --Robby On Apr 16, 7:21 pm, Shannon Whitley wrote: > I've updated Twit Connect for WordPress to include @anywhere. It adds > hovercards, follow buttons, and tweetboxes. I really like the tweetbox on > the WordPress comment form. > > http://wordpress.org/extend/plugins/twitconnect > > On Fri, Apr 16, 2010 at 3:11 PM, Pelechati wrote: > > You can visithttp://apture.com/pluginfor a wordpress/drupal plugin > > for @anywhere functionality. Apture has been serving up @anywhere > > behavior for over a year in a single line of javascript. > > > On Apr 16, 2:45 pm, Robby Grossman wrote: > > > A Wordpress plugin makes a lot of sense, as it would let non- > > > developers easily integrate with it. I was going to look over the docs > > > this weekend to see what would be involved in writing a generic > > > @anywhere plugin for hosted Wordpress installs. > > > > --Robby > > > > On Apr 16, 2:09 am, "M. Edward (Ed) Borasky" wrote: > > > > > Are there any plugins for @anywhere that will run on Drupal and > > > > WordPress? My blog is on WordPress, and I want to get rid of as many > > > > non-Twitter gizmos and widgets as possible. I'll be keeping AddToAny, > > > > since it goes to Developer Zone, and I'll be keeping Twitoaster, since > > > > it threads conversations. But I'm ditching Topsy and a couple of > > > > others as soon as I can get @anywhere running. > > > > > I don't know the details of the Drupal site yet - I need to meet with > > > > them and see if they want to do @anywhere. P.S.: If you blog for > > > > developers, I highly recommend posting to Developer Zone. I get more > > > > traffic to my blog that way than anywhere else. I've had 800-visitor > > > > days just from them. > > > > > -- > > > > Subscription settings: > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en > >
[twitter-dev] Re: @anywhere Drupal and WordPress Plugins?
A Wordpress plugin makes a lot of sense, as it would let non- developers easily integrate with it. I was going to look over the docs this weekend to see what would be involved in writing a generic @anywhere plugin for hosted Wordpress installs. --Robby On Apr 16, 2:09 am, "M. Edward (Ed) Borasky" wrote: > Are there any plugins for @anywhere that will run on Drupal and > WordPress? My blog is on WordPress, and I want to get rid of as many > non-Twitter gizmos and widgets as possible. I'll be keeping AddToAny, > since it goes to Developer Zone, and I'll be keeping Twitoaster, since > it threads conversations. But I'm ditching Topsy and a couple of > others as soon as I can get @anywhere running. > > I don't know the details of the Drupal site yet - I need to meet with > them and see if they want to do @anywhere. P.S.: If you blog for > developers, I highly recommend posting to Developer Zone. I get more > traffic to my blog that way than anywhere else. I've had 800-visitor > days just from them. > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Early look at Annotations
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 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 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 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
[twitter-dev] Re: dev.twitter.com
Why in peace? :P +1 on the positive sentiments. Looks great! --Robby On Apr 14, 3:16 pm, Josh Roesslein wrote: > Very nice! RIP apiwiki. > > Josh -- To unsubscribe, reply using "remove me" as the subject.
[twitter-dev] Re: Some thoughts leading up to Chirp
Tweetie 2 for Mac is still alive, folks! http://www.macheist.com/forums/viewtopic.php?pid=370710#p370710 --Robby On Apr 12, 7:33 am, Michael Macasek wrote: > Ryan, > > Great post. Thank you for taking the time to clarify some of Twitters > recent actions and future direction. Hopefully this thread will not > get derailed... > > Looking forward to seeing you and all the Twitter folks in a few days > to continue the discussion. And maybe at the oneforty PreChip > party? :) > > RE Mike's comment... Yea what's the deal with Tweetie for Mac man? I > need my Tweetie fix. ;) > > M > > On Apr 11, 8:22 pm, Ryan Sarver wrote: > > > I wanted to email everyone and share my thoughts on the acquisition > > from Friday, the communication around it and where we are going from > > here. We're incredibly excited about Chirp, and I think an open > > dialogue going into it is important. I look forward to meeting many of > > you there and continuing the discussion. > > > We love the Twitter ecosystem and work hard every day to help support > > you and make the platform you are building on as successful as it can > > be for everyone involved. We love the variety that developers have > > built around the Twitter experience and it's a big part of the success > > we've seen. However when we dug in a little bit we realized that it > > was causing massive confusion among user's who had an iPhone and were > > looking to use Twitter for the first time. They would head to the App > > Store, search for Twitter and would see results that included a lot of > > apps that had nothing to do with Twitter and a few that did, but a new > > user wouldn't find what they were looking for and give up. That is a > > lost user for all of us. This means that we were missing out an > > opportunity to grow the userbase which is beneficial for the health of > > the entire ecosystem. Focus on growing and serving the userbase is > > beneficial to everyone in the ecosystem and more opportunities become > > available with a larger audience. We believe strongly that the > > ecosystem is critical to our success and this move doesn't change > > that. We have analytics that show our most engaged users are ones that > > use SMS, twitter.com AND a 3rd-party application. It further proves > > that there are different audiences and needs that we can never meet on > > our own and we all need to work together to provide what is best for > > the users. Once I understood the long-term view I strongly believed it > > was not only the right thing to do for users, but the right thing to > > do for the ecosystem as a whole. > > > To be clear, we are going to work hard to improve our product, add new > > functionality, make acquisitions when it's in the best interest of > > users and the whole ecosystem at large. Each one of those things has > > the potential to upset a company or developer that may have been > > building in that space and they then have to look for new ways to > > create value for users. My promise is that we will be consistent in > > always focusing on what's best for the user and the ecosystem as a > > whole and we will be sincere and honest in our communication with you. > > To the point that we can, we will try to give more certainty about the > > areas where we think we can maximize benefit to users. We will > > continue to focus on what is best for users and we will work together > > to make sure that we are creating more opportunities for the ecosystem > > on the whole. We will also admit our mistakes when they are made and > > the Blackberry client should never have been labeled "official". It > > has since been changed and you won't see that language used with > > Twitter clients in the future. > > > This week will hopefully show that we are focused on building a > > platform that no longer just mirrors twitter.com functionality, but > > offers you raw utility that provides much greater opportunities to > > innovate and build durable, valuable businesses. I also want this week > > to be an opportunity for us to get together and discuss the future of > > the platform and how we can improve our communication, responsiveness > > and clarity. We have an open office hours at 10:15am on Thursday at > > the Hack Day and I invite all of you to come by for a discussion to > > talk about the future of the platform and help us craft a working > > relationship that is beneficial for both of us. I will provide a free > > ticket to anyone from this list that is unable to afford the current > > price so that they can be part of that discussion. Just email me > > directly. For those of you who can't make it to Chirp, it will be live > > streamed so you can tune in from home -- where ever home might be. > > > As always, you can reach me by email or by phone, 617 763 9904. I am > > here to listen and provide clarity when possible and you should know > > we are committed to working with you on this. > > > Best, Ryan > > -- To unsubscribe, reply using "remove m
[twitter-dev] Re: Some thoughts leading up to Chirp
Thanks for the post, Ryan. Looking forward to hearing more of both perspectives later this week. --Robby On Apr 11, 8:22 pm, Ryan Sarver wrote: > I wanted to email everyone and share my thoughts on the acquisition > from Friday, the communication around it and where we are going from > here. We're incredibly excited about Chirp, and I think an open > dialogue going into it is important. I look forward to meeting many of > you there and continuing the discussion. > > We love the Twitter ecosystem and work hard every day to help support > you and make the platform you are building on as successful as it can > be for everyone involved. We love the variety that developers have > built around the Twitter experience and it's a big part of the success > we've seen. However when we dug in a little bit we realized that it > was causing massive confusion among user's who had an iPhone and were > looking to use Twitter for the first time. They would head to the App > Store, search for Twitter and would see results that included a lot of > apps that had nothing to do with Twitter and a few that did, but a new > user wouldn't find what they were looking for and give up. That is a > lost user for all of us. This means that we were missing out an > opportunity to grow the userbase which is beneficial for the health of > the entire ecosystem. Focus on growing and serving the userbase is > beneficial to everyone in the ecosystem and more opportunities become > available with a larger audience. We believe strongly that the > ecosystem is critical to our success and this move doesn't change > that. We have analytics that show our most engaged users are ones that > use SMS, twitter.com AND a 3rd-party application. It further proves > that there are different audiences and needs that we can never meet on > our own and we all need to work together to provide what is best for > the users. Once I understood the long-term view I strongly believed it > was not only the right thing to do for users, but the right thing to > do for the ecosystem as a whole. > > To be clear, we are going to work hard to improve our product, add new > functionality, make acquisitions when it's in the best interest of > users and the whole ecosystem at large. Each one of those things has > the potential to upset a company or developer that may have been > building in that space and they then have to look for new ways to > create value for users. My promise is that we will be consistent in > always focusing on what's best for the user and the ecosystem as a > whole and we will be sincere and honest in our communication with you. > To the point that we can, we will try to give more certainty about the > areas where we think we can maximize benefit to users. We will > continue to focus on what is best for users and we will work together > to make sure that we are creating more opportunities for the ecosystem > on the whole. We will also admit our mistakes when they are made and > the Blackberry client should never have been labeled "official". It > has since been changed and you won't see that language used with > Twitter clients in the future. > > This week will hopefully show that we are focused on building a > platform that no longer just mirrors twitter.com functionality, but > offers you raw utility that provides much greater opportunities to > innovate and build durable, valuable businesses. I also want this week > to be an opportunity for us to get together and discuss the future of > the platform and how we can improve our communication, responsiveness > and clarity. We have an open office hours at 10:15am on Thursday at > the Hack Day and I invite all of you to come by for a discussion to > talk about the future of the platform and help us craft a working > relationship that is beneficial for both of us. I will provide a free > ticket to anyone from this list that is unable to afford the current > price so that they can be part of that discussion. Just email me > directly. For those of you who can't make it to Chirp, it will be live > streamed so you can tune in from home -- where ever home might be. > > As always, you can reach me by email or by phone, 617 763 9904. I am > here to listen and provide clarity when possible and you should know > we are committed to working with you on this. > > Best, Ryan -- To unsubscribe, reply using "remove me" as the subject.
[twitter-dev] Re: About the oneforty application directory
Hi folks, This is Robby from oneforty. We wanted to take a moment to address the issues that you all have raised surrounding our use of Twitter OAuth. oneforty requests read/write access to your Twitter account. At present, read access is used to examine the source tag of your tweets, so that we can identify which applications you are using. This allows us to automate filling in the "My Apps" section of your profile. If your tweets are public, we can do it without read access, but only in limited number because we need to authenticate in order to get past the Twitter API limits. As for write access, we're hoping to add features along the lines of "Tweet about this app" or "DM the app developer." By requesting read/write access, we can provide a much better user experience for handling these features than we could otherwise, as the alternative would be a nonnative mechanism involving popup windows or new browser tabs on twitter.com. We will never, under any circumstances, post to your twitter account without your consent. Any publishing to your tweet stream, sending of DMs, etc. will be the result of an explicit action on your part. It will never be done automatically. It will always be opt-in rather than opt-out. We are in the process of updating our site copy to reflect all of this, but wanted to pass along our intentions to this group sooner rather than later. As always if you have any questions or concerns we are always available at develop...@oneforty.com. Best, Robby (on behalf of @graysky, @macasek and myself)
