Tuesday, February 14, 2006

The Glass is Half Empty

It's not quite that bad, but I just learned that the ship date for my Mac Book Pro has been moved from February 15th to February 28th (with the processor speed increased, of course).

I'm disappointed, but the completely unrelated good news is that I was able to repair the G3 that was rapidly becoming unusable. The display had been crapping out (black was being displayed as red), and QuickTime display was illegible, but I found a replacement display on eBay for $75 (promising no red "washout"), and I was able to disassemble and reassemble the G3 in a couple of hours today and it's as good as its six-year-old new.

Obsolete before it ships?

Not really, but...

It's a running joke (or sometimes a genuine complaint) in the PC business that PCs become obsolete too fast, almost as quickly as you buy them.

I ordered a MacBook Pro a few weeks ago, and have been waiting for to ship "by February 15th", according to the estimate on the Apple Store.

Today, Apple announced that the new MacBook Pros are shipping, and a higher speed processor is available as a build-to-order option. If I had wanted the fastest possible processor, the machine that hasn't shipped yet would be less than I wanted.

On the other hand, I had opted for the slower (1.67 GHz) processor vs. the faster 1.83 GHz, and Apple's announcement includes the news that I'll be getting a 1.83 GHz model instead.

The glass is definitely half full.

Why did I opt for the slower processor? A few reasons:

  • My current laptop is a 400 MHz G3 (Pismo). Relatively speaking, the 1.67 GHz Core Duo would have seemed blindingly fast. (My other regularly used machine is a dual 2 GHz G5, so I think I can handle it.)

  • I deliberately ordered the G3 just a few weeks before it was end-of-lifed by what turned out to be the G4 Titanium PowerBook, and caught the price drop as Apple cleared the inventory. The G3 suited me perfectly, and cost me nearly $1,000 less than a new TiBook would have. Not that I didn't drool over the TiBook, but I was on a budget. I'm just not convinced you get the best bang for the buck at the very top end. (Don't ask about the G5...)

  • Similarly, I had economized on the Pismo and bought the 400 GHz model instead of the available 500 MHz; again, I never regretted it.

  • One of the best performance improvements I applied to the G3 was to replace the hard drive with a faster (and quieter) 5400 RPM drive. On the basis of that lesson, I paid for a 7200 RPM drive (vs. the now-standard 5400) for the MacBook.

  • I also decided that money was better spent on more RAM than GHz, so I upgraded to 1 GB on a single DIMM (to leave room for expansion). (The G3 was eventually upgraded to 640MB, a little beyond the Apple-specified "maximum" of 512MB.)

  • We'll see how it turns out. Soon, I hope.

    b r r r e e e p o r t

    Not sure why I'm playing along, but Scoble is asking for blogs containing "brrreeeport" to test blog search engines. Maybe we'll also get a sense of how many people really care...

    Thursday, February 09, 2006

    Google and Privacy

    Michael Arrington at TechCrunch notes with alarm the release of Google Desktop 3.0, which enables desktop search from across computers by maintaining a search index of your local files on Google servers. (It should be noted that use of the feature is optional).

    Arrington links to a Gillmor Daily discussion about the privacy implications of this. I usually like listening to these guys, but I thought their opposing positions both missed the point, badly.

    Arrington seems to be most worried about the potential for abuse by The Government, especially in the wake of Google's agreement to share information with the Big Bad Bush Administration.

    Gillmor scoffs at the concern, not because he doesn't think the current administration is indeed The BogeyMan, but because (if I understand him correctly) They have more and better means to abuse our privacy anyway, and the value of storing our data in the internet cloud is so compelling that the way to deal with it is to manage how we manage ownership of that data, and specifically asks why Google's storage of indices is worse than storage of private data via online backup.

    What I Find Troubling About This

    To take the last point first, here's the fundamental difference from my point of view: in the case of backup, I build a package of my backup data locally, encrypt it to make in (hopefully) impenetrable, then move it into the cloud. In the case of Google Desktop, my data is moved to Google's servers in a form where they can peek into it, in the name of search.

    I find this troubling. Google promises not to share my data with anyone. Fine, let's accept that and hope that Google is better at protecting it than the Boston Globe, of whose idiocy I was affected.

    Being able to search my data and affirmatively determine whether it contains references to certain keywords conveys information about me, even if the content of that data is not explicitly shared. Google does not do this, as far as I know; they certainly don't let anyone to ask "who has references to Al Qaeda or Barry Manilow" in their index?" But there's a spectrum of possibilities between complete privacy and outright sharing.

    As for government surveillance, challenging the government on its exercise of power is always healthy, but Arrington and Gillmor are so focused on it that they race each other to proudly label themselves as unpatriotic for wanting to retain their privacy; it's actually comical.

    While it's legitimate to be vigilant to ensure that we don't become a police state over the next 20 years, I also try to make sure that many small, annoying things aren't done to me on a daily basis between now and then.

    Up to now, Google has commercialized what they know about your interest as expressed by your search queries, and there's an strong element of fairness to this. If you go to Google and type "Barry Manilow" into the search box, you're transmitting your interest in the subject to Google, and they use this to deliver discreet ads with your search results that reflect your expressed interest.

    But increasingly, Google has the ability to color their interactions with you based not on your expressed intentions, but on the interests implied by the content of your email (if you use GMail), and now, the content of your private files. I don't think they are doing that now, but the potential is there, and I don't see that their current privacy policy prevents that. Even if they don't publish lists that say "RetiredMidn is interested in these topics" or "RetiredMidn is one of the people interested in this one topic", my interactions with Google can now be adjusted based on the electronic equivalent of the contents of my underwear drawer.

    Controlling Attention Data

    Gillmor is an advocate of giving the user control of this information about themselves, as exemplified by the principles espoused by AttentionTrust.org, with which he is intimately involved. Their notion is that the user ought to have control of the information about their attention, what is included in it, and how it is shared.

    In the discussion with Arrington, Gillmor seems content that users can exclude specific folders from Google's net-based indexing, and that this event will trigger the concern and discussions necessary to convince Google that they need to provide better control of this information. I'm less confident about this. Desktop search is most valuable when it can help you find stuff in obscure places, and constraining the search indexing reduces the usefulness. It also places the burden on the user to proactively identify all the places sensitive data is now or might possibly land in the future, and I don't think this is realistic. In theory, the user has the control; in practice, it's too easy not to exercise it.

    Capability May Not Be Intent, But That Hasn't Stopped Us Before

    Years ago, ActiveX came into being because the techies at Microsoft (and elsewhere) thought it would be cool and powerful to enable program code to be embedded in emails (and later, web pages). There were some clever ideas; when someone received an email requesting them to perform an action, the email could embed code that would perform, or support the user's performance, of the requested actions. There were all sorts of scenarios drawn up where this could be a significant productivity enhancement.

    In hindsight, most people agree that this was a Bad Idea: used maliciously, this capability became a conduit, perhaps the most exploited one, for spreading malware. The consequences are that the innocent have been inconvenienced. For example, my wife is an elementary school teacher, and in the name of security she is now prevented from installing and trying out many potentially useful pieces of new software, which is what is supposed to make computers flexible and powerful.

    Like Microsoft, Google is, I think, optimistically focusing on the potential value of desktop search across the network, and in their enthusiasm is blind to the potential for abuse. I hope I'm wrong.

    To those who think, like Steve Gillmor, that it's alarmist to worry about the potential for abuse instead of the deed itself, I would point out that wiretapping and gun control laws are based on the same premise: good intentions aren't sufficient protection.

    I'm not proposing that Google Desktop be outlawed. (When Google is outlawed, only outlaws will Google.) But I'm not installing Google Desktop (I use Macs anyway; small sacrifice), and I don't use GMail for my personal correspondence. (*)

    (*) I do use GMail to collect the traffic from related public mailing lists, so I can search them in one place.