Ted Leung on the air: Open Source, Java, Python, and ...
I consider Thomas Hawk to be one of the superstars in the Flickr's community. He shoots prolifically, and almost every day I see a great shot of his go by. He's also very active in the Flickr on-line and offline communities. Thomas has been very vocal and hands on about photographer's rights. On top of all that, he also maintains a great blog where he talks about photography and technology in general. So when I read that he was going to Work for Zooomr, I paid attention. A lot of attention.
As I wrote previously, the thing that make Flickr sticky for me is the community of people. I have built up enough of a base there that I'm unlikely to switch to another photo-sharing site just for features. But if a bunch of people that are part of my personal community started hopping over to another site, then that would get my attention. The blogosphere is already aflame with the conversation about the technical end of this: should there be wholesale import/export API's or tools, who should provide them, and so forth. That's all fine, and I'm not worried about any of that, because in the end, any system that provides an API will end up having a way to do import/export. The more interesting question is, what could cause a sizable portion of the community to make the jump to a new system.
I think it's going to be interesting to see how this plays out, because Thomas has said he is going to keep on going at Flickr, so for the moment, there isn't going to be a break in the network. But if the day comes that Thomas switches to Zooomr as his primary, that's going to be very interesting. When companies try to build a product or service around a community, prominent members of that community are going to have more and more of an impact.
I wonder whether over time, we'll see further and more crisp stratification of the photo sharing market: Yahoo Photos for families, Flickr for people who want to learn and get serious about photography, Zooomr for the really hard core photographers... I'm not making a prediction about either niches or residents of those niches, but it is interesting to think about.
For me Flickr and Zooomr are about two different things. Flickr is a full rich community with lots and lots of community interaction. Zooomr's not there yet. But we are working towards that. We need to build a lot more of the community tools which we are working on for version 2.0 due out next month.
What Zooomr's got over flickr in my mind though is amazing features (and more to come) geotagging, trackbacks, advanced analytics, etc. Ultimately I'd even like to figure out a way for the advanced pro/am type of user to monetize their photostream (stock sales, print sales, etc.). But a lot of work must happen first before that would happen.
But Kris can write features super fast for Zooomr and I think whereas Flickr is the richer community today that Zooomr will be the ultimate photogeek toy going forward. For me there's room for both in my life. I think for a lot of the hardcore photogeeks there will be room for both. Others who spend less time on photosharing sites will have to look at each and kind of judge their own merit side by side.
I'm super excited about Zooomr and where Kris is taking. And I'm also super excited about the rich community that you describe well at flickr here now today.
Posted by Thomas Hawk at Wed Jun 21 05:00:19 2006
Whether that comes to pass is likely predicated on the nature of the communities. The middle-tier users who "want to get serious about photography" are going to want to hang out with the experts where they can really learn something - not with other learners so I would expect a migration to where the experts are.
The question is whether the "hardcore photogeeks" want to share their community with learners.
Posted by IanS at Wed Jun 21 07:09:51 2006
To insert a URI, just type it -- no need to write an anchor tag.
Allowable html tags are:
<a href>
, <em>
, <i>
, <b>
, <blockquote>
, <br/>
, <p>
, <code>
, <pre>
, <cite>
, <sub>
and <sup>
.You can also use some Wiki style:
URI => [uri title]
<em> => _emphasized text_
<b> => *bold text*
Ordered list => consecutive lines starting spaces and an asterisk