Thanks for the insight this early into everything. This helps from the communication standpoint.
I hope this devolve thought into design by commit on this thread though for the name-spacing. I have a few ideas but I'm reserving them because they may be obvious and not going to hurt me because I can work around anything you make. Now make some annotations. :-) Zac Bowling On Fri, Apr 16, 2010 at 1:43 PM, Marcel Molina <mar...@twitter.com> 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 <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: >> http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >> > > > > -- > Marcel Molina > Twitter Platform Team > http://twitter.com/noradio >