Re: [twitter-dev] Re: Early look at Annotations

Raffi Krikorian wrote: Not to be glib, but they are more than welcome to join in on the conversation in the community. We plan to let the community really drive this one. ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that

Re: [twitter-dev] Re: Early look at Annotations

> > Not to be glib, but they are more than welcome to join in on the >> conversation in the community. We plan to let the community really drive >> this one. >> >> ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that >>> Twitter intends to leave the annotation classification system

Re: [twitter-dev] Re: Early look at Annotations

On 04/19/2010 11:21 PM, Raffi Krikorian wrote: > Not to be glib, but they are more than welcome to join in on the > conversation in the community. We plan to let the community really > drive this one. Yes, but, for example, is Sir Tim Berners-Lee even *on* Twitter? I know Marshall Kirkpatrick is,

Re: [twitter-dev] Re: Early look at Annotations

Raffi Krikorian wrote: Not to be glib, but they are more than welcome to join in on the conversation in the community. We plan to let the community really drive this one. On Apr 19, 2010, at 8:06 PM, R_Macdonald wrote: ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that

Re: [twitter-dev] Re: Early look at Annotations

Not to be glib, but they are more than welcome to join in on the conversation in the community. We plan to let the community really drive this one. On Apr 19, 2010, at 8:06 PM, R_Macdonald wrote: ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that Twitter intends to

Re: [twitter-dev] Re: Early look at Annotations

On 04/19/2010 08:06 PM, R_Macdonald wrote: > ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that > Twitter intends to leave the annotation classification system to be > determined by the market. > http://bit.ly/csK8Od > > Although I appreciate that Twitter values keeping the annot

[twitter-dev] Re: Early look at Annotations

ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that Twitter intends to leave the annotation classification system to be determined by the market. http://bit.ly/csK8Od Although I appreciate that Twitter values keeping the annotation ecosystem open for innovation and adaptation, I h

[twitter-dev] Re: Early look at Annotations

On Apr 16, 10:54 am, Marcel Molina wrote: > This isn't final. The payloads could end up wildly different after we noodle > around in things like RDF and the semantic web's literature and all that > kind of stuff. You can't see me but my hands are waving vigorously. I think there are amazing opp

Re: [twitter-dev] Re: Early look at Annotations

Marcel Molina wrote: I've talked to the analytics team. Three main metrics we're going to work to surface on something like dev.twitter.com initially (and maybe even an API so you all can build experiences/explorers around annotations): 1) All time most used namespace

[twitter-dev] Re: Early look at Annotations

XML option #2 feels like the best option to me, because it seems the most flexible, most forward compatible, and plays well with AWS: http://docs.amazonwebservices.com/AmazonSimpleDB/latest/DeveloperGuide/SDB_API_GetAttributes.html (that's my $0.02) _s. >   XML option #2 which is more verbose bu

Re: [twitter-dev] Re: Early look at Annotations

I think this will be a great addition to the platform. I suppose it will be up to each software client to determine how (classic) retweets are handled. The annotations could be copied and edited. I assume new retweets will simply reference the original tweet and its annotations. On Fri, Apr 16,

Re: [twitter-dev] Re: Early look at Annotations

I'd say keep it all on dev.twitter.com - minimise sites to visit. On 16 April 2010 22:44, Raffi Krikorian wrote: > 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 Gro

Re: [twitter-dev] Re: Early look at Annotations

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 wrote: > Thanks for all of the info, Marcel. Cool stuff! > > How would people feel about a wiki for developers to shar

[twitter-dev] Re: Early look at Annotations

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 Ann

Re: [twitter-dev] Re: Early look at Annotations

Been following the conversation; very interesting to see, even today, the devlopment of ideas around potential standards from the community of developers. To see the trends, most used, etc will definitely help us work towards the namespaces and keys with the most utility for ourselves and our users

Re: [twitter-dev] Re: Early look at Annotations

I've talked to the analytics team. Three main metrics we're going to work to surface on something like dev.twitter.com initially (and maybe even an API so you all can build experiences/explorers around annotations): 1) All time most used namespaces/keys. 2) Trending namespace/keys. 3) Most widely

Re: [twitter-dev] Re: Early look at Annotations

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 ca

Re: [twitter-dev] Re: Early look at Annotations

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 wrote:

[twitter-dev] Re: Early look at Annotations

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

Re: [twitter-dev] Re: Early look at Annotations

right now, i could send out a whole bunch of tweets with crappy yfrog URLs (that all return 404s). to end users, again, it seems like yfrog is a bad service. i mean, you have good points - and i hear all of them - its not something we are going to with for now, but i totally understand everything

[twitter-dev] Re: Early look at Annotations

Raffi, It's not about people using or not using rogue apps. It's about rogue apps poisoning the annotation data and ruining it for everybody. Rogue apps can continue to refresh their consumer keys with new accounts and OAuth app registrations, as soon as the one currently in use is suspended. Me

Re: [twitter-dev] Re: Early look at Annotations

not necessarily - twitterbots are easy to build. you can't rely on lack of usage by humans to kill a twitter app. Raffi Krikorian wrote: if there happens to be a rogue app, then users will stop using it. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Subscription se

Re: [twitter-dev] Re: Early look at Annotations

comments inline... Dewald Pretorius wrote: Marcel, I'd strongly urge you to consider a more structured and controlled environment for annotations. agreed, but... Ideally, I think an OAuth app must register a namespace, or subscribe to an existing namespace of another app, before it can c

Re: [twitter-dev] Re: Early look at Annotations

> > I'd strongly urge you to consider a more structured and controlled > environment for annotations. > > Ideally, I think an OAuth app must register a namespace, or subscribe > to an existing namespace of another app, before it can create > annotations in that namespace. And these registrations an

[twitter-dev] Re: Early look at Annotations

Marcel, I'd strongly urge you to consider a more structured and controlled environment for annotations. Ideally, I think an OAuth app must register a namespace, or subscribe to an existing namespace of another app, before it can create annotations in that namespace. And these registrations and su