On: Why You Shouldn't Ignore Amazon's New FPS

A taximeter is an example of a UI where small charges accumulate, and you don't have to think about them individually.

I agree, but the example doesn't work for this case. You don't think about each 1/8th mile on a ride, so the charges aren't thought of individually.

But the issue here is content that isn't worth much, and you pay a tiny amount for each piece. My application to yc shares more thoughts on this.

I do. It hurts to see the meter keep increasing, especially at stop lights or a few feet from the destination.

The best way to make a metered scheme hurt less is to hide the current charge, like an electric meter does, and only expose the value once per month. (the best way to decrease power consumption would probably be to expose the current charge in very visible and realtime way)

Paul,

I just heard a great NPR story about a power company that is doing just this:

http://www.npr.org/templates/story/story.php?storyId=1247674...

I think I agree, but that's only because I'm a cheap bastard. Also, I often stop myself and realize I'm biased towards thinking a cab is a better deal when it is moving faster -- as if I can magically avoid traffic and stop lights when I'm driving.

But I suppose the point is that user pain needn't be rational.

Or, as the update to the post suggests, allow people to pay a large amount up front.

This works with current payment processing schemes as well: the accumulated result is no longer a micropayment. Examples: monthly subscriptions (WSJ, Basecamp), Amazon S3.

I see. Thanks.