MIME-Version: 1.0
Received: by 10.101.62.10 with SMTP id p10mr1066128ank.34.1255564263419; Wed, 
	14 Oct 2009 16:51:03 -0700 (PDT)
Date: Wed, 14 Oct 2009 16:51:03 -0700 (PDT)
In-Reply-To: <8ab9c18e-c589-486c-bd1c-9b7fa592d3e4@m7g2000prd.googlegroups.com>
X-IP: 69.181.1.244
References: <3a7f9a9e-6dee-4cac-922f-1b1c85ee9d02@d4g2000vbm.googlegroups.com> 
	<B8FDF604-0899-4E86-A8BD-549CADC214A3@gmail.com> <02c02eb5-34b4-4946-9d82-ced05515be23@g1g2000vbr.googlegroups.com> 
	<bef96b30-a4aa-4079-9773-3511481967f3@13g2000prl.googlegroups.com> 
	<8ab9c18e-c589-486c-bd1c-9b7fa592d3e4@m7g2000prd.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_1; en-us) 
	AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9,gzip(gfe),gzip(gfe)
Message-ID: <cf4f548c-6fa3-44ca-a7e2-0df78654966c@x5g2000prf.googlegroups.com>
Subject: Re: Order of listAll and listExplained.
From: Ingo Muschenetz <ingo.muschen...@gmail.com>
To: What The Trend API <what-the-trend-api@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

There is in the beta API. you can experiment with the "count"
variable:

http://beta.whatthetrend.com/api

Let us know how that goes.

Best,
Ingo

On Oct 14, 4:49=A0pm, Steve Cerruti <scerr...@otabi.com> wrote:
> Is there currently a parameter to limit the number of trends returned?
> Is that something you would consider?
>
> On Sep 21, 6:39=A0am, Ingo Muschenetz <ingo.muschen...@gmail.com> wrote:
>
>
>
> > That is correct. The order listed on the homepage is to encourage the
> > unexplained trends to the top of the list so that they may be
> > explained. The RSS feeds are similar, but as you say, if you take the
> > top 10 items of the feed, that will match what Twitter has trending
> > (if not the exact order).
>
> > We are looking at fixing the order of the feeds to match Twitter
> > exactly.
>
> > Best,
> > Ingo
>
> > On Sep 20, 2:08=A0pm, Crashthatch <fletcher....@gmail.com> wrote:
>
> > > Thanks for the fast response. I saw your response and looked further-
> > > it seems that the trends/listAll is in order of "most recently a
> > > trending topic on twitter" (as on the whatthetrends.com homepage), an=
d
> > > trends/listExplained is in order of "most recently had its explanatio=
n
> > > edited".
>
> > > So it seems there's no guarantee that the most popular topics will be
> > > at the top of the list, although in practice this is roughly what
> > > happens, and the current top-10 will always be the same as those
> > > listed on twitter.com.
>
> > > Tom.
>
> > > On Sep 19, 2:58=A0pm, Thomas Mango <tsma...@gmail.com> wrote:
>
> > > > You'll have to query the Twitter trends API method directly to find=
 =A0
> > > > the top ten current trends. You can then take each trend and plug i=
t =A0
> > > > into the whatthetrend API for an explanation.
>
> > > > As far as I know, whatthetrend doesn't have any support for the act=
ual =A0
> > > > order of trends on Twitter.
>
> > > > --
> > > > Thomas Mango
> > > > tsma...@gmail.com
>
> > > > On Sep 19, 2009, at 9:54 AM, Crashthatch <fletcher....@gmail.com> w=
rote:
>
> > > > > On the API documentation for both trends/listAll and trends/
> > > > > listExplained it states that "most recently explained trends are
> > > > > returned first." However when I view these feeds (in any format) =
they
> > > > > are in different orders.
>
> > > > > When I visit twitter.com to see the actual top 10 trends I get
> > > > > another, 3rd order.
>
> > > > > What I'm trying to do is to display the current top trends, along=
 with
> > > > > their explanations. However it seems like if I were to simply dis=
play
> > > > > the first 10 results from trends/listAll or trends/listExplained,=
 then
> > > > > they won't actually be the top 10 current trends- they will be th=
e
> > > > > ones whose explanations have most recently been updated on
> > > > > whatthetrend.com.
>
> > > > > Is this correct / can anyone explain why the 2 API calls are orde=
red
> > > > > differently / where I've misunderstood?
>
> > > > > Thanks,