> 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 * Flo
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 detai
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
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"
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
calcul
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 tweet
+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.
+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
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 (#tweetsearc
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)
> 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 de
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
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
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
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
transito
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
"authorit
> > 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
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 compa
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: 392213
19 matches
Mail list logo
