I’ve been using Photophlow a fair amount over the last few days – It’s been pretty fun, although the real value will come if we manage to use it for shoot planning or review, which hasn’t happened yet.
One thing that I’ve noticed is that having Photophlow open in a browser while I’ve got other webapps running tends to make the overall experience a bit less nicer. So taking a page from Travis Vachon, I created a Prism (Webrunner) application for Photophlow. This lets you run Photophlow as a standalone application, in a container which is essentially a custom version of Firefox. You can get the webapp here. You will also need a copy of Prism to make this work.Author Archives: Ted Leung
New blog theme winner – Gridlock K2
2 Replies
For now I’ve settled on a new theme for the blog, “Gridlock K2“. I’m running the latest RC(3) of K2 and there were some issues with the Gridlock style, some of which were also reported on the Gridlock K2 page, without resolution. Matthew Eernisse, our resident AJAX and CSS wizard for Chandler Server, was kind enough to take a look at the issues that I was having, most notably the sidebar being pushed to the bottom, and the menu rendering oddly. Matthew reduced hours of work to just a few minutes. In order to prevent anyone else from having to do that, here’s a pointer to the “fixed” gridlock.css for the Gridlock K2 style.
Photo 2.0 – Photophlow
Last night, Scoble mentioned Photophlow on Twitter. I went over to see the site and then begged and pleaded for an invite – and got it. Photophlow is kind of like an IRC customized for dealing with Flickr photos. There is a global chat room, each user has his or her own chat room, and there is a chat room for every Flickr group. Within a chatroom, people can search Flickr photos and the room can follow along to see what they are searching. You can select photo out of the search, which will be transmitted to the room. There are some other features, like turning off the following of other people’s searches and turning off people’s ability to see what you searched for.
The Photo 2.0 angle
People like David Hobby and Chase Jarvis have been talking about (and living out) “Photography 2.0”, where there is massive sharing of photographs and photographic information. One of the things that I’ve often wished for is the ability to talk (in real time) to someone to get/do a critique of a photo. I think that this is something that happens best in real time. You could do that via IM and hyperlinks. You might even be able to do that via IM group chats, if all the people in the critique were using the same IM system. (It’s 2008, IM vendors). The value that I see in Photophlow is having a realtime way of talking about photos in a group. It would be even better if there was a way to annotate the photo being broadcast at the moment, so that you could focus attention on particular parts of a photograph. We’ve been doing some interesting group photo stuff here in Seattle lately, and I definitely think that Photophlow is something that could really help with some of the things we have done, as well as some of the things we are thinking of doing. Besides annotation tools, I would also like an easy way to log/archive a whole chat session or parts of a chat session.
The Web 2.0 angle
Photophlow is technically interesting for a number of reasons. It’s an app that’s built entirely on top of another web applications’ API. And it’s pretty substantial. There’s a lot going on here – a lot of AJAX, and API calls to Flickr. The app feels kind of pokey because it’s pushing the limits of what can be done in Javascript. Indeed, if I run Photophlow in Safari 3 instead of Firefox, the performance is noticeably better. This is a situation that we also see in Chandler Server. It’s going to be interesting to see how well this is able to scale up.
Photophlow is also pushing the limits of how some people think of using a web application. It’s designed to be used a lot and in a highly interactive fashion. I know that I would probably keep chat rooms for my personal group, the Seattle Flickr Meetups group, and the Strobist group open all at once if I could. The designers have also built in bridges to IM notification and to allow you to Twitter from within Photophlow. Too bad their isn’t a way to get a Twitter stream instead of an IM notification – but that’s more a limitation of Twitter than of Photophlow.
I bet that you could do some of what Photophlow does with a custom IRC bot. But I also bet that it would be substantially less accessible to people who are photographers first and computer users second (or third, or what have you). Then again, maybe here’s another opportunity for VOIP…
If you haven’t gotten into the beta yet, there’s a short tutorial video.
Technorati Tags: photography, photophlow, flickr
New Blog theme
I’m trying out a new blog theme. Let me know what you think.
2007 – The year in photography
Here’s a round up of the highlights of my photographic year.
January
A trip to San Francisco gave me the chance to hang out with the San Francisco Flickr group – one of my favorite things to do in San Francisco – that is when the stars align.
February
I was the official photographer for Bainbridge Island’s second annual Chinese New Year Festival. I got the gig because my pictures of the previous year’s event showed up in the top 5 results for the search “Bainbridge Island chinese new year”.
March
A trip to the Seattle Aquarium:
April
I attended Zack Arias’ amazing One Light Workshop. Shortly thereafter I bought some PocketWizards and started my journey to the lit side.
May
June
July
The Kitsap Sun bought this picture and ran it in the Bainbridge Islander (the local local paper).
August
I attended my first Seattle Flickr Strobist event, and finally connected with some local camera nuts.
Also in August I got to meet David Hobby in person at the Seattle Strobist Seminar.
I confirmed my status a a photography nut by staying up to photograph the lunar eclipse:
September
I finally got around to making some Strobist style grid spots
Which I promptly put to use during my first studio shoot with the Seattle Flickr Strobists.
I also did a Strobist architectural shoot:
October
I practiced my lighting and people shooting skills
November
I framed my first picture in order to display it in the November Seattle Flickrites photo show
I also covered ApacheCon, as I have in previous years.
This year I also put my new skills to use by shooting a bunch of headshots for ASF folks. Average time per person: 5 minutes
December
Another Seattle Flickr Strobist shoot (including video) gets featured on Strobist.com.
It’s been a great year of learning and improving. Thanks to all the people (and there are a lot) who have helped me out along the way!
Photo thoughts
There have been a few photo related blog posts and twitter conversations that I wanted to comment on.
First, buying digital SLR’s. Tim Bray commented on Dave Sifry’s Beginners Digital SLR buying guide, and ranted on the insanity of buying a camera based on the number of megapixels, which is a very common metric. Buying a digital SLR is a sizable task — I wrote about it last year. I didn’t recommend specific cameras, but I did try to point out a bunch of things that I wish someone had told me, in addition to the initial purchase of the camera. One thing that I would note is that there’s a lot more to taking photos than just the camera. Technology people tend to get obsessed with the specifications and features of the gear, but the most important piece of photographic equipment is between your ears. People think that having a good camera will automatically result in good pictures, but that just doesn’t make any sense. It’s like saying the buying really good paintbrushes will make one a painter, or that buying really good pots and pans will make one a chef. There’s nothing wrong with wanting a nicer/newer camera, just be aware that you aren’t going to turn into Ansel Adams when it arrives.
Second, post processing software. This one is a result of a late night Twitter storm between Stephen O’Grady, Tim Bray, and to a lesser extent, me. Steven wanted to know about choosing between iPhoto, Adobe Lightroom, and Apple’s Aperture. People on a Macintosh probably have iPhoto lying around, and it is decently competent for people are not photography enthusiasts. The cost of trying it is pretty minimal, since it is bundled with Mac OS X, although if you have an older Mac and haven’t upgraded iLife recently, it’s probably worth it to do that after giving it a try. iPhoto leverages OS X’s system wide RAW conversion, so it can even handle RAW files from DSLR’s and high end point and shoots.
That leaves Lightroom and Aperture. I was an early fan and adopter of Aperture, and I was pretty happy with it until recently. Since October, I’ve stopped running Lightroom and Aperture side by side and am only using Lightroom. I’ve now had a chance to really work with the Photoshop integration, which works decently well – I wish there was a way to go back and re-edit a Photoshopped version instead of Lightroom creating another copy, but you can work around this by opening the Photoshopped version with Photoshop directly — Lightroom correctly updates once you save the file. The Lightroom API’s have started to show, although not as quickly as I thought they would. Right now you can mostly get export plugins, which means there is now a way to publish to Flickr directly with Lightroom, although none of the plugins (or Flickr’s on Uploadr 3.0) is anywhere near a match for Frasier Speirs’ FlickrExport, which doesn’t have a Lightroom version.
More importantly, I’ve really lost a lot of faith in Apple in terms of the future of Aperture. I thought for sure that there would be an Aperture 2.0 when Leopard was released. We might still see it at MacWorld or PMA in late January, but it doesn’t build my confidence that Aperture is an important product. When I got Lightroom, on the other hand, it was at version 1.1 and is now up to version 1.3.1. Adobe was very public about Lightroom/Leopard issues, and has been relatively quick to address them. Apple, on the other hand, is following its usual tight lipped policy. Both of these programs are first versions, and each needs additional development. Apple is leaving me with a reasonable amount of doubt as to whether they are really committed to Aperture.
Seattle photography scene
The Seattle amateur photography scene is exploding. Here’s some video that shows what we’ve been up to recently.
My favorite picture from the event:
Maybe now David Hobby will move to Seattle…
ApacheCon US 2007 Update
Yesterday I did my talk on Open Source Community Antipatterns. I am always nervous talking about community stuff in front of an Apache crowd, because these are folks who have a huge amount of cumulative experience in this area. There were some good questions and several people asked me if the slides would be available. I’ve put them up on the page with some of the other for ApacheCon US 2007. I was happy to have that under my belt.
I also co-hosted the ApacheCon Lightning Talks with Brian Fitzpatrick, last night. The Lightning Talks at ApacheCon are very entertaining, to the point of really being part of the entertainment as opposed to being part of the technical program. A no slides rule helps keep it that way. Kudos to those brave folks who gave “straight talks”, and to those who found ways to make their funny talks relevant somehow. Thanks to Fitz for asking me to do it with him — I expect Wilfredo Sanchez to be returning to his regular spot as the co-host, though.
Technorati Tags: ApacheConUS2007
ApacheCon US 2007 is now in full swing
The main conference portion of ApacheCon US 2007 has now started here in Atlanta. We’ve already had two days of tutorials and the Apache committers’ Hackathon.
I’ve put up a set of pictures on Flickr and will be updating them throughout the week.
Best of the 2.25 days so far: Doc Searl’s keynote about the live web, including ProjectVRM.
Caja: Capability Javascript
Ben Laurie has posted some initial information about the Caja (Capability Javascript) project that he is leading at Google. The code is going to be open sourced under the Apache License (with Ben running it, that’s no surprise). Caja is based on the work that Ben did on CaPerl a few years back. I saw CaPerl when we were looking at how to improve Python security for Chandler Desktop. Ben was interested in doing some capability stuff for Python, but the stars never aligned for it to happen. I’m glad to see that his work will live on – it’s not like JavaScript couldn’t use some security help. People worried about yet another version of Java/ECMAScript should go read Ben’s post before they complain.