Have I Met ‘Laplace’s Demon’?

A Technorati link tickle to my culinary commentary via the new discourse.net links feed clues me into a new blog entitled Laplace's Demon.

Here's some of what the proprietor has to say about him/herself:

Well, here it is. I've been following weblogs of various kinds for years because of my work. In fact, I would venture to guess that I have one of the longer reading-to-writing ratios among bloggers. The reasons for not keeping a blog have been easy.

I am a freelance purveyor of difficult to locate and valuable information. I know that is not exactly precise. One of the things I will need to do is work out how vague I must remain in terms of the kind of work I do. I don't break laws unless I really have to, and I try to remain ethical in the jobs I take, though once I agree to a job, I feel obligated to do almost whatever it takes to maintain my obligation to my client. I would say that I am a “troubleshooter” or maybe simply a “process consultant” (I've used both of these titles in the past.) But basically my job is to provide a client with the means to make a decision, and sometimes to help coordinate the solution.

Anyway, since my work involves providing an informational advantage to clients, a public blog doesn't mesh well with that. I don't advertise: my clients come to me because of a very strong reputation within various circles. I do have business cards, but that's about it.

And the person has a sport, probably a martial art. And s/he's seriously into crypotgraphy (“I've always liked to think about information through the lense of crypto.”)

Add to this s/he reads my blog, and I figure it's someone I know, at least vaguely, back from the cypherpunks list or CFP days.

I'm guessing male, maybe a little younger than me, just going on the braggadicio. And has lived somewhere where croc was on the menu…

Give me time, I could walk this cat. But that wouldn't be nice, would it?

This entry was posted in Discourse.net. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *