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.com> wrote:
> 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
> with this list.
> 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
> > surface on something like dev.twitter.com initially (and maybe even an
> > 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>
> > > 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
> > > team and see if we can surface analytics on the most used namespaces
> > > 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:
> > >>
> > > --
> > > Marcel Molina
> > > Twitter Platform Team
> > >http://twitter.com/noradio
> > --
> > Marcel Molina
> > Twitter Platform Teamhttp://twitter.com/noradio
Twitter Platform Team