Overlooked E-Book Chapter: DRM Makes Monopolies (2012 CEA repost)

(Since a site redesign at the Consumer Electronics Association resulted in the posts I wrote for CEA’s Digital Dialogue blog vanishing, along with everything there older than last November, I’m reposting a few that I think still hold up. This one ran on April 17, 2012; since then, sci-fi publisher Tor Books–a subsidiary of the Macmillan publishing conglomerate–has gone DRM-free, but most of the industry has yet to take that step.)

Even if you’ve been following the e-books story for the past five years, it can be hard to define the heroes and villains of that plot.

First Amazon was the innovator, liberating us from paper with its Kindle. Then Apple was going to upend things with the iPad’s iBooks app and store. Now the Department of Justice says that the real problem is an unholy union of the publishers and Apple.

E-book reader appsIn an antitrust lawsuit announced last Wednesday, the DoJ charged Hachette Book Group, HarperCollins Publishers, Simon & Schuster, Macmillan, Penguin Group and Apple with conspiring to fix prices, to the disadvantage of consumers and Amazon.

The first three publishers have already agreed to a settlement that will block “most-favored nation” clauses that prevent e-book stores from discounting titles while allowing them to place other limits on the sale of their work. Meanwhile, Macmillan, Penguin and Apple continue to fight the suit.

It’s an immensely complicated issue, colored to a large degree by who you think is more evil. Is the problem the big publishers targeted by the DoJ’s suit, who allegedly colluded over dinners in expensive Manhattan restaurants? Or is it the gigantic Seattle retailer, which both controls a huge share of e-book sales and has been getting into the publishing business itself?

(A CEA press release posits a third foe, quoting association president Gary Shapiro calling the lawsuit “another sad milestone in our government’s war on American companies.”)

But the basic issue at stake here is not complex: ensuring vigorous competition in e-books that eliminates the need for court battles and consent decrees. And in that context, you can’t ignore how publishers have not just given Amazon a tool to build a monopoly but required its use.

This is the “digital rights management” restrictions required by publishers on e-book titles sold through all of the major online outlets–not just Amazon’s Kindle Store but also Barnes & Noble’s Nook store and Apple’s iBookstore.

DRM is supposed to stop unauthorized copying and sharing by making a copyrighted work playable, readable or visible only on authorized products. It’s not always a huge annoyance: DVDs and Blu-ray discs employ standardized–if easily circumvented–DRM that doesn’t limit you to player hardware or software specifically approved by a movie studio.

But in the world of digital downloads, DRM usually locks the “buyer” of a DRMed item into using only one vendor’s hardware or software.

(The scare quotes are necessary because the license agreements for many DRMed items stipulate that you don’t actually own those downloads.)

If you want to keep your future hardware and software options open, this favors doing business with the e-book store that offers the most DRM-compliant reading options.

That store, by a hardcover-thick margin, is Amazon. Beyond its growing family of Kindle reader devices, including last year’s Kindle Fire tablet, it also ships reader apps for Windows, Mac OS X, Linux (via a “Cloud Reader” Web app) iOS, Android, Windows Phone 7, BlackBerry and even HP’s now-abandoned webOS.

Barnes & Noble, by contrast, only provides Nook reader apps for iOS, Android, Windows and OS X. And Apple limits iBooks to its iOS devices.

Considering that evidence, where do you think somebody ought to shop?

So long as DRM stays part of the plot, every Kindle reader sold, every Kindle app installed and every Kindle title purchased will strengthen Amazon’s hand.

DRM can’t solve this problem, any more than any form of DRM tolerable to home users can abolish copyright infringement. But ditching it would erase the equation. If you could buy an e-book in a standard format that, like an MP3 music file, would be playable on current and imaginable future hardware, it wouldn’t matter which store sold it. There would be no lock-in; each sale would would not weigh so heavily on the next.

(As I wrote last spring, not having to worry about DRM-induced obsolescence would also vastly increase the odds of me buying e-books at all.)

The music industry figured this out years ago. Giving up on the DRM dream enabled a thriving competition between Apple, Amazon and other vendors of digital downloads, with no lock-in beyond the relative difficulty of syncing music from iTunes to a non-Apple device.

Other observers of the e-book business have been making the same call on personal blogs and on tech-news sites. One publisher, Hachette, may even be paying attention, as PaidContent reporter Laura Hazard Owen wrote last month.

But in much traditional-media coverage of digital content, DRM remains the lock that dare not speak its name. You can read a thousand-word piece about the slow market for movie downloads that notes a “lack of interoperability” without ever explaining why–or even using that three-letter abbreviation. Many of last week’s stories about Amazon, Apple and book publishers miss this point just as badly. And if we can’t properly identify this issue, we certainly can’t fix it.

About these ads

Belated updates to this year’s stories

You don’t have to run a correction when a story changes after you’ve written about it–but it is polite to follow up. Here’s a not-so-short list of updates to stories I’ve done this year.

Old stories sepia toneWhen I wrote that Google’s new, unified privacy policy would almost certainly be recast to let users opt out of having the company assemble a detailed portrait of them based on their use of separate Google services, I was wrong; that has yet to happen.

Sonic.net’s groundbreaking fiber-to-the-home service–a steal at $69.95 a month for 1 billion bits per second–seems to be off to a fine start in Sonoma County, but the planned expansion to San Francisco’s Sunset District is still on the way. It hasn’t shown up as an advertised offering on this Santa Rosa, Calif., Internet provider’s home-services page either.

Remember when adjacent-friend-discovery apps were going to blow up after their moment in the sun at SXSW in March? Didn’t happen. Facebook bought Glancee (and has yet to do much publicly with its technology), while Highlight seems to have fallen off the map (maybe I’m not hanging out with the right crowd?).

The ethics of outsourced manufacturing, fortunately, have stayed in the headlines since I wrote about them in March for CEA. And we may even be seeing legitimate progress, to judge from the New York Times’ story earlier this week recounting upgrades in pay and working conditions at contract manufacturers Foxconn and Quanta’s Chinese factories.

I’m still waiting to see comparable progress in liberating e-books from “digital rights management.” The sci-fi publisher Tor/Forge–a subsidiary of Macmillan–went DRM-free in July, but other branches of the major publishing houses have clung to this self-defeating measure. 

After saying so many good things about the car2go car-sharing service–and seeing that story get picked up in a few other places–I have to confess that I, ahem, haven’t used the service since. Capital Bikeshare is even more convenient and cheaper for trips under two miles, plus I need to make my way into the District to jump into one of car2go’s Smart fortwo vehicles.

I tempered my praise for Sprint’s Evo 4G LTE by wondering how long its users would wait to get Google’s software updates. Answer: almost six months, the time it took HTC and Sprint to deliver the Android 4.1 release Google shipped in June.

I was pretty sure I’d buy a Nexus 7 tablet after liking it as much as I did in July. But now that I own an iPad mini, that purchase seems like it would be redundant. Am I making a mistake there?

After teeing off on Apple Maps in the first chapter of my iPhone 5 review for CNNMoney.com, I have to give Apple credit for fixing the two worst flaws I called out. It now lists the correct address for the Kennedy Center as its first search result and provides a route to Dulles Airport that don’t cross any runways. But it still doesn’t know about Yards Park or the new 11th Street Bridges across the Anacostia–and the latter omission means its directions will now send you on a closed stretch of freeway.

My upbeat review of Samsung’s $249 Google Chromebook noted some build-quality concerns, in the form of a loose corner of the screen bezel. I found out the hard way that it’s more delicate than that; its LCD is now broken, and I don’t even know how. (We do have a two-year-old at home, but it’s also possible that I dropped something on it.)

My advice about enabling multiple-calendar Google Calendar sync on an iOS device by setting up your Google account as a Microsoft Exchange account will soon be obsolete. Effective January 30, Google will no longer support Exchange syncing on new setups (although existing ones will still work). Fortunately, it’s also posted instructions to enable multiple-calendar sync without the Exchange workaround.

3/23/2013: Updated the link for the car2go review after the post vanished in a site redesign and, for CMS-driven reasons that escape me, could not be re-posted at the same address. 

Four further Windows 8 issues

It’s now more than half a month since I reviewed Windows 8, and close to three weeks since I installed the shipping version of Microsoft’s newest PC operating system on my ThinkPad.

I’m still wrapping my head around how much time I’ll spend in its new interface (FYI, this weekend’s USA Today column covers ways to bring back a Start menu), but I’m also dealing with some smaller-scale issues. If you’ve got insight on how to fix them, please share it in a comment.

  • I’m hoping this is just my laptop, but WiFi looks outright broken. It keeps losing a working IP address, then won’t fix it on its own; I have to disconnect and reconnect manually. The problem can’t be my router (the Wirecutter-endorsed Asus RT-N66u), since no other device in my home exhibits this behavior.
  • The new Calendar app doesn’t seem capable of displaying anything but a default Google calendar account. That renders it useless to detail freaks like me who set up separate work and home calendars. I’d like to find a solution simpler than (I’m not making this up) impersonating an iPhone.
  • The desktop’s right-click “Send To” menu lists an option to send a document via fax–even though my laptop, like almost all sold now, doesn’t have a modem. (I hope the remedy I outlined in 2008 still works to remove that line.) The same menu doesn’t offer the Bluetooth file transfer that this ThinkPad does support, and which did appear in the Send To menu in Windows 7.
  • Is there really no way to have Windows set the time zone by the computer’s location? I’m tired of realizing I’ve had a computer stuck in Pacific time for days after I got home, even as OS X has been figuring out time zones more or less automatically since 2009.

 

A CalendarAgent cure

A runaway, memory-eating process in Mac OS X Mountain Lion that I’ve whined about on Twitter and in last weekend’s USAToday.com column seems to have returned to sanity.

At first, this CalendarAgent program had been a mild-mannered citizen on both my MacBook Air and on my older iMac. But a day or two after Discovery News posted my generally positive review of Mountain Lion, the iMac started locking up as CalendarAgent devoured as much as three to four gigabytes until I force-quit it with OS X’s Activity Monitor app.

The problem went away long enough for a cautious endorsement of Activity Monitor in Sunday’s USAT piece, but then it resumed. After a few days of getting bored with killing off this process two or three times an hour, I was trying to remember how to yank its execute privileges when I thought to check the Console app.

The repeated errors listed in this troubleshooting tool indicated that CalendarAgent was choking on my wife’s shared Google Calendar feed. I’d subscribed to that in Lion’s iCal without any issues (parenthood requires a non-trivial coordination of schedules), but Mountain Lion apparently had other opinions. I deleted the subscription from ML’s Calendar app,  added it back in the BusySync software I use to publish my own set of calendars to Google, and was soon treated to the welcome and overdue sight of CalendarAgent’s memory allocation dropping back to normal levels.

I still don’t know what exactly went wrong on the iMac; the MacBook Air didn’t have this problem even after I subscribed directly to my wife’s schedule in its Calendar app. Adding it under the “delegation” option for the Google account I’d already configured in that copy of Mountain Lion–but which I hadn’t set up on the iMac–didn’t result in any memory leaks either.

But if you’re tired of seeing CalendarAgent hold up your Mac, try changing how Google calendars get to the computer. Instead of adding a direct .ics subscription via Calendar’s Edit menu, subscribe to that feed in your Google Calendar, add that Google account in System Preferences’ Mail, Contacts and Calendars pane and you should see the subscription when you click Calendar’s “Calendars” button look under “Delegates.” Or revert from the delegation approach to a direct subscription. Let me know if that yields any better results.

How Windows (may have) killed my laptop

Little-known fact about me: For the past two weeks or so, I haven’t been able to use the ThinkPad I bought last summer. Here’s what happened, in 10 painful steps.

1. Months after successfully installing the Customer Preview of Windows 8 in a separate partition of my  ThinkPad X120E (and somewhat regretting that it required me to wipe out Lenovo’s recovery partition), I finally got around to trying to install the Win 8 Release Preview Microsoft shipped at the end of May.   At the tail end of a seemingly-nominal installation, the Release Preview installer, it got stuck at the “Finalizing your settings” screen. After waiting a few hours, I forced the machine to shut down and got a prompt at startup saying that Windows would undo the RP installation and return me to CP.

2. Because I am an idiot, and because I was getting fed up with some networking problems in Win 8 CP, I decided I’d try installing Release Preview again the night before I was heading out to San Francisco to cover Google’s I/O conference. Once again, the installer couldn’t get past “Finalizing your settings”–which is a funny place for Win 8 RP to halt, since it doesn’t preserve any of your settings in the first place.

3. Because I’m an idiot, I then tried wiping the Win 8 partition and doing a clean installation. The results were much worse:

4. After yet another restart that night–which by now counted as “early morning,” I got as far as the setup screens where Windows 8 asks you to set a live.com user account. It said mine was already in use on the machine. Trying different usernames only resulted in yet another stall

5. With no Win 8 system available and less than six hours remaining before my 8 a.m. departure from National Airport, I gave up, reverted to Windows 7, and resented its slower performance all week long.

6. Back home, I took yet another stab at installing Win 8 RP in early July. I got the same failure: a bogus report that somebody else was trying to use my Windows Live account on the system. (By then, I had gotten a few sympathetic e-mails from a Microsoft publicist promising help from people on the Windows team, but I never got more than an initial, friendly “what can I do to help?” response from them.)

7. For reasons I don’t remember precisely, I elected to switch back to Windows 7, saw that the system had a round of updates to install, and thought I’d proceed with them. Bad idea: The installation failed, leaving the computer unbootable in two different versions of Windows.

8. Successive attempts to use the disk-repair tools in Windows 7 failed; a Lenovo troubleshooting utility came up, complained that it needed me to log in, and demanded a reboot with an “Okay” button. No, it’s not okay. The disk-repair tools on the Win 8 installer’s flash drive didn’t do any better.

9. Because I’m not a complete idiot, I had a complete drive-image backup of my pre-Win 8 system (plus incremental backups from mid-July). But I can’t recover it: The Win 8 installer flash drive said it couldn’t restore a 32-bit disk image–even though there’s nothing bit-specific about that job. (Sometimes I think the only way the 32- and 64-bit editions of Windows could get along worse is if Microsoft farmed out the development of each to the Israeli Defense Forces and the PLO.) Edit, 2:43 p.m. And as of this morning, booting up the laptop yields the results you see in the photo above.

10. A 32-bit version of the Windows 8 Release Preview installer then said it couldn’t restore an image from an earlier version of Windows. So now I need to generate a Windows recovery-tools flash drive from a 32-bit version of Windows 7. And thanks to Microsoft’s unwillingness to offer a download of that program, this job apparently either requires a machine with CD or DVD burner or a painful amount of monkeying around with DOS commands.

But things could be worse. Wired writer Mat Honan, one of the smarter observers of technology around and one of the more decent human beings on the Internet, had somebody break into his iCloud account and use its remote-wipe feature to nuke his MacBook Air, iPad and iPhone–while also laying waste to his Twitter and Google accounts. So I’m not going to whine too much about this self-inflicted wound. Besides, I can always install Linux on the machine.

Epilogue, 10/21: In case anybody was wondering how this turned out, I was able to generate a USB-based, 32-bit Windows 7 system-repair volume using Into Windows’ directions. My only hangups involved having to disable Parallels Desktop from sharing USB volumes with OS X, followed by the exceptionally long time it took to format this USB flash disk in NTFS from the command line. Things worked as advertised otherwise, and I once again have a working Windows laptop–ready for me to try out Windows 8 once again when it ships next week.

 

Post-CES travel tech recap, 2012 edition

One of the things I try to do after each CES–catch up on sleep, do laundry and cook for myself for the first time in a week–is note how the technology I took with me to the show worked out.

I did that in 2008, 2009 and 2010 for the Post, but apparently I was too wiped out after CES and the Verizon iPhone circus too repeat the exercise last year. This time around, I had a lot of new hardware on hand, and I was also able to switch out some of the software I’d used in previous years.

My laptop at this year’s show was the Lenovo ThinkPad X120E I bought in April. I continue to enjoy its light weight (3.3 lbs.) and extended battery life (four hours of nonstop work is no problem), and at a wireless-hostile show like CES it’s handy to have a laptop with a conventional Ethernet port.

But this ThinkPad is not a fast machine. At all. I’ve been planning to replace its hard drive with a solid-state drive, which should help a bit; in the meantime, it’s not a bad computer for writing and simple photo editing. And, hey, it only cost $500 or so.

About photos: After ditching Google’s Picasa a while back–it was too much work getting at edited photos from inside other programs–I usually alternate between Microsoft’s Windows Live Photo Gallery and Paint.Net. I used the latter app almost exclusively at CES for a reason irrelevant to most of you: Discovery News’s blog format requires specific photo sizes, and Paint.Net makes it easy to crop a photo to a set proportion.

The best photos I took came from the oldest hardware in the image above, the Canon A570 IS camera I’ve had since 2007. Once I got home, I used Apple’s iPhoto to upload everything to a Flickr set.

I carried my own phone, the battered HTC model at the bottom left of the photo, but used it much less often than the two review models above it, also Android-based: a Samsung Galaxy Nexus on Verizon and an LG Nitro HD on AT&T. I’ll save my full evaluation of both for later, but I will say I’m not the biggest fan of the Nexus for its battery drain, the two freeze-ups I could only cure by removing its battery, and its maddening failure to save a timestamp on several photos. The Nitro, in turn, suffered from LG’s puzzling and unnecessary alterations to the standard Android interface.

I took most of my notes on Twitter, which was terrific for real-time sharing but inconvenient afterwards. As noted before here, Storify is useless as an archiving tool, since I’d have to drag and drop 300 or so tweets one at a time; I may try TweetBackup instead. I didn’t use Evernote as much as in prior years, and this time around its utility was undercut when the app crashed a couple of times, taking my most recent input with it in each case. That raises a question: Why does its Android version have a “Save” button at all when the Windows and Mac editions save every keystroke automatically?

I took along one extra item, a Belkin travel surge protector. Being able to turn one outlet into three–plus two powered USB ports–simplified recharging everything in my hotel room. It was also an enormous help (and a good conversation piece) in crowded press rooms.

The luggage you see underneath is a messenger bag called an Airbeltbag that I got as a Christmas gift. Yes, that’s a real airline seat-belt buckle you see latching it closed. The TSA guy at McCarran Airport in Las Vegas and a publicist for the Tripit travel-planning app got a kick out of that, but I also appreciated that this bag will not accidentally open once you insert the metal fitting into the buckle. I just wish the zippered pocket on the outside had some pouches on its inside for pens and business cards.

If you have questions about any of this gear–or, more importantly, my coverage of the show, including the wrap-up I did for the Consumer Electronics Association this week–you can ask me in real time at tomorrow’s Web chat. It runs from noon to 1 or so at CEA’s blog. This will be my first live Q&A since my finale at the Post back in April, so I’m looking forward to it. Talk to you all then?

Chromebook contemplation, cont’d.

At home, my wife and I have an iPad 2 parked more or less permanently on the coffee table–and, aside from Skype, we spend most of our time on this thing in its Web browser. Given that background, I should have liked Google’s “nothing but the Web” Chromebook concept. Right?

Wrong. I detail the reasons why I did not in my review for Discovery News, posted on Friday: The Samsung Series 5 machine I tested costs a little too much, weighs a little too much, is sometimes sluggish and is liable to turn into a brick should you stray beyond a wireless signal. I could have inventoried other gripes, such as its cooling fan’s distractingly loud whir, the overly-sensitive keyboard that repeatedly caused me to type duplicate characters, and the strange failure of Google’s Chrome Web Store to highlight Web apps that can run in an offline mode.

All of those aspects fell short of the optimistic presentation at this summer’s Google I/O developer conference that I watched on YouTube after the fact.

Don’t forget the inconvenient fact that Google already has a Web-friendly operating system that both runs  programs and saves data on your own device and automatically backs up everything online: Android.

But then there’s the possible market that Google didn’t pursue, the same one that Apple neglected when it introduced the iPad: the beginners who use a computer almost exclusively for Web and e-mail access, and never outside of the house. If you’ve had the privilege of providing Thanksgiving-weekend tech support for these first-timers, you’ll also admit that they probably don’t keep their applications up to date and often neglect to back up their data.

The Chromebook or something like it–a computer that updates itself, focuses on Web and e-mail use, and backs up everything automatically to secure Web storage–could serve that constituency well. But Google’s own marketing message, echoed by such retailers as Best Buy and Amazon, speaks right over this crowd:

Chromebooks are built and optimized for the Web, where you already spend most of your computing time.

There’s a chance left for somebody to connect with people who can’t give a billable-hours breakdown of their computing time and don’t throw around verbs like “optimize.” Right?

Ways to read the Google-Motorola Mobility deal

Did somebody forget to remind Google that August is supposed to be a slow news month? At 7:35 this morning, the Mountain View, Calif., company announced in a blog post by CEO Larry Page that it had agreed to pay about $12.5 billion for Motorola Mobility.

The sum involved alone sets this apart from the average tech merger. So do the relationships that would be upended by Google’s planned purchase of the consumer-oriented half of Motorola spun off in January. (Also unusual compared to other mega-mergers: How nobody leaked the news in advance.)

The reactions I’ve been reading this morning have fallen into three broad categories.

What does this mean for other Android phone vendors?

Motorola wasn’t the first company to ship a phone running Android, so it’s a little awkward to see Google bring it in-house while saying it will continue to license Android to such competing firms as HTC, LG and Samsung. That’s not how things usually work; normally, the operating-system developer either keeps the hardware business to itself (Apple) or lets other companies mess with circuit boards and batteries (Microsoft). There aren’t many cases of an OS vendor both shipping its own devices and licensing its software to competitors–although Palm did this for a while during the Palm OS’s heyday a decade ago, when Sony, Symbol and Handspring also shipped handheld organizers running its software.

The comical conformity of the supportive quotes from HTC, LG, Samsung and Sony Ericsson executives that Google trotted out this morning adds to the weirdness here. Veteran tech observer Dan Gillmor (like me, a former newspaper columnist) suggested that HTC and Samsung must be “absolutely furious.” But if Google uses its control of Motorola to strip out the bloatware that has gummed up too many Android phones, consumers may not mind. (Here’s a tip for Android phone manufacturers: Instead of wasting your time on proprietary software add-ons, get your developers and engineers working on battery life–the single weakest aspect of Android relative to other smartphone operating systems.)

Google says it will run Motorola Mobility as a separate shop, but AllThingsD’s Ina Fried and others have already suggested that it might do better to flip the company’s hardware business.

What about the non-phone half of Motorola Mobility?

Contrary to the “Mobility” moniker, this firm also makes cable boxes–a category of hardware both widely resented by consumers and one of the bigger obstacles to Google’s Google TV project. Commentators such as Tech.pinions’ Steve Wildstom, ZatzNotFunny’s Mari Silbey and GigaOM’s Ryan Lawler and Ryan Kim have all noted this morning that Google will now be in a position to ship a cable box with Google TV software built in–well, if the cable companies don’t mind shipping hardware that puts YouTube and other non-cable video services front and center on the subscribers’ TVs.

To me, this is the biggest reason for optimism about this deal.

What about the patents?

And here we have the most depressing aspect of this transaction–Google needs a stash of patents to defend Android against all the mobile-device patent lawsuits flying around. Motorola Mobility has 17,000 or so, and by gaining control of them Google can then threaten such opposing litigants as Apple and Microsoft with its own patent lawsuits–then propose to settle these fights with cross-licensing deals that extinguish the litigation but will do almost nothing to improve the products in question.

As the New Yorker’s Nicholas Thompson notes in a post this morning, this demonstrates how badly the patent system has failed to promote innovation:

Meanwhile, customers and shareholders will pay for the lawyers. And engineers will spend too much time worrying about violating someone else’s patents, and not enough time figuring out how to build the next magical thing.

He’s right. Suppose we didn’t have this overhang of too-obvious tech patents that should not have been issued in the first place; can’t you think of more productive uses for $12.5 billion than procuring an extra layer of legal armor?

Debugging a few defective defaults in Lion

My review of Mac OS X Lion for Discovery News represented a departure from long-standing practice: For the first time in maybe a decade, I reviewed a new Apple operating-system upgrade by installing it on my primary computer, not an expendable review machine.

As you can read in that writeup, the installation went fine on my late-2009 iMac, and I consider Lion to be a good deal overall. But I also disliked enough of Apple’s changes to prior Mac behavior that I found myself quickly undoing these new defaults–which is another thing I traditionally haven’t had to do with a Mac upgrade. Here are my major corrections:

Tame scrolling and zooming behavior. By default, Lion imposes two iOS aspects on OS X, “reverse scroll” and “smart zoom.” The former has you flicking two fingers in the direction of scroll on a Mac laptop’s trackpad or a Mac desktop’s Magic Mouse, as if either were the screen of an iPad or iPhone–i.e., the opposite of how you’ve scrolled on a computer until now. The latter zooms into a window if you tap two fingers on either input device–which I found myself doing unintentionally way too often. Fundamentally, I think you need a different user-interface grammar on a computer and a touchscreen mobile device. As long as the computer requires you control it through indirect manipulation–that is, by touching something besides the display–the mobile model breaks down. If you agree, you can undo both of Apple’s changes in the Mouse and Trackpad panes of System Preferences.

Show scroll bars. In general, I appreciate Apple’s willingness to edit out complexity and pare things down to the minimum. But hiding scrolls bars until you start to scroll with the mouse or trackpad seems an enormous mistake. In long documents, I felt lost and kept gesturing with the mouse to force the scroll bar to resurface. The effect was even more annoying in Web forms on a page and in other cramped, scrolling-required boxes. And to what benefit–to save a few pixels of screen real estate on the right edge of the window or form? No thanks, Apple. I’ll live with that clutter if it stops me from reflexively twitching a finger on the mouse every few minutes. To undo that mistake, click the button next to “Always” under “Show scroll bars” in the General pane of System Preferences.

Make the Library folder visible again. Apple somehow elected to copy one of Microsoft’s stupider interface decisions by hiding the Library folder in Lion. This is where your applications store their preferences, supporting files and some of their data–and it’s far more human-readable than the tangled array of hidden “AppData” sub-folders in Windows 7 that Microsoft hides from its users. Many common troubleshooting routines require access to your Library’s contents, but Lion hides the entire folder from view. To make it visible again, open the Terminal app and paste in the following command, then hit Enter:

chflags nohidden ~/Library

(That comes from a TidBITS post, but there are other ways to get at this folder. Macworld offers a full 18 workarounds.)

I may adjust more of Lion’s defaults as I get more familiar with this operating-system upgrade. I can also think of other changes I’d make on a laptop–for instance, setting Lion to show a messages when then screen is locked, then maybe adding Boxee to replace the Front Row media-browsing software Apple excised from OS X. But for now, these are the big three fixes I’d make to any Lion installation. What’s on your own list?

Update, 9/7, 4:17 p.m. Since writing this, I’ve had to change two other system settings:

  • To stop getting flicked from the Finder into the Dashboard by an unintended two-finger gesture, I unchecked the “Show Dashboard as a space” checkbox in System Preferences’ Mission Control pane.
  • After twice losing work when my attempt to scroll horizontally led Safari to assume I wanted to go to the previous page–after which this browser failed to return me to the blog post I’d been composing–I unchecked the “Swipe between pages” checkbox under the “More Gestures” heading in System Prefs’ Mouse pane.

Should I review a product that you can’t use?

Tuesday, Google launched a new social-media service called Google+ that almost none of you can use. A long blog post by engineering vice president Vic Gundotra about Google+ touts such flexible info-sharing options as “Circles,” “Hangouts” and “Sparks,” then offers an apologetic note in red, italicized text in the third-to-last paragraph:

We’re beginning in Field Trial, so you may find some rough edges, and the project is by invitation only. 

Well, then. A notice on the Plus sign-in page comforts shut-out users that “it won’t be long before the Google+ project is ready for everyone,” but in the meantime you may face a Twitter stream full of invited Plus users yammering on about the service and whether it’s a Facebook killer or just a Tumblr killer.

(Google has refrained from describing Plus as a killer of anything. Good idea: Calling your new product a “[fill in the blank] killer” usually guarantees its imminent demise in the market. Just ask all the companies that bragged about their iPod, iPhone and iPad killers.)

After an initial rebuff by Google’s PR agency and a subsequent appeal to a contact in the Mountain View, Calif., company’s D.C. office, I’m told that I have an invite on the way. (Disclosure: I’ve spoken at a couple of Google events.) When that arrives, I’m certainly interested to see how Plus works–and if it lives up to the hype or will flop just as badly as the enigmatic, since-shelved Google Wave communications application or the initially privacy-deprived Buzz sharing service. And yet: Since I probably won’t find my closer friends on Plus–and can’t extend them an invite–I’d only use a subset of its capabilities.

It’s not an easy question, but I’d like to know what you think. Should I join the in crowd and review Google+ for Discovery or anybody else? Or should I direct my attention this week to something that you can use without getting on a guest list? (The likeliest candidate: HP’s new TouchPad tablet.) Take the poll and explain your vote in the comments.

Update, 7/1, 12:41 p.m. Thanks for your votes. I went ahead with the Google+ first-take analysis, which you can now read on Discovery’s site.