Re: [twitter-dev] Re: Most popular tweets in the search API
> I wanted to give a head's up that while the "top tweets" feature will > be *opt-in* at rollout, What was the eventual decision on keeping sorted-by-time the default for Search API results? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Queen, you shall be it if you wish/Look for your king -- Pink Floyd -- To unsubscribe, reply using "remove me" as the subject.
Re: [twitter-dev] Re: Most popular tweets in the search API
Has there been any consideration to including popular flag in the REST API
as well?
Abraham
On Tue, Mar 30, 2010 at 16:14, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:
> Hi all,
>
> This will be rolling out either later this week or early next. I'll be
> providing you with more details as the release approaches.
>
> I wanted to give a head's up that while the "top tweets" feature will be
> *opt-in
> *at rollout, the addition of the new fields to the XML and JSON returns of
> the search API are going to be rolled out globally for all API-based search
> results.
>
> If you have a fragile implementation that relies on only specific fields
> being present in the JSON or XML returns, or a specific ordering of fields,
> you'll likely want to move on to a more robust implementation. I'll be
> providing more details on the formats of these fields in a forthcoming post.
>
> In JSON, the new parent field will be called "metadata" and in turn will
> contain more key value pairs, like the new result_type field already
> discussed.
>"metadata": { "result_type": "recent" }
>
> In XML, the parent node for these new fields will be located within
> twitter:metadata :
>
> popular
>
>
> We're really excited about this release. More details soon!
>
> Taylor Singletary
> Developer Advocate, Twitter
> http://twitter.com/episod
>
>
> On Tue, Mar 30, 2010 at 3:46 PM, @dbbradle wrote:
> >
> > Can you provide us with a time line for when this is going to be
> > rolled out?
> >
> > On Mar 19, 10:09 am, Taylor Singletary
> > wrote:
> > > Your questions so far have been great and we're listening.
> > >
> > > I wanted to let everyone know that when we do roll this out, it will be
> such
> > > that developers will "opt-in" to receiving Top Tweets in their results
> for
> > > the first month or so of the feature rollout. After the trial
> transition
> > > period is complete, we'll enable this feature by default. You will have
> time
> > > to adjust.
> > >
> > > Taylor Singletary
> > > Developer Advocate, Twitterhttp://twitter.com/episod
> > >
> > > On Fri, Mar 19, 2010 at 9:44 AM, Nick Arnett
> wrote:
> > >
> > > > On Fri, Mar 19, 2010 at 7: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,
> > >
> > > > What is the definition of "popular?"
> > >
> > > > Nick
> > >
> > > > 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, reply using "remove me" as the subject.
>
>
--
Abraham Williams | Community Advocate | http://abrah.am
Digri | Your network just got hotter | http://digri.net
This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Re: Most popular tweets in the search API
Hi all,
This will be rolling out either later this week or early next. I'll be
providing you with more details as the release approaches.
I wanted to give a head's up that while the "top tweets" feature will
be *opt-in
*at rollout, the addition of the new fields to the XML and JSON returns of
the search API are going to be rolled out globally for all API-based search
results.
If you have a fragile implementation that relies on only specific fields
being present in the JSON or XML returns, or a specific ordering of fields,
you'll likely want to move on to a more robust implementation. I'll be
providing more details on the formats of these fields in a forthcoming post.
In JSON, the new parent field will be called "metadata" and in turn will
contain more key value pairs, like the new result_type field already
discussed.
"metadata": { "result_type": "recent" }
In XML, the parent node for these new fields will be located within
twitter:metadata :
popular
We're really excited about this release. More details soon!
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Tue, Mar 30, 2010 at 3:46 PM, @dbbradle wrote:
>
> Can you provide us with a time line for when this is going to be
> rolled out?
>
> On Mar 19, 10:09 am, Taylor Singletary
> wrote:
> > Your questions so far have been great and we're listening.
> >
> > I wanted to let everyone know that when we do roll this out, it will be
such
> > that developers will "opt-in" to receiving Top Tweets in their results
for
> > the first month or so of the feature rollout. After the trial transition
> > period is complete, we'll enable this feature by default. You will have
time
> > to adjust.
> >
> > Taylor Singletary
> > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > On Fri, Mar 19, 2010 at 9:44 AM, Nick Arnett
wrote:
> >
> > > On Fri, Mar 19, 2010 at 7: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,
> >
> > > What is the definition of "popular?"
> >
> > > Nick
> >
> > > 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, reply using "remove me" as the subject.
[twitter-dev] Re: Most popular tweets in the search API
Can you provide us with a time line for when this is going to be rolled out? On Mar 19, 10:09 am, Taylor Singletary wrote: > Your questions so far have been great and we're listening. > > I wanted to let everyone know that when we do roll this out, it will be such > that developers will "opt-in" to receiving Top Tweets in their results for > the first month or so of the feature rollout. After the trial transition > period is complete, we'll enable this feature by default. You will have time > to adjust. > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > On Fri, Mar 19, 2010 at 9:44 AM, Nick Arnett wrote: > > > On Fri, Mar 19, 2010 at 7: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, > > > What is the definition of "popular?" > > > Nick > > > 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, reply using "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 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 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
> >
> > On Mar 19, 10:37 am, Taylor Singletary
> > 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":" > > rel="nofollow">Tweetie",
> > > "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":" > > rel="nofollow">Tweetie",
> > > "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_image
[twitter-dev] Re: Most popular tweets in the search API
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 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
>
> On Mar 19, 10:37 am, Taylor Singletary
> 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":" > rel="nofollow">Tweetie",
> > "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":" > rel="nofollow">Tweetie",
> > "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",
> > "id":9153622261,
> > "from_user_id":106309,
> > "geo":null,
> > "iso_language_code":"en",
> > "source":" > rel="nofollow">Tweetie",
> > "metadata":
> > {
> > "result_type": "popular"
> > }
> > },
> > {
> >
> > "profile_image_url":"http://a3.twimg.com/profile_images/641350353/TimCheekFinger_normal.jpg";,
> > "created_at":"Mon, 15 Feb 2010 23:42:45 +",
> > "f
[twitter-dev] Re: Most popular tweets in the search API
+1 for asking for keeping the default as it is right now (should be clear really strange to even discuss 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.
[twitter-dev] Re: Most popular tweets in the search API
+1 to Cameron and funkatron. Making this default, even with a transition period, would be extremely bad practice. The whole point of API versioning is such that old stuff does not break. And yes, changing behavior so that results returned to same query are suddenly different is definitely "breaking." I find popular tweets in search results mixed with recents to be a great idea, but it cannot be the default, since it would break many apps that have relied on current behavior. And having whatever transition period is not good enough. You are forcing developers to change priorities and re-test old stuff, some of which may be unmaintained legacy. API versioning and backwards compatibility are standard industry practices, just please stick to those and don't piss off developers any further. (I could insert a more elaborate rant here to show what I really feel, but the above captures the point.) rgds, Jaanus On Mar 19, 3:29 pm, Cameron Kaiser wrote: > > Your definition of "time to adjust" may not be ours. Twitter has, to > > be honest, a fairly crappy reputation for changing API behavior. While > > some of that was surely driven by performance concerns, I don't see > > how this could be. This doesn't help the rep. > > > Please, do not enable this by default, *ever*. Don't change behavior > > unless it is necessary. Add a new API method, or make recent results > > the default and keep it that way. > > > If you're advocating for developers, advocate for making us do less > > work to maintain current functionality, please. > > This is spot on. It's not that I think the idea itself is bad -- I'm all > for more relevant search results *when relevance is what's requested*. Right > now, every app that queries the Search API expects time-oriented results > because that's what we got before. Making this the new default is needless > dev chaos, *and* I haven't heard if there is even a way to opt back to the > old behaviour if this becomes the ill-advised default anyway. > > I'd love to support this feature, in the appropriate context, when it makes > sense to do so. I don't want to have to code around it as the new, > unsolicited default when it doesn't. > > -- > personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com > -- FORTUNE: Good day for romance, but try a single person this time. > -- 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
As a developer, I've got my foot in (at least) two communities:
Twitter developers and on-line marketing practitioners. Given that, I
think this discussion needs to happen in a larger forum than the
Twitter Developers' Google Group. I've put up a blog post and created
a hashtag (#tweetsearchpop), and I'd like to invite you all to
participate that way - I'm prepared to man the comment monitoring
dashboard ;-)
http://borasky-research.net/2010/03/19/seeker-or-seller-what-do-you-think-about-adding-popularity-to-twitter-search-tweetsearchpop/
--
M. Edward (Ed) Borasky
borasky-research.net/m-edward-ed-borasky/
"A mathematician is a device for turning coffee into theorems." ~ Paul Erdos
Quoting Dewald Pretorius :
Taylor,
In terms of this change, you need to separate Twitter Search from the
Twitter Search API in your minds.
Do with Twitter Search (the web interface) what you like. Make popular
the default if you want.
But, don't decide on behalf of the developers (the consumers of the
Twitter Search API) that popular is the default that we want. In most
cases it probably isn't. In my case it definitely isn't, otherwise I
would have asked for something like that a long time ago.
In other words, don't force something down our throats just because
you think it's a cool idea.
Leave the default as is. Make "popular" an option that we can use if
we want to. That's good developer service, because it doesn't create
additional work for us if we want to remain with the status quo, and
it gives us additional options if we want to use them.
On Mar 19, 2:39 pm, Taylor Singletary
wrote:
Even further clarifications:
Top Tweets are coming to make search results even more relevant. We'll be
tuning our ranking algorithms with gusto. Some people will naturally resist
these changes. Approach with a zen mind.
When we launch this new feature for the API, it will be opt-in for a
transitory period, but the search.twitter.com site will come with these
results already baked in. Before implementing in your own applications,
you'll be able to see the top results for your favorite queries your self.
The Search team is always working on ways of making results more
relevant. We recognize that not everyone wants search results with
algorithmic ranking of tweets, but we like what we've come up with and we
think you'll like it too.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Fri, Mar 19, 2010 at 10:11 AM, davidzimm wrote:
> Bad idea.
> 1) reduces the credibility and thereby the value of the results in
> twitter search
> 2) who determines which is popular- no matter how you try to calculate
> this, someone will figure it out and spam the results.
> 3) people are used to searching twitter for breaking news, rather than
> "authoritative" results. You'll have to change user expectations.
> 4) perhaps this can be an "advanced" setting, rather than a default
> practice.
> On Mar 19, 10:37 am, Taylor Singletary
> 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":"http://www.atebits.com/";
> > rel="nofollow">Tweetie",
> > "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:
> > {
>
[twitter-dev] Re: Most popular tweets in the search API
Taylor,
In terms of this change, you need to separate Twitter Search from the
Twitter Search API in your minds.
Do with Twitter Search (the web interface) what you like. Make popular
the default if you want.
But, don't decide on behalf of the developers (the consumers of the
Twitter Search API) that popular is the default that we want. In most
cases it probably isn't. In my case it definitely isn't, otherwise I
would have asked for something like that a long time ago.
In other words, don't force something down our throats just because
you think it's a cool idea.
Leave the default as is. Make "popular" an option that we can use if
we want to. That's good developer service, because it doesn't create
additional work for us if we want to remain with the status quo, and
it gives us additional options if we want to use them.
On Mar 19, 2:39 pm, Taylor Singletary
wrote:
> Even further clarifications:
>
> Top Tweets are coming to make search results even more relevant. We'll be
> tuning our ranking algorithms with gusto. Some people will naturally resist
> these changes. Approach with a zen mind.
>
> When we launch this new feature for the API, it will be opt-in for a
> transitory period, but the search.twitter.com site will come with these
> results already baked in. Before implementing in your own applications,
> you'll be able to see the top results for your favorite queries your self.
>
> The Search team is always working on ways of making results more
> relevant. We recognize that not everyone wants search results with
> algorithmic ranking of tweets, but we like what we've come up with and we
> think you'll like it too.
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Fri, Mar 19, 2010 at 10:11 AM, davidzimm wrote:
> > Bad idea.
>
> > 1) reduces the credibility and thereby the value of the results in
> > twitter search
> > 2) who determines which is popular- no matter how you try to calculate
> > this, someone will figure it out and spam the results.
> > 3) people are used to searching twitter for breaking news, rather than
> > "authoritative" results. You'll have to change user expectations.
> > 4) perhaps this can be an "advanced" setting, rather than a default
> > practice.
>
> > On Mar 19, 10:37 am, Taylor Singletary
> > 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":"http://www.atebits.com/";
> > > rel="nofollow">Tweetie",
> > > "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",
> > >
Re: [twitter-dev] Re: Most popular tweets in the search API
> Your definition of "time to adjust" may not be ours. Twitter has, to > be honest, a fairly crappy reputation for changing API behavior. While > some of that was surely driven by performance concerns, I don't see > how this could be. This doesn't help the rep. > > Please, do not enable this by default, *ever*. Don't change behavior > unless it is necessary. Add a new API method, or make recent results > the default and keep it that way. > > If you're advocating for developers, advocate for making us do less > work to maintain current functionality, please. This is spot on. It's not that I think the idea itself is bad -- I'm all for more relevant search results *when relevance is what's requested*. Right now, every app that queries the Search API expects time-oriented results because that's what we got before. Making this the new default is needless dev chaos, *and* I haven't heard if there is even a way to opt back to the old behaviour if this becomes the ill-advised default anyway. I'd love to support this feature, in the appropriate context, when it makes sense to do so. I don't want to have to code around it as the new, unsolicited default when it doesn't. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- FORTUNE: Good day for romance, but try a single person this time. -- 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.
[twitter-dev] Re: Most popular tweets in the search API
Your definition of "time to adjust" may not be ours. Twitter has, to be honest, a fairly crappy reputation for changing API behavior. While some of that was surely driven by performance concerns, I don't see how this could be. This doesn't help the rep. Please, do not enable this by default, *ever*. Don't change behavior unless it is necessary. Add a new API method, or make recent results the default and keep it that way. If you're advocating for developers, advocate for making us do less work to maintain current functionality, please. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On Mar 19, 1:09 pm, Taylor Singletary wrote: > Your questions so far have been great and we're listening. > > I wanted to let everyone know that when we do roll this out, it will be such > that developers will "opt-in" to receiving Top Tweets in their results for > the first month or so of the feature rollout. After the trial transition > period is complete, we'll enable this feature by default. You will have time > to adjust. > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Fri, Mar 19, 2010 at 9:44 AM, Nick Arnett wrote: > > > On Fri, Mar 19, 2010 at 7: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, > > > What is the definition of "popular?" > > > Nick > > > 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.
[twitter-dev] Re: Most popular tweets in the search API
I'm also curious to understand how 'popular' tweets will be determined. Once a tweet is considered to be popular for search purposes, might it be cached for an extended period of time so that it will return for queries beyond the currently limited period? -- Richard Nevins Twitter: @hornOKplease 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.
[twitter-dev] Re: Most popular tweets in the search API
I'm assuming "popular" is based on retweet count? I'd suggest that if result_type is not given in the request that the search performs as it has been. If you want just popular, you'd use popular as you've suggested or recent for non popular. If you wanted a mix, ordered as you are suggesting, then add the value "all" for the result_type. That would be much more of an extension/feature rather than a refactor. On Mar 19, 10:09 am, Taylor Singletary wrote: > Your questions so far have been great and we're listening. > > I wanted to let everyone know that when we do roll this out, it will be such > that developers will "opt-in" to receiving Top Tweets in their results for > the first month or so of the feature rollout. After the trial transition > period is complete, we'll enable this feature by default. You will have time > to adjust. > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Fri, Mar 19, 2010 at 9:44 AM, Nick Arnett wrote: > > > On Fri, Mar 19, 2010 at 7: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, > > > What is the definition of "popular?" > > > Nick > > > 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
Even further clarifications:
Top Tweets are coming to make search results even more relevant. We'll be
tuning our ranking algorithms with gusto. Some people will naturally resist
these changes. Approach with a zen mind.
When we launch this new feature for the API, it will be opt-in for a
transitory period, but the search.twitter.com site will come with these
results already baked in. Before implementing in your own applications,
you'll be able to see the top results for your favorite queries your self.
The Search team is always working on ways of making results more
relevant. We recognize that not everyone wants search results with
algorithmic ranking of tweets, but we like what we've come up with and we
think you'll like it too.
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Fri, Mar 19, 2010 at 10:11 AM, davidzimm wrote:
> Bad idea.
>
> 1) reduces the credibility and thereby the value of the results in
> twitter search
> 2) who determines which is popular- no matter how you try to calculate
> this, someone will figure it out and spam the results.
> 3) people are used to searching twitter for breaking news, rather than
> "authoritative" results. You'll have to change user expectations.
> 4) perhaps this can be an "advanced" setting, rather than a default
> practice.
>
> On Mar 19, 10:37 am, Taylor Singletary
> 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":"http://www.atebits.com/";
> > rel="nofollow">Tweetie",
> > "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":"http://www.atebits.com/";
> > rel="nofollow">Tweetie",
> > "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!
>
[twitter-dev] Re: Most popular tweets in the search API
Bad idea.
1) reduces the credibility and thereby the value of the results in
twitter search
2) who determines which is popular- no matter how you try to calculate
this, someone will figure it out and spam the results.
3) people are used to searching twitter for breaking news, rather than
"authoritative" results. You'll have to change user expectations.
4) perhaps this can be an "advanced" setting, rather than a default
practice.
On Mar 19, 10:37 am, Taylor Singletary
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":"http://www.atebits.com/";
> rel="nofollow">Tweetie",
> "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":"http://www.atebits.com/";
> rel="nofollow">Tweetie",
> "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",
> "id":9153622261,
> "from_user_id":106309,
> "geo":null,
> "iso_language_code":"en",
> "source":"http://www.atebits.com/";
> rel="nofollow">Tweetie",
> "metadata":
> {
> "result_type": "popular"
> }
> },
> {
>
> "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":"http://www.atebits.com/";
> rel="nofollow">Tweetie",
> "metadata":
> {
> "result_type": "recent"
> }
> }
>
> /* etc ... */
>
> }
>
> --- Only getting popular results ---
>
> If you *onl
Re: [twitter-dev] Re: Most popular tweets in the search API
> > 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. > > +1. Don't break backwards compatibility unless there's a really good > reason to do so. Also +1. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- If you're too open-minded, your brains will fall out. -- 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
On 3/19/10 10:42 AM, funkatron 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. +1. Don't break backwards compatibility unless there's a really good reason to do so. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) 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.
[twitter-dev] Re: Most popular tweets in the search API
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 Finkler
http://funkatron.com
Twitter:@funkatron
AIM: funka7ron
ICQ: 3922133
XMPP:funkat...@gmail.com
On Mar 19, 10:37 am, Taylor Singletary
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":" rel="nofollow">Tweetie",
> "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":" rel="nofollow">Tweetie",
> "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",
> "id":9153622261,
> "from_user_id":106309,
> "geo":null,
> "iso_language_code":"en",
> "source":" rel="nofollow">Tweetie",
> "metadata":
> {
> "result_type": "popular"
> }
> },
> {
>
> "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":" rel="nofollow">Tweetie",
> "metadata":
> {
> "result_type": "recent"
> }
> }
>
> /* etc ... */
>
> }
>
> --- Only getting popular results ---
>
> If you *only* care about popular results for a given query term, yo
