|
Wingedpig.comWeblog for Mark Fletcher |
Continuing my experiments with iPhone panoramas (and risking turning this blog into just a photo-blog), this was stitched together using Photoshop CS3 from three pictures I took this weekend. I'm not terribly happy with the colors, but I'm a bit limited with the iPhone.
Every spring, the county brings in this herd of goats to munch on the grass across from my house. The furry lawnmowers devour a prodigious amount of grass every day, and they make quick work of the area. It's difficult to see in this picture, but there's a goat walking across the pipe. This group is about half of the goats working the hill. When they're all concentrated in a smaller area, it looks like a sea of fur and horns.
Last night, Amazon announced that they're adding a persistent storage capability to their EC2 service. To review, EC2 provides the ability to create virtual servers on the fly. These servers are a bit ephemeral, however. They can fail at any time and don't provide any persistent, local storage of their own. If an EC2 instance fails, you have to completely restart it, losing any data it may have been working on. Amazon's S3 service is persistent storage, but it is not designed to be accessed as local storage by EC2 instances. The newly announced persistent storage capability is designed to solve this issue. It's like an on-demand S.A.N., but with more flexibility. One of the really nice things about it is the ability to checkpoint a persistent volume to S3. This is great for database backups, among other things. No performance numbers have been published yet, but those who have been using it say the performance is good. This makes Amazon Web Services even more interesting, because it's now easier to run a normal MySQL instance without having to do something like running some kind of replication just to deal with the non-persistent local storage. And it scales up.
See Werner Vogels' announcement of the persistent storage service, and RightScale's analysis of it, for more information.
A friend, seeing my panorama pictures yesterday, said I could have done a much better job using Photoshop CS3. He offered to redo one of my panoramas to show me how much better Photoshop was at blending the exposures of the individual images. I have to agree, it definitely looks better. The resulting picture doesn't have any of the banding or abrupt transitions seen in my original panoramas. Time, perhaps, to grab a copy of CS3. The only question is whether it's worth spending $1000 on.
I've been experimenting with panoramas over the past few months, with varying degrees of success. Panoramas are multiple pictures of a given scene, from different views, combined into one larger, (hopefully) coherent, image. Since I'm only using my iPhone, the individual source pictures aren't that great (fingers crossed that iPhone 2.0 has a better camera), but I like the results. I'm using Calico to assemble the panoramas, and I think it does a good job. One of the challenges is adjusting the exposure/colors of the individual pictures. Calico does some of that automatically, but as you can see in these, there's still some variation. A second challenge is getting enough 'coverage' of the scene. As you can see in these panoramas, there are some black spots indicating where I didn't get enough coverage (ie. take a picture). Click through each picture to Flickr for other sizes.
The first panorama was taken in Kauai last month:
The next two panoramas are from Northstar, Lake Tahoe. The first is from off the top of Comstock:
And this one is from mid-way down Prosser. It's difficult to see, but in the upper, middle of this picture is the Truckee, Tahoe airport:
The concept of aggregation is increasingly important on the Internet, as the sheer number of information resources increases. The average user wants to track more and more things on the Internet; an aggregator quickly becomes necessary as one's bookmark list grows to infinity. The first aggregators, what I call 'general purpose' aggregators, like Bloglines, Google Reader, and Newsgator, are focused on tracking blogs and news feeds, making it easy to subscribe to whatever blogs the user came across.
The new service FriendFeed has been getting a lot of attention the past couple of weeks. It's the latest in the line of what I call 'individual aggregators,' services that aggregate all the distributed parts of a person's on-line presence in one place. A person may have a blog, a Twitter account, a Flickr photostream. These services combine all of these items in one place. This trend started with Facebook's newsfeed, continued with Plaxo's Pulse, and then several other services, including Tumblr can do most of what the individual. These services are different than the general purpose aggregators in that they're focused on tracking individuals, not feeds. But the general purpose aggregators can do what the individual aggregators can do, because the underlying technology, RSS, is the same. It's really just a matter of user interfaces and a key bit of information.
The individual aggregators collect a list of all of the distributed parts of a person's on-line presence. They ask each user to list their Twitter account, their Flickr account, their YouTube account, their blog. This list doesn't exist anywhere in a way that's machine readable. Each of the individual aggregators has to deduce this information and then maintain it. Or more specifically, each user has to maintain this information on each of the individual aggregators. Wouldn't it be better if this list existed somewhere under direct control of the user in a way where it wasn't siloed in a centralized, proprietary service? That way, every aggregator could take advantage of it and users would only have to update the list in one place.
This problem is actually a general purpose version of a problem already solved by something called RSS Autodiscovery. In order to make it easier for general purpose aggregators to find RSS feeds to subscribe to, many publishers included a special line of text in the headers of their HTML. I have one on my blog:
<link rel="alternate" type="application/rss+xml" title="RSS" href="http://www.wingedpig.com/index.rdf" />
Aggregators know to look for this line, which tells them where the RSS feed for that blog exists. Can't we just extend this to include a list of all the other aspects of a person's identity? Have one line for each service the person uses, and change the title accordingly. So, I could include:
<link rel="alternate" type="application/rss+xml" title="Flickr Feed" href="http://api.flickr.com/services/feeds/photos_public.gne?id=35034347955@N01&lang=en-us&format=rss_200" />
for my Flickr feed. This doesn't have to only apply to services that publish RSS feeds. I could even do something like:
<link rel="alternate" type="application/twitter" title="Twitter" href="wingedpig" />
to indicate my Twitter account.
By doing this, the list of all the parts of a person's on-line presence is kept under the control of the person, associated with their blog. It's distributed, open, and easy to implement.
For this to work, a couple things need to happen. Blog publishing software has to be modified to ask for and then insert this information into the headers of a person's blog. Then,aggregators need to be modified to look for this information, and to periodically recheck it. The general purpose aggregators need to augment their interfaces to allow people to subscribe to these new feeds. But none of these things are terribly difficult to do.
The system failed me. When I think about it, I get frustrated that this should never have happened or gone so long undetected in me. I've heard that healthcare is in the process of changing SOP to provide MRIs in young women (mammograms are still better for older women).And, her advice to women:
Soapbox moment: I believe most women do find lumps themselves. Just remember, that a mammogram doesn't rule out cancer and now you can be proactive about your care. Always get it tested if not removed.Cancer is a terrible disease. My thoughts are with Melanie.
Dear Lazyweb,
I'm in need of a new laptop bag, something on the smallish side. It needs to fit my Macbook Air and its power adapter, my Kindle and its power adapter, my Bose headphones, possibly a small mouse, and a couple of cords. So, not much. Any recommendations? I'd like to see it in person before I buy it, and I'd like to get it this weekend, so that eliminates mail-order places like WaterField.
From outside a bar in downtown Aspen.
