Wednesday, December 17, 2008

Microsoft's amazing WLW team also did Onfolio?!

I was happily scanning the release notes for the sure-to-excel WLW 2009 release when I came across a surprise note ...

Windows Live Writer 2009 RC released « whateverblog.

... On a more reflective note, this was the first full milestone (Beta to RC) we did without Charles Teague, our dev lead and voice of reason since the earliest days of Onfolio...

Onfolio is the only Windows app besides Windows Live Writer that I use and admire. I'm quite sad that Microsoft bought it only to kill it.

So one team did both products.

They must be Minnesotans.

I hope Microsoft is paying 'em very well!

Monday, December 15, 2008

Windows Live Writer news: 2009 and Blog This for Firefox 3.0

The really big news on one of my favorite apps from any vendor is that Joe Cheng has released a version of the "Blog This" add-on for Firefox 3. So we don't have to follow Joe's prior workarounds. Unfortunately it's in "sandbox mode" and won't be generally available until it collects a number of positive reviews.

So take a moment, register as a Firefox add-on tester, and contribute your five star review with a big thank you to Joe. My guess is he had to make time from his Microsoft duties to get this out.

In comparison, the announcement of a new version of WLW is a minor detail: Windows Live Writer 2009: Release Candidate. I mean, it's not like WLW 2.x was missing very much. The only WLW version news that would excite me would be a Mac version, which falls into the hell freezing category.

There's nothing in the features list I care about. Really, what I'd most like is a way to search against the titles of the post history list, and have other ways to manage the list of past posts. [See updates. Turns out the preview has some nice fixes to minor bugs and some great new features – like searching the list of retrieved past posts.]

WLW 2009 is bundled with "Windows Live Essentials", but I think you can choose which to install.

I'll wait for the release version. It's hard to improve on something as fine as WLW 2.x. Except, of course, by releasing the Firefox Blog This add-on.

Update: Joe commented that Firefox "Blog This" is a certified Microsoft product, not solely his project. Joe also tells us that the new version of WLW has the title search feature I wanted, implemented as filter.

Guess I'll have to test earlier than expected!

Thanks for the correction Joe, and thanks for your work and that of the WLW team.

Update 12/23/08: Blog This! is still stuck in the sandbox, so it needs more reviews. Works great, of course. WLW 2009 preview looks very good, so I’m glad I didn’t wait. I love the “filtering” feature – but I think it’s better than title filtering. I think it’s searching entire posts. They’ve also fixed the minor but annoying bug where the display of some labels/categories/tags for Blogger was truncated. The problem’s been long understood, but it wasn’t serious enough to justify a patch outside of this update. You have to uncheck a few things, but the new Windows Live installer will eventually agree to simply update WLW 1 and the IE toolbar.

LifeHacker's 2008 favorite features

Best Of 2008: Most Popular How-To Features of 2008

I especially like slipstreaming SP 3 into XP Installs.

Saturday, December 13, 2008

Reason over fashion: Yellow iPhone cases

I like my Clarifi case with macro lens, but since it turned my white iPhone black it's darned hard to find around the house.

Turns out, Reason is not quite dead. There are yellow iphone cases for sale. There's even a fire engine lime yellow-green case (several, actually) that would really make my phone easy to find.

I'm impressed.

The state of webcam-based low cost business videoconferencing

ver in Gordon's Notes, where I keep my ravings, I've opined on the root causes of the very slow development of useful and reliable low costs business videoconferencing.

Not for the first time, a solution seems to be almost in reach. It's been a longtime coming.

We've almost got reliable 640x480 (or more) 15fps point-to-point video with reasonably sharp edges and decent management of suboptimal lighting. That's enough to support facial expression tracking, and to enable sharing physical white boards.

Here's my summary of the state of the technology based mostly on my personal experience:
  1. There are now reasonable quality USB 2 webcams, but focusing beyond 10 feet can be a real problem. Autofocus, even when it exists, is slow and unreliable.
  2. Current webcams have very limited dynamic range. They seem to be tuned to keep from blowing out the high (right) end of histogram, so contrast extremes produce a lot of dark areas. Glare from reflected lights are a real problem. We need next generation sensors to improve the dynamic range.
  3. Our CMOS (vs CCD) webcams have surprisingly good light sensitivity, even with small lenses and tiny sensors. I often find better results with relatively dim but indirect lighting.
  4. I'd like to see some levels on the webcams to help with orientation. Oh, and a $%!$! tripod screw too. Velcro tape and black tape are most helpful, yeah, just like in the movies.
  5. Relatively modern laptops seem to have just enough horsepower to do at least 640x480 at 15fps with the newest variants of adaptive h.264 compression. That seems to be the current practical limit.
  6. Our networks are a problem. Attacks on BitTorrent seem to be taking out iChat, and possibly other video conferencing software. Comcast gets a lot of criticism; but it may be regional and it's not clear that DSL is always better. Comcast @Work may be better, but I have no real evidence yet. [see update]
  7. Gmail based Google Video Chat (Vidyo technology) has given us the image quality we need on both XP and OS X. It hasn't, however, been very robust. [1] GVC is point-to-point, no multicasts. It also has voice quality that's sometimes excellent, but we prefer to use standard phone conferencing.
  8. Stack Overflow likes Oovoo and Adobe Connect. Both have some multi-user support, but in our tests OOvoo had a lot of dropouts. On the other hand, we've had GVC issues as well.
I'll update this post as I learn more.

[1] Incidentally, Google's help forums are a waste of time. I think the XP to OS X connections have problems when a corporate VPN or firewall is involved, the XP to XP connctions seem more resilient.

Thursday, December 11, 2008

iMovie '08: Official support for FLIP Video camcorders

I wish it had happened six months ago, but for the past month or two editing clips from our Flip Video camcorder in iMovie 8 (on a MacTel machine) has been painless.

Today Apple provided official documentation on how to import the videos (mildly messy): iMovie '08: Pure Digital Flip Video MinoHD camcorders. (Directions are same for all FLIP camcorders.)

With iMovie 8 the imported AVI files are not transcoded, they can now be natively edited. I don't know about iMovie 7 and I've not tried on my G5 PPC machine.

Microsoft LifeCam VX-7000 vs. Logitech 9000 and VisionPro -- it's in the focus

I bought my LifeCam VX-6000 two years ago. For most of that time it sat on my shelf.

Now, thanks to Google Video Chat, and several Microsoft updates of the incredibly botched device drivers, it's finally useful [1].

It's a pretty plain webcam, but it does 800x600 video and that's more than our infrastructure seems able to handle these days. Even 640x480 over Google Video is enough to make a small but close whiteboard readable.

The killer feature of the VX6000 is the manual focus ring. It's chintzy, but it makes all the difference.

Which is why Microsoft's current top-of-the-line webcam seems ... stupid:
LifeCam VX-7000 (Windows only)

...The webcam is always in focus – no fine tuning needed. Focus depth of field is from 21” to 60”...
Right. Always in focus. Uh-huh. They still sell the VX-6000 by the way, but they don't mention the focus ring. Gotta love marketing.

By contrast the competition does autofocus -- sort of ...
Logitech QuickCam Pro 9000 (windows only, 960x720 video, aka 720p [2])

Premium autofocus: Your images stay razor-sharp, even in close-ups.
Except from (excellent) Amazon reviews we learn that the VisionPro's autofocus is controlled by the computer, not the camera. So it's sluggish and slow. It also sounds like some VisionPro's can focus further than others, and anything beyond 8 feet is pretty iffy.

There's no manual focus ring on either the Logitech or the LifeCam. Grrr.

Lastly, we have the one and only webcam sold for OS X:
Logitech VisionPro (OS X theoretically, but see this.)

...Premium autofocus: Your images stay razor-sharp, even the most extreme close-ups...
There's about zero information on Logitech's site, much more in their press release
To deliver image-perfect detail and clarity, the Logitech QuickCam Vision Pro webcam for Mac combines Logitech’s premium autofocus technology with Carl Zeiss optics. The new Logitech webcam uses a voice coil motor for its autofocus system, instead of a stepper motor. Focusing is fast and fluid – crisp even in extreme close-ups only 10 cm from the camera lens. Logitech’s autofocus system compensates for changes in image-edge sharpness and refocuses images in less than three seconds.
and on Amazon we get very mixed reviews of the autofocus, from this to this. I wouldn't expect to get much out of this camera on a non-Intel system, so it's really an accessory for the Mac Mini (other Intel systems have built-in not-to-bad webcams). One review that impressed me claims that this camera does its own autofocus, not relying on the computer and gives us the low down on resolution ... [see update]
Autofocus and autoexposure (light level) are done purely in hardware. There's no software to install. This is different from the earlier Logitech QuickCam 9000, which depended on Windows software to do the focus and exposure, which lowered the price of the webcam, but forced you to use Windows. The microphone is pretty good for a webcam, but you'll still want a headset for clear conversation. Frame rate is very fast and smooth, 30fps at 640x480.

... The included stand is very wobbly, and falls down easily. When set on top of the monitor, gravity's the only thing holding it on, it will slide off easily. Unlike the older Logitech webcams with flexible plastic that could mold into place, this camera has stiff plastic, so it doesn't maintain as good a grip. No zoom. Frame rate gets much slower if resolution is increased beyond 640x480. At 960x720, it's 15fps. At the maximum 1600x1200, it's only 5ps. Anything above 960x720 is just hardware upscaling, as the true optical resolution of the webcam is 960x720.
Now that's a review!

The ability to work without drivers on XP is very interesting.

For my purposes I may stick with the LifeCam, but buy one or the other of the Logitechs for our other team members.

[1] The process of establishing a trusted chat relationship is nuts. See update to my Google Video Chat post for what I think works.

[2] Be careful. You may find your chat software won't allow anything beyond 640x480, so this number may be pointless. iChat peaks at 640x480, and practically speaking, that's the limit for everything today. I think to do better we'll need dedicated hardware based h.264 compression on the camera.

Update 12/19/08: (posted as comment on Mr. Krellan's initial review)

I had to order several XP webcams as part of a corporate order, and based on this review I ordered one VisionPro and several Pro 9000 cameras.
... On my XP SP2 laptop the camera took a few seconds to register. In Windows Explorer it then showed up, next to my drives, as a "USB Video Device". (In properties it's "manufactured by microsoft".) Clicking on the "USB Video Device" in Explorer opens a video window. In this display is no "mirroring" or zoom since we're just seeing unmodified output.

The camera focused clearly at 6" (rather better than claimed) and at about 30 feet.

Adjustment to light levels is automatic and impressive.

The dynamic range (ability to deal with glare, bright and dark areas) is vastly better than my 1-2 year old Microsoft VX-6000.

It's a solid device. Mr. Krellan is correct that it doesn't mount very securely but I think will suffice.

Impressive.

Fantastic list of iPhone tips - mostly keyboard

Referral via Daring Fireball - tap tap tap ~ 10 useful iPhone tips & tricks.

There were two things on the list I didn't know about, including how to create 'curly braces' for quotes. I've also reset my phone rather than turn it off when apps slow down, but recovery from off is faster so I might try that.

There are many things about the iPhone that frustrate and worry me, but the virtual keyboard is a work of genius and beauty.

Wednesday, December 10, 2008

Google's SMS integration - assigning a 406 area code phone number to your Gmail ID

Google has added a (phone) SMS gateway to their Instant Messaging and Video (Chat) Conferencing Gmail extensions.

This would be more interesting if we didn't pay 40 cents every time I sent Emily a text message.

As it is, the most curious part is how they enable Gmail to receive SMS messages ...
Official Gmail Blog: Really new in Labs this time: SMS Text Messaging for chat

... On the receiving end, when you get a text message from Gmail on your phone, it will come from a number in the 406 area code... You can reply to this text on your phone just like you'd reply to any other text. The reply gets routed back to our Gmail servers and shows up in your friend's Gmail chat window...

... messages will come from a [unique] 406 number so you can reply to any message and it will get back to the right person. Messages from the same person will always come from the same number, so you can even bookmark it in your phone....
My interpretation of this cryptic announcement is that the first time you use Gmail to send an SMS message, your Gmail identifier is assigned a unique 406 phone number. From that moment on SMS to that number go to Gmail.

Makes me wonder if there's a GrandCentral angle to all this.

It's not clear whether other phones, with whom you've never communicated, can use that unique number to send Gmail an SMS.

From my perspective this is backwards. I want Google instant messaging on my iPhone, I don't want to bother with SMS at all.

Update: Chris, in comments, notes that 406 is Montana's area code (I also had a 404 typo I've corrected). They chose it to get lots of free numbers.

Apple's iChat (videoconferencing) problem

I was looking at using iChat for some business videoconferencing. That's when I realized what a mess OS X iChat is. Great client software, but a mess on the back end.

iChat depends on  a network service to establish a connection. I thought that could be either MobileMe ($$) or AOL's AIM service.

I have an old AIM account, so I took a look at them today. They're in disastrous shape. I ran into authentication issues, services that were "down", security errors (bad certificate chain) when attempting to create an account in IE 7, etc.

Wow. That makes iChat much less useful. With AOL/AIM dying in the Dacopalypse I don't want to expose anyone to them, but MobileMe isn't an option.

Ben enough, but it gets worse. MobileMe has an AIM depency too.

MobileMe: About expired accounts and iChat

... When you create a MobileMe account, Apple creates an AOL Instant Messenger (AIM) account for you that uses your MobileMe member name and password. Your MobileMe account and its entry on the AIM service are linked, so that administrative actions, such as password modifications, are carried over from MobileMe to AIM.

As long as your MobileMe account is active, the associated AIM account will also be active for your use with iChat...

So is MobileMe really using AIM's infrastructure? Brrrr. That's ominous.

At least Intel Macs can use Google Video Chat, and I think Oovoo and Skype will work on any OS X machine.

Apple needs to extricate itself from it's AIM dependency -- yesterday.

Monday, December 08, 2008

Google Tasks show up -- in Gmail?!

I thought Google might add Tasks to Calendar -- but instead they show up as a minimalist Gmail add-on.

No API, no import/export, no calendar integration and, obviously, no synchronization with Appigo's Todo.app.

Reminds me of the pointless task feature Apple added to Mail.app in OS X 10.5 (Apple completely screwed that feature).

Yawn.

Google, my offer stands.

My review: LaCie 1 TB USB 2.0 External Drive 201304U

My 200 MB Venus enclosed backup drives needed a size boost. They're a 2-3 years old anyway, that's getting geriatric for today's short-lived consumer drives.

I like the Venus enclosures, but the fans do tend to die, or just get noisy. I wanted a fanless design since they seem to work with today's cooler drives. I also wanted to get the drive and enclosure together to cut down on the hassle factor.

The LaCie USB enclosure was on sale at Amazon (Black Friday), so that's what I got. Here's my Amazon review ...
Amazon.com: LaCie Hard Disk 1 TB USB 2.0 External Hard Drive, Design by Neil Poulton 301304U: Electronics

I bought two of these for my rotating backups at a sale price of $120.

I wasn't impressed by the case, but I was impressed by the 2 year limited warranty. La Cie has been around for a while, so this long a warranty suggests they expect the drive to last. That's all I care about. For the purposes of storage attached to my backup server performance is irrelevant.

Some quick observations:

1. You could cut an artery on the case. Really, it's a bit silly even without LED glow. I prefer a sturdier case with softer edges.

2. Vents are in back and the base, so you can stack on atop another. I would still recommend not stacking though, these things should stay cool.

3. I believe it's fanless.

4. On XP SP 2 it doesn't spin down. I don't know if it would spin down on a Mac. Too bad, spin down preserves life in these cases.

5. Comes with a standard 2A 12V compact power supply with a modest brick in mid-cord. So easy to plug in. Completely generic brand, not La Cie branded. The power cords is not excessively long, just right for me.

6. The attached USB cable is very short. I have lots of cables, so I was happy to get a new one that's short. I used another cable with this.

7. When you plug it in you have the option of formatting for OS X or XP. I tested both. With OS X it seems to do a full formatting, but with XP it formatted far too quickly. It must have been preformatted. Unfortunately, with XP I ran into some odd behavior with delayed write errors. Could have been chance, but I did a proper full XP format (takes hours) and the drive then behaved properly. I don't like those funny formats, I like to format myself and look for errors. I then follow the formatting with a disk test.

8. Mine came with a Samsung HD103UJ internally, but I suspect that varies.
They seem fine, I'll update this post if I run into problems. I hope to get a few years out of them. I do have to figure out what to do with the old 200-300MB drives. The 300 MB will replace a 200MB drive sitting in a firewire enclosure, but then I'll have to figure out what to do with the others. Maybe I can donate one to a friend who doesn't do backups yet ...

Update 5/6/09: I did run into problems. I discovered I couldn't start the system with the USB drive on. I have to restart with the drive off, then leave it off until startup is done. I don't think this was a LaCie problem, I suspect other causes.

Update 2/2/10: You can't open the #$!$!$ enclosure. Ok, so you can -- if you use credit cards to slightly separate the front, left, and right sides from their tabs then pull out the drive using string that's been threaded through the drive vents. Who the **** would ever make a sell a drive enclosure that couldn't be opened. LaCie, you are on my black list.

See also:

Use Reader's subscription trends to eliminate dead blogs

By chance I discovered today that Google Reader has an excellent feature for detecting and eliminating dead subscriptions.

It's not a new feature, so rather than add to the blog clutter with a screen shot I'll direct to a nice post with images ...
Using Trends In Google Reader To Manage RSS Overload

... The Subscription Trends can be very useful because it has a list of Inactive feeds where it shows rss feeds which haven’t been updated since months. Hence you just need to start clicking on the delete or trash button and start unsubscribing from those inactive feeds which are just a burden in your reading list...
I found a bunch that have been inactive for 2 years. Some people, like Tim Berners-Lee only publish every 6-18 months, but these don't fall into that category.

Great feature.

Sunday, December 07, 2008

Pixelpipe, Picasa and my Google password

I've used PictureSync for years to upload images from iPhoto SmugMug. Lately I've used a specific iPhoto plug-in for Picasa and SmugMug uploads, but the app did well when I needed it.

Now the author has launched a web service that performs similar functions: Pixelpipe. The beauty of the service is that he can create single high quality uploader for OS X or iPhoto or Windows, and then the middleware will route the image to one or more services.

The good news, at least with regard to Picasa, is that you don't have to provide Pixelpipe with your Picasa/Google password. That would be unthinkable -- I have far too much wrapped up in my Google password to hand it over to a 3rd party. [Update: see comments.]

Google has a good API for this sort of thing. If you're authenticated with Google, then Pixelpipe requests access and Google asks if you want to grant it. Pixelpipe never gets your Google info.

I'm sure not all the services work that way, but Google is the one I care about. My SmugMug un/pw is only for photos, but my Google un/pw is a big chunk of my digital identity.

Update 11/9/08: Signing up for SmugMug does require a un/pw, but that's a much smaller risk than handing over my Google credentials. I commenter tells us that SmugMug will also move to the "OAuth" standard, so even that won't be necessary. I recommend, however, that when you share a password like this you use either a unique password or, more practically, the password you use for all the stuff you don't really care about.

In the crash of '08 a big advantage of Pixelpipe is you can spread your risks. I pay for storage at both Picasa and SmugMug -- and I have lots of it. Might as well replicate anything I send to SmugMug at Picasa.

Saturday, December 06, 2008

Apple blocking email to some domains

I've had a Spamcop address for years.

Apple has been silently deleting email sent to Spamcop.net accounts, possibly it's a bug, possibly for fear that bot-captured MobileMe generated spam will add MobileMe to a blacklist ...
macosxhints.com - A caution on MobileMe outbound email domain filtering

This is a hint regarding a serious problem for MobileMe users: Outgoing mail via smtp.me.com may not actually be sent if it is sent to certain domains. If a message is caught in this domain filter, it is silently dropped without notification to the user. None of the recipients of the message will receive it, even if they are not in the filtered domain. This problem occurs with mail sent through Apple's Mail app, on the iPhone or on Mac computers. It does not happen when sending via the MobileMe webmail interface. So far, only spamcop.net has been identified as a domain filtered by smtp.me.com, but there may be others.

This problem is testable and repeatable as of this writing; you can test it yourself as follows. On a Mac or iPhone, use Mail to create a new message using your MobileMe account. In the To field, put support@spamcop.net, in the CC field, enter a valid personal email address, and in the Subject field, put test, then send the message. You will not receive the cc message, and you will not receive an acknowledgment from spamcop.net. Try sending from a non MobileMe account; you will receive both very quickly.

More discussion of the problem can be found in this thread on Apple's discussions site. This has been happening for months, apparently since the transition from mac.com. The problem has been reported to Apple, and apparently some in frontline support are aware of it, but others are not. In the meantime, all MobileMe users should be aware that their outgoing mail is apparently filtered by domain. If you're sending to a spamcop.net address, be aware that the mail will not be sent to any recipient, nor will you be notified of the problem.
It's the silent policy that's unforgivable. If this is policy rather than bug then Apple has jumped the shark.

So that brother who's not speaking to you any more? Maybe it's because you didn't respond to the desperate email he sent from his MobileMe account a month ago, the one Apple silently deleted.