A lot of good he’d do them as a commander, if he lost his mind during the voyage.

Sure, he had plenty of books in the onboard database. Millions of them. And announcements of new books were sent to him by ansible; any he wanted, he could ask for and have them in moments.

What he couldn’t have was a conversation.

He had tried. After all, how different was the ansible from regular email over the nets? The problem was the time differential. To him, it seemed he sent out a message and it was answered immediately. But to the person on the other end, Mazer’s message was spread out over days, coming in a bit at a time. Once his whole message had been received and assembled, the person could write an answer immediately. But to be received by the ansible on Mazer’s little boat, the answer would be spaced out a bit at a time, as well.

The result was that for the person Mazer was conversing with, many days intervened between the parts of the conversation. It had to be like talking with somebody with such an incredible stammer that you could walk away, live your life for a week, and then come back before he had finally spit out whatever it was he had to say.

A few people had tried, but by now, with Mazer nearing the point where he would decelerate to turn the ship around, his communications with IF-COM on the asteroid Eros were mostly limited to book and holo and movie requests, plus his daily blip—the message he sent just to assure the IF that he wasn’t dead.

He could even have automated the daily blip—it’s not as if Mazer didn’t know how to get around their firewalls and reprogram the shipboard computer. But he dutifully composed a new and unique message every day that he knew would barely be glanced at back at IF-COM. As far as anyone there cared, he might as well be dead; they would all have retired or even died before he got back.