Grab your helmet, check the air in your tires, and hop on your bike because in many U.S. cities, May 12 - 16 is Bike to Work Week! Six Apart has a lot of biking enthusiasts, so we're very excited to support this event by encouraging all of our employees to bike to work this week. San Francisco's Bike to Work Day is tomorrow, Thursday, May 15th, and New York's is Friday, May 16th.
Six Apart is helping out its employees by providing maps (shaded according to steepness - a must in SF!) to help everyone plan out his/her route, as well as finding first-time riders buddies to commute with. We're also supporting ALL SF riders who pass the front of our office by handing out coffee, juice and snacks from 7 a.m. to 9 a.m. tomorrow morning. If you're in our neighborhood, look for the sign that says "Six Apart Supports Bike to Work Day" and stop by to say hi and get energized!
Improve your health, financial status, productivity, and happiness by joining thousands - maybe even millions - of commuters around the country who are hopping on their bikes to get to work. Visit the Bike to Work Week website to find out more about events in your area.
Support the two-wheeled way of life with the "Passing Left" theme found in "Photo-Based" in the Design Area. Planning on cycling to work this week? Let us know in the comments!
As we mentioned last week, we had to postpone the maintenance that was due to occur on Thursday, May 8th.
We have rescheduled the maintenance for tonight, Tuesday, May 13th, starting at 6:00 P.M. Pacific Daylight Time (that's 1:00 A.M. UTC/GMT). We'll be taking Vox offline for a bit in order to move the service to a brand new home in some bright, shiny new server racks. We don't expect to be offline for more than an hour or two, but we apologize in advance for any inconvenience this may cause.
Again, thank you for your patience as we continue to invest in Vox's infrastructure!
Today's stupid software idea comes courtesy of the most recent episode of Battlestar Galactica, which featured (as some previous stories have) the Hybrid, the organic controller of a Cylon base star (aka the big pointy bad guy space ships). This week, though, saw probably more Hybrid than any other.
Hybrids, you see, continually babble, a stream of consciousness mixing what sounds like system diagnostics, physics and poetry. After the episode ended, I thought "wait, system diagnostics? Well, if I open up Console, I have those. What if there was an additional process - call it hybridd - which emitted poetry to go along with the more prosaic debugging and whatnot that my computer spits out?"
I have an idea how to do it, too. Algorithm::MarkovChain is a venerable Perl module that puts out almost, but not quite, meaningful sentences, based on an input corpus. Tie that in to the syslog function, a bit of Launch Services, and there you are. (I'm sure you could do a bogstandard Unix version too.)
A further step would be to replace the Console UI with one that boils down the actual computer stuff and tries to fit it in with the hybrid's poetry, but that idea's a lot harder to do well, I'm sure.
Anyway. hybridd - an idea whose time has come. And now, thanks to Tom Insam, here's a Perl version. Requires the aforementioned module, along with File::Tail and Unix::Syslog, both available at your nearest CPAN mirror.
When Adobe first launched Photoshop Express (from hereon in, PX) a month and a half or so ago, it featured integration with three online sites: Facebook, Photobucket, and Picasa. Unfortunately, I don't use any of those for photos. So when I saw that there was an update to add Flickr support, I dug out my old registration - the one that required me to claim I was living in the US, sigh - and had a very quick look.
Flickr appears under the "Other Sites" heading on the left nav - or is it a palette? - of the main window. Clicking the "Flickr" item asks you to authenticate, although somewhat oddly it uses desktop-style auth, so instead of using a nice redirect, PX instead uses a pop up window, which was naturally blocked. It also means you manually have to click about three more buttons than you would with web based auth. Perhaps this is explained by the amount of client-side code, but it still jarred for me. I expect users who don't have to wrangle API auth code would probably cope, though.
Once logged in, Px starts fetching images from Flickr. This is done pretty nicely- pulling each image is slow, so it will carry on if you're not doing anything else, and present the images it's already found for you. Images are sorted by date taken, which is odd if you're used to Flickr's photostream order, which is by date uploaded. (Dates are, naturally, in American format, which annoys me no end, but let's try and ignore that for now.) However, for me it stopped after just over 550 images, which is only about a tenth of the total. I'm not sure why, or how to get it to look for the rest.
Once the images are listed in the Flickr album, they're editable just like any other image available to PX. The tools aren't as sophisticated as those in the main desktop version of Photoshop, Photoshop Elements, or even iPhoto: there's no "levels" tool, and minimal highlight and shadow controls, for example. However, the white balance editor is pretty good, and there's a "Pop Color" effect for those images where you want a red London bus in a monochrome city. Beyond desktop apps, I'd also say that it compares fairly shabbily to Picnik, which is also web-based, but manages a much richer set of tools. Handily, Picnik's integrated into Flickr, making it even more likely to be used.
After editing my image, I wondered where the "save" dialog was, and where I'd get to choose whether the original image was replaced, or who'd get permissions on the new image. It turns out that this is all done automatically. An edited image gets uploaded as a new photo, with your default permissions. The title and description are preserved, but tags and date metadata aren't. To me, this is a killer flaw. Firstly, I want the option to replace an existing image. Secondly, throwing away image metadata is something Photoshop hasn't done since about version 7; it's appalling that PX does this today. Thirdly, I want the option to set privacy levels.
Once again, Picnik's Flickr integration gets all of these things right - in fact, it even seems to have an option to bump images up your photostream with comments intact, which is a very clever trick indeed. In contrast, PX looks like it's hardly trying.
One place that Photoshop Express does try very hard - for publicity - is with images that are copied from its library to Flickr. You can explicitly copy an image into the internal library, create an "album" on Flickr (what's more usually called a set, there), and then copy it back to Flickr in that set. Doing this creates a description that lets everyone know you're using Photoshop Express, and, hey, would you like to use it too? I know everyone is after viral exposure these days, but please let me know you're doing it first and let me set something more sensible.
On the subject of albums, PX loads your Flickr sets as a list of albums, although for some reason this didn't happen the first time I tried it. They're listed in alphabetical order, which, like the "date taken" ordering, is a little odd - Flickr preserves set ordering, and it would be nice if PX would honour that, at least as an option. Opening an album, unfortunately, shows an empty screen, even if there are images in the set. I assume the photo download process is linear. Hopefully a later release will change this, and let the UI take priority, as well as adding caching - each time you open the web app, it has to fetch the list of photos and sets from Flickr afresh.
For all this criticism, I do recognise that Adobe's product is just a beta. On the other hand, given how slick Picnik is, and how nicely it's integrated, it's hard to see how Photoshop Express has much to offer Flickr users, other than a brand name.
Tonight, starting at 6:00 P.M. Pacific Daylight Time (that's 1:00 A.M. UTC/GMT), we'll be taking Vox offline for a bit in order to move the service to a brand new home in some bright, shiny new server racks. We don't expect to be offline for more than an hour or two, but we apologize in advance for any inconvenience this may cause.
Thank you for your patience as we continue to invest in Vox's infrastructure!
Update: we've postponed tonight's maintenance, and will let you know when we reschedule. Thanks for your patience!
Opera just launched their alpha of Dragonfly, "the foundations of Opera's upcoming Developer Tools", which prompted Tom to note that
"Firebug seems to have defined the universe for this lot."
('This lot' includes Safari's Web Inspector, which is actually not that similar to Firebug - the JS debugger is a seperate app for a start - and IE8's developer tools, which I really should look at once I get a disposable Windows image.) It means that all four of the major browsers now ship with developer tools - an impressive change in the last year.
Tom's observation is mirrored by Michael Smith of the W3C: in his XTech presentation when he says that Firebug sets the standard by which all web development tools are to be judged.
The discussion reminded me of Steve Yegge's point in his long, but worthwhile, post about XEmacs in which he said
IDEs are draining users away, but it's not the classic fat-client IDEs that are ultimately going to kill Emacs. It's the browsers. They have all the power of a fat-client platform and all the flexibility of a dynamic system. I said earlier that Firefox wants to be Emacs. It should be obvious that Emacs also wants to be Firefox. Each has what the other lacks, and together they're pretty damn close to the ultimate software package
To be honest, I suspect what he really means here is Firefox + Firebug. At least, if he doesn't mean that, he should be. For me, doing serious web development now requires that combo, even though I dislike Firefox otherwise.
The really interesting point for me is that Firebug, unlike the three other browser development tools, is actually not under the Mozilla Foundation's control. Firefox ships with a DOM Inspector, but this is more of an internal developer tool. Firebug, a third party tool, builds on DOM Inspector's abilities, and it's built for Firefox because Mozilla have developed not just a browser, but a platform. Maybe when I criticised Gecko for their choice to build a platform as well as a browser I was missing something very important.
That extensibility means more than just Firebug, though. If there's a browser that you want to rewire from inside, using the same tools as you do to create web pages (more or less), it's the one from Mozilla. This is where Yegge is coming from, and I suspect that, hidden in a long post that's titled to attract only command-line editor users, it's a point that's likely to be missed.Last week, we announced the winners of the HP "What Do You Have to Say? Theme Design Contest and promised you we'd make the winning themes available on Vox in the coming weeks. After a little more thought, we decided you shouldn't have to wait a second longer to use these creative and inspiring designs on your blogs, so we made them available for you today. Who says good things only come to those who wait?
Straight to Video
Now you can share your Flickr videos on your Vox blog!
A few weeks ago, Flickr announced that pro members are now able to share videos of up to 90 seconds in their photostream. Many of you already post photos to your Vox blog directly from your Flickr account, and now we’ve made it so you can do the same with your Flickr videos.
To post a Flickr video to your Vox blog, just follow the same steps you would if you were posting a Flickr photo. (Yes, that means you’ll find your Flickr videos in “Photos,” not “Videos.”)
Not using Flickr to add photos to Vox? Find out how to connect your Flickr account to your Vox account. Plus, using Flickr means you’ll never have to upload a photo twice, or waste valuable storage space!
Around the World with Vox and CupCate
A little over a year ago, we announced that CupCate was one of the Grand Prize winners of the Vox World Tour. A month ago, Cate and her husband, Iain, packed their bags and flew to San Francisco, the first stop of a three-cities-in-fourteen-days vacation.
While they were in SF, Team Vox was lucky enough to have a yummy lunch with Cate and Iain and some of us even made it out for a late night karaoke session at The Mint.
We were also happy to hear, however, that she took some time to enjoy a glass of wine, a roaring fire, and the luxury of utter relaxation.
Then it was off to Tokyo where she saw gorgeous cherry blossoms, the Tokyo Tower and the Sensoji Temple, and even got a special tour around Tokyo with Ayako from Six Apart’s Japan office!
And it wouldn't be a Vox World Tour without Paris in the spring time, decadent French meals, and, of course, the Eiffel Tower.
It sounds like an amazing adventure. Congratulations again to CupCate. We had so much fun with you while you were in SF and we can't wait until your next visit!
It was hard to choose from the 355 entries, but the judges have announced the winners of our month-long "What Do You Have to Say?" theme design contest, sponsored by HP. And the winners are....
And while we know it's not polite to brag, you'll forgive us for a moment while we gush about the fact that the 2nd and 3rd prize winners are both Voxers!
The Second Place theme, “Live and Learn” was submitted by Li Kim Goh, or as you may know her: gollykim. We thought it was pretty cool to hear that Li, “didn't really think about winning, but mainly [entered] just for fun [while also] creating a few new banners for [her] own Vox blog.
When asked why blog design was so important to her, Li answered, ““because it draws readers' attention and makes your blog stand out from the millions of other blogs.” With such a great design, we think Li did just that.
The Third Place winner, Terri, showed off her “funky-fresh style” with her theme, “Vector Drips.” Terri said that having her theme picked made her day. You know what Terri? It made our day too!
The best part of the contest? In the coming weeks, we’ll make all the winning themes available on Vox, TypePad and LiveJournal so that you can use them on your blog!
Thank you to everyone who entered the contest and CONGRATULATIONS to all the winners!
I've never been one of the people who's seen a need to use any terminal application in Mac OS X other than the one supplied by Apple in Utilities. It does the job, uses Monaco 9, doesn't anti-alias (or at least, can be made not to). It starts up in Mac-ish black on white, and generally Just Works.
10.5 saw a bit of an overhaul, with a much saner configuration interface (all in Preferences, rather than hidden in a rather baffling out-of-the-way inspector) and tabbed browsing. Now, I still don't use tabs on the Mac OS, personally; I like the established app/window split and don't see the need to bring a third level of indirection into play, especially when it doesn't even have consistent shortcuts. (Tabs on Windows? Now that's a different story.) In fact, for years I'd quite happily got by with a bunch of scripts in ~/Library/Scripts/Applications/Terminal/ that would neatly stack all the windows.
Sadly, the new version of Terminal also introduced an annoying AppleScript bug which renders these scripts less than useful. When positioning a window, the vertical positions aren't honoured correctly: instead, the window ends up 320 pixels up the screen from the desired location - OK if you want a window at the top, but certainly not if it's meant to be at the bottom right, which is my usual position. I mention this now because the bug in Terminal that broke my window arrangers will also affect a script to centre windows that TALlama (no really) posted in response to a lazytwitter invocation by John Siracusa. If you try to centre a Terminal window, it ends up jammed at the top of the screen, for no apparent reason.
Now, I'm not down with the cool kids who post radr:// URLs, so if anyone who's reading this is, it's really easy to replicate the error: get a Terminal window towards the bottom of the screen, run this script - which should do nothing, as it's merely putting the window back where it started - and watch your window shift around. Do that, report it, and hopefully eventually I'll be able to retire my "set voffset to 320 -- work around AppleScript bug" line.
tell application "Terminal"
set b to bounds of window 1
set bounds of window 1 to b
end tell
Anyway, thanks for listening, and here's hoping for a better Terminal AppleScript interface in 10.5.3.
My Groups
-
Pinko Commie Traitors Updated: 1 hour ago
-
Human Rights Updated: 2 hours ago
-
Buddhism Updated: Yesterday
Neighborhood
Explore friends, family, friends & family, or entire neighborhood.
Links from my Neighborhood
MTV Multiplayer » Behold ‘P...
About this Blog You are now plugged in to Multiplayer, a ...
Check out the RockMe. Schedule. I'm not sure if this is a...
All of us as Six Apart
Vox's parent company