All posts filed under “Firmware

Do you really need to print that?

Do you really need to print that?
Do you really need to print that?

This is not difficult to do, once you know how. Of course, it’s not terribly useful, since a) most people don’t read the display on a printer unless an error occurs, or b) you’re only likely to see it once you’ve already sent something to print.

Is this kind of very, very weak persuasion – actually worthwhile? From a user’s point of view, it’s less intrusive than, say, a dialogue box that asks “Are you sure you want to print that? Think of the environment” every time you try to print something (which would become deeply irritating for many users), but when applied thoughtfully, as (in a different area of paper consumption) in Pete Kazanjy’s These Come From Trees initiative, or even in various e-mail footers* (below), there may actually be some worthwhile influence on user behaviour. It’s not ‘micropersuasion’ in Steve Rubel’s sense, exactly, but there is some commonality.

Please consider the environment

I’m thinking that addressing the choices users make when they decide to print (or not print) a document or email could be an interesting specific example to investigate as part of my research, once I get to the stage of user trials. How effective are the different strategies in actually reducing paper/energy/toner/fuser/ink consumption and waste generation? Would better use of ‘Printer-friendly’ style sheets for webpages save a lot of unnecessary reprints due to cut-off words and broken layouts? Should, say, two pages per sheet become the default when a dicument goes above a certain number of pages? Should users be warned if widows (not so much orphans) are going to increase the number of sheets needed, or should the leading be automatically adjusted (by default) to prevent this? What happens if we make it easier to avoid printing banner ads and other junk? What happens if we make the paper tray smaller so the user is reminded of just how much paper he/she is getting through? What happens if we include a display showing the cost (financially) of the toner/ink, paper and electricity so far each day, or for each user? What happens if we ration paper for each user and allow him or her to ‘trade’ with other users? What happens if we give users a ‘reward’ for reaching targets of reducing printer usage, month-on-month? And so on. (The HP MOPy Fish – cited in B J Fogg’s Persuasive Technology – is an example of the opposite intention: a system designed to encourage users to print more, by rewarding them.)

Printing is an interesting area, since it allows the possibility of testing out both software and hardware tactics for causing behaviour change, which I’m keen to do.

Biting Apple

BBC News headline, 28 September 2007

Interesting to see the BBC’s summary of the current iPhone update story: “Apple issues an update which damages iPhones that have been hacked by users”. I’m not sure that’s quite how Apple’s PR people would have put it, but it’s interesting to see that whoever writes those little summaries for the BBC website found it easiest to sum up the story in this way. This is being portrayed as Apple deliberately, strategically damaging the phones, rather than an update unintentionally causing problems with unlocked or modified phones.

Regardless of what the specific issue is here, and whether unmodified iPhones have also lost functionality because of some problem with the update, can’t we just strip out all this nonsense? How many people who wanted an iPhone also wanted to be locked in to AT&T or whatever the local carrier will be in each market? Anyone? Who wants to be locked in to anything? What a waste of technical effort, sweat and customer goodwill: it’s utterly pathetic.

This is exactly what Fred Reichheld‘s ‘Bad profits’ idea calls out so neatly:

Whenever a customer feels misled, mistreated, ignored, or coerced, then profits from that customer are bad. Bad profits come from unfair or misleading pricing. Bad profits arise when companies save money by delivering a lousy customer experience. Bad profits are about extracting value from customers, not creating value.

If bad profits are earned at the expense of customers, good profits are earned with customers’ enthusiastic cooperation. A company earns good profits when it so delights its customers that they willingly come back for more—and not only that, they tell their friends and colleagues to do business with the company.

What is the question that can tell good profits from bad? Simplicity itself: How likely is it that you would recommend this company to a friend or colleague?

If your iPhone’s just turned into the most stylish paperweight in the office, are you likely to recommend it to a colleague?

More to the point, if Apple had moved – in the first place – into offering telecom services to go with the hardware, with high levels of user experience and a transparent pricing system, how many iPhone users and Mac evangelists wouldn’t have at least considered changing?

Another charging opportunity?

A knife blade cutting the cable of a generic charger/adaptor

Last month, an Apple patent application was published describing a method of “Protecting electronic devices from extended unauthorized use” – effectively a ‘charging rights management’ system.

New Scientist and OhGizmo have stories explaining the system; while the stated intention is to make stolen devices less useful/valuable (by preventing a thief charging them with unauthorised chargers), readers’ comments on both stories are as cynical as one would expect: depending on how the system is implemented, it could also prevent the owner of a device from buying a non-Apple-authorised replacement (or spare) charger, or from borrowing a friend’s charger, and in this sense it could simply be another way of creating a proprietary lock-in, another way to ‘charge’ the customer, as it were.

It also looks as though it would play havoc with clever homebrew charging systems such as Limor Fried‘s Minty Boost (incidentally the subject of a recent airline security débâcle) and similar commercial alternatives such as Mayhem‘s Anycharge, although these are already defeated by a few devices which require special drivers to allow charging.

Reading Apple’s patent application, what is claimed is fairly broad with regard to the criteria for deciding whether or not re-charging should be allowed – in addition to charger-identification-based methods (i.e. the device queries the charger for a unique ID, or the charger provides it, perhaps modulated with the charging waveform) there are methods involving authentication based on a code provided to the original purchaser (when you plug in a charger the device has never ‘seen’ before, it asks you for a security code to prove that you are a legitimate user), remote disabling via connection to a server, or even geographically-based disabling (using GPS: if the device goes outside of a certain area, the charging function will be disabled).

All in all, this seems an odd patent. Apple’s (patent attorneys’) rather hyperbolic statement (Description, 0018) that:

These devices (e.g., portable electronic devices, mechanical toys) are generally valuable and/or may contain valuable data. Unfortunately, theft of more popular electronic devices such as the Apple iPod music-player has become a serious problem. In a few reported cases, owners of the Apple iPod themselves have been seriously injured or even murdered.

…is no doubt true to some extent, but if the desire is really to make a stolen iPod worthless, then I would have expected Apple to lock each device in total to a single user – not even allowing it to be powered up without authentication. Just applying the authentication to the charging method seems rather arbitrary. (It’s also interesting to see the description of “valuable data”: surely in the case that Apple is aware that a device has been stolen, it could provide the legitimate owner of the device with all his or her iTunes music again, since the marginal copying cost is zero. And if the stolen device no longer functions, the RIAA need not panic about ‘unauthorised’ copies existing! But I doubt that’s even entered into any of the thinking around this.)

Whether or not the motives of discouraging theft are honourable or worthwhile, there is the potential for this sort of measure to cause signficant inconvenience and frustration for users (and second-hand buyers, for example – if the device doesn’t come with the original charger or the authentication code) along with incurring extra costs, for little real ‘theft deterrent’ benefit. How long before the ‘security’ system is cracked? A couple of months after the device is released? At that point it will be worth stealing new iPods again.

(Many thanks to Michael O’Donnell of PDD for letting me know about this!)

Previously on the blog: Friend or foe? Battery authentication ICs

UPDATE: Freedom to Tinker has now picked up this story too, with some interesting commentary.

Uninnovate – engineering products to do less
Image from

I’ve just come across a very interesting new blog,, which focuses on the phenomenon of “engineering expensive features into a product for which there is no market demand in order to make the product do less.” The first few posts tackle ‘Three legends of uninnovation‘ (the iPod’s copy restrictions, Sony’s mp3-less Walkman, and Verizon’s rent-seeking on Bluetooth features), Microsoft’s priorities (patching DRM flaws vs. security flaws that actually damage users), Amazon’s absurd new Unbox ‘service’ and ‘Trusted’ computing for mobile phones. The perspective is refreshingly clear: no customer woke up wanting these ‘features’, yet companies direct vast efforts towards developing them.

In a sense the ‘uninnovation’ concept is a similar idea to a large proportion of the architectures of control in products I’ve been examining on this site over the last year, especially DRM and DRM-related lock-ins, though with a slightly different emphasis: I’ve chosen to look at it all from a ‘control’ point of view (features are being designed in – or out – with the express intention of manipulating and restricting users’ behaviour, usually for commercial ends, but also political or social).

Uninnovate looks to be a great blog to watch – not sure who’s behind it, but the analysis is spot-on and the examples lucidly explained.

Use of RFID in DRM

A CD with its functionality destroyed using GHz-range radio frequencies

Via Dave Farber’s Interesting People, a brief New Scientist article outlines Sony’s continuing obsession with restricting and controlling its customers (the last one didn’t go too well):

“A patent filed by Sony last week suggests it may once again be considering preventing consumers making “too many” back-up copies of its CDs…

Sony’s latest idea is to place a piece of monitoring hardware inside the CD. Its patent suggests embedding a radio-frequency ID chip that could be interrogated wirelessly by a PC or CD player. The chip would record the number of times the disc was copied and prevent further recordings once it reached the limit. The device could also be fitted to DVDs. Whether Sony will turn the patent idea into reality remains to be seen.”

Read More

Ed Felten: DRM Wars, and ‘Property Rights Management’

RFID Velcro?

At Freedom to Tinker, Ed Felten has posted a summary of a talk he gave at the Usenix Security Symposium, called “DRM Wars: The Next Generation”. The two installments so far (Part 1, Part 2) trace a possible trend in the (stated) intentions of DRM’s proponents, from it being largely promoted as a tool to help enforce copyright law (and defeat ‘illegal pirates’) to the current stirrings of DRM’s being explicitly acknowledged as a tool to facilitate discrimination and lock-in — and the apparent ‘benefits of this’:

“First, they argue that DRM enables price discrimination — business models that charge different customers different prices for a product — and that price discrimination benefits society, at least sometimes. Second, they argue that DRM helps platform developers lock in their customers, as Apple has done with its iPod/iTunes products, and that lock-in increases the incentive to develop platforms.
Read More