December 1948: Force of Evil















Hm… that’s a very familiar name? Oh, yeah, that’s what I thought: Orson Welles did a movie with a similar name.

This is definitely not that one.

It’s John Garfield playing a mobster(ish) lawyer. It’s about the intricacies of running a numbers game. Basically everybody in this movie are crooks.

I don’t know. I didn’t connect with this movie at all. It’s just not very interesting.

I do like the cluttered, dirty look of the interiors. It’s either very thoughtfully done or it’s filmed on a perfect location.

Force of Evil. Abraham Polonsky. 1948.

Popular movies in December 1948 according to IMDB:

PosterVotesRatingMovie
48177.8Portrait of Jennie
32307.5Yellow Sky
43667.4Force of Evil
15577.3Command Decision
7157.3Enchantment
22037.0Adventures of Don Juan
2436.9The Feathered Serpent
29056.9The Paleface
9306.8Mexican Hayride
6266.8Jungle Jim

This blog post is part of the Decade series.

October 1948: June Bride



















Oops! I was supposed to watch this before the previous movie, but I got confused because the first copy of this DVD arrived broken and I had to get another one in and then etc.

But here it is! June Bride!

Bette Davis! And… people…

I didn’t think Davis did that many comedies, but this is at least the third funny movie I’ve seen her in during this blog series.

Ooh! Mary Wickes is in this! Mah favourite.

I guess this could easily have been a Katharine Hepburn/Cary Grant movie. It’s fun and easy on the brain. It’s so… welcoming? You know how this is going to turn out, and there’s a ton of jokes and stuff on the way there, and it’s just a perfect little movie.

The only slight problem is that Robert Montgomery isn’t quite Cary Grant. Bette Davis isn’t Katharine Hepburn, either, but she’s Bette Davis instead, which is even better!

This is just about perfect. I laughed a lot (out loud) and the rest of the time it’s exceedingly amiable. But there’s just something about it that makes it not be “Bringing Up Baby”. But it’s almost there. Almost. What spoils it is the anti-woman-as-boss subtext (and text).

But… it’s so much fun.

June Bride. Bretaigne Windust. 1948.

Popular movies in October 1948 according to IMDB:

PosterVotesRatingMovie
5757.5Quartet
6657.3Apartment for Peggy
11457.3June Bride
11037.2Moonrise
46607.2The Three Musketeers
7597.1Night Has a Thousand Eyes
16217.1A Song Is Born
6316.9Kiss the Blood Off My Hands
4826.8You Gotta Stay Happy
4636.1Inner Sanctum

This blog post is part of the Decade series.

November 1948: Unfaithfully Yours



He’s on the down low here.




















It feels like forever since I saw the previous movie. But it’s been only… two weeks? Last weekend was Copenhagen.

Oh wow! This is written, directed and produced by Preston Sturges, the director I wasn’t aware of before doing this blog series, but who’s become a new favourite after Christmas in July and Sullivan’s Travels and The Great McGinty! How weird that I picked out four of his movies when I started buying for this blog series. I did choose movies based on popularity, so I guess that his movies were extremely popular at the time, and I just somehow didn’t know…

Unfortunately, it looks like his directorial career was just 13 movies long, so including this movie, I’ve seen about one third of it. I’ll have to get the other movies later…

But! Me am excite!

This starts off delightfully. Rex Harrison is beyond perfection here, and there’s so many enjoyable little scenes here, like the orchestra rehearsal (I always love those bits) with the enthusiastic percussionist.

But… then we get to middle part of the movie, where Harrison imagines several ways to confront his wife about her supposed infidelity. I see what Sturges was going for, really: A fun explorations of various possible scenarios. It’s very writerly. But the possibilities aren’t that entertaining. Sturges is great a comedy telent, but the insistence of Harrison being the only one with any agency in this section makes you go “eeeh?”

That bit is more interesting than entertaining.

But then Sturges makes it all up to us with the hilarious prolonged (which seems like it’s filmed in one genius one long shot) scene where Harrison is searching the apt! I laughed until I cried.

This is a very funny movie, but it’s not perfect. I’m definitely going to see the rest of his films at some point.

And Terry Jones talks for fifteen minutes as one of the extras on the DVD.

And the half hour with Sandy Sturges is fascinating.

Well done, Criterion. *slow clap*

Unfaithfully Yours. Preston Sturges. 1948.

Popular movies in November 1948 according to IMDB:

PosterVotesRatingMovie
51217.7The Snake Pit
37257.7Unfaithfully Yours
32837.2He Walked by Night
64007.23 Godfathers
9367.2So Dear to My Heart
11877.0Scott of the Antarctic
15076.9Blood on the Moon
4076.9An Act of Murder
19806.8The Boy with Green Hair
5146.7That Wonderful Urge

This blog post is part of the Decade series.

CCCB: Downriver

For the baking today, I’m going to do a slight re-run: A few weeks ago I did a knead-free pan bread. Which turned out delicious. But it seemed to me that the recipe just had a few more complicated steps than seems necessary: You’re supposed to fold the dough a few times before doing the second proofing (but why?) and pre-heat the pot to 250C, which makes transferring the dough to the pot kinda on the eek side.

So let’s try to just skip those two steps.

So mix flour, salt and dry yeast, add water, and mix until it’s, well, mixed. Then let stand for 18 hours.

I floured up the pan…

Beat the dough down a bit…

Beat beat!

Transferred to the pan and let it proof there for 90 minutes.

There.

Then into the oven for 30 minutes at 250C with a lid on and then 15 minutes at 200C without.

Still not very dark… I think 200C is too low temperature…

Then catastrophe! The bread sticks to the pan! On the sides! Where the flour wouldn’t stick! Gah.

Let’s taste it anyway…

It’s very nice! There’s less of a crust at the bottom, which is both nice and less nice, since there’s little crust at the top, either. So if you hate crust, this is perfect, but who does that? Let’s try it again…

Once more, let the dough rise for 18 hours.

Then… tada! Put some baking paper into the pot. I wondered whether this would inhibit contact with the metal to the point that there wouldn’t be any crust on the bottom, but we’ll see…

Beat the dough down a bit and then scoop into the pan. Put the lid on and let it proof for an hour and a half in the pan.

Then into the oven at 250C for half an hour (with the lid on). Then take the lid off, turn the temperature down to 220C, and bake for 20 minutes more. (I shifted it up in the oven to give it a chance to get some crust going…

And yes! It’s almost perfect! I could have given it five minutes more for more crustiness, but it’s nice and fluffy, and still chewy and glutenous and very satisfying.

Hah! I knew those complicated steps in the middle were totally superfluous!

I should write this up properly as a recipe blog post some day with proper instructions, because the NY Times recipe is way too complicated, and doesn’t give a better result, in my opinion. The only difference is that there’s more of a crust on the bottom of the bread, but whatevs. Totally not worth the bother.

And now I have to pick a book from among the remaining eight unread-since-1992 books to read while eating some bread.

And the winner is… Downriver by Iain Sinclair!

Now, why haven’t I read this one? Or perhaps a better question is: Why have I bought it?

I think the answer to the second question is “it was on sale” and “I was thinking of Iain Banks”.

One is an SF author and the other in Iain Sinclair.

I love shopping at book sales, but I have noticed that that seems to make them less of a priority to actually read. And couple with the Iain/Ian sitch, it’s probably not anything I would ever have worked up the enthusiasm to try reading. And I don’t seem to have made the effort; the book has that “never been opened” feel.

Let’s read the first two pages together.

The most striking thing here is, of course, that the margins are tiny. Especially the bottom margin, which makes it physically unpleasant to read the book, because my fingers are constantly getting in the way of the text while reading.

I’ve got plenty of other books by Paladin (the literary but cheap imprint of HarperCollins, kinda like Picador (which is… Penguin?)), and they’re usually set better than this. Did they do it to keep the page count down? If there’d been normal margins this would probably have been a 500 page paperback instead of a 400 page one. Or did they just keep the typesetting from the hardback but cut down the paper size?

ANYWAY!

The other thing you noticed is that this is a very, very early-90s British novel. Very literate and excruciatingly erudite. Post-modernism was over, so we’re back to modernism, I guess?

But how’s the bread with the book? Well, if probably would have made sense with a darker, more complex bread, but this is a quite satisfying combination. The full-on sweet wheat experience coupled with random acts of bizarre violence and even weirder exigesises (that’s a word) on the meaning of each London neighbourhood complement each other well.

Downriver is very much a product of its time. Sinclair, for instance, predictably rails against nouvelle cuisine, as did all other older authors at the time, it seemed like. And the writing style is what I remember as being diagnosed at the time as “word processing novels”: It’s not that authors didn’t write long books filled with convoluted sentences before; it’s just that the word processor made it so easy to go over and over the text, revising sentences into maximum cleverness. And “[…] a side of bloody Aberdeen Angus, with all the coronary trimmings” is witty — but there’s just so much of this stuff. Everything is tortured into a kind of samey, erudite mush.

On the other hand, there’s amusing dog hatred like this (“the first bite is on the house”), so who am I to complain?

Hey! I know what he’s talking about here: Railway Time. Before railways were a thing in the UK, towns didn’t really feel the need to remain synchronised, so everybody just set their watches by whatever means were agreed-upon in that hamlet. But when railroads were introduced, you had to have a way to write accurate time tables, which led to the railways being the ones who standardised the time (i.e., Greenwich Standard).

So here Sinclair is taking that bit of trivia and using it as a starting point for imagining what perhaps could result in rebelling against that standard. Sounds cool, right? But as with any springboard in this novel, nothing leads anywhere: It all ends in some inconsequential petit guignol or other, and at this point I’m losing faith that Sinclair knowing what he’s doing.

Is it coked-up épater la bourgeoisie all the way through?

I guess this particular bit disappointed me more than all the other disappointing bits in this book because it reminded me of what Thomas Pynchon did with something not altogether dissimilar in one of his books (Mason & Dixon, I think?): The shift from Julian to Georgian calendars. Pynchon takes the factoid and really builds something on it; making it into this entire paranoid What Happened To Those Lost Eleven Days mystery, making the reader care because we trust that it’s going somewhere. And it kinda did!

It was thrilling.

This book isn’t. There’s plenty of funny bits (like Sinclair making a movie with The Corporation (i.e., BBC)), but it’s all so inconsequential.

And I can’t really imagine anybody wanting to read this at all in a few decades, because most of the references (and it’s a book that’s 75% reference) will be completely incomprehensible by then.

Let’s see what contemporary readers think! Let’s try Amazon, because that’s where people people hang out. (Let eye rolling commence.)

:

He’s not good at plot, satire, character, or structure in a work this length, but Downriver is still conventional enough in style (realism punctuated by historical visions) that it isn’t really a formal experiment, or a Thomas Bernhard-style dynamic rant either.

The highest-rated review here is a two-star review, which is pretty unique. It means that people really loathe this book.

This one’s pretty amusing, too:

Neither I nor anyone in my book-group liked this book, in fact I was the only one to finish it. I should explain that I downloaded the book so my husband, whose sight is not good could read it in enlarged type from my computer, I had the Penguin print copy. My husband read the first chapter and abandoned it. This was pretty well what the rest of the group did. I should say that there are ten of us and all have either a degree or a professional qualification, reasonably intelligent, well read people – all equally baffled. I realise the book has been well received and has won prizes but I think I can honestly say it is the only book that I have read and resented the time wasted in reading.

Yeah, I know, most of the other reviews are favourable, but then they usually are on Amazon.

Sinclair has a flair for doing very vivid descriptions (“The furniture was impregnated with ancestral flatulence (bad meat, verruca’d potatoes, cabbage boiled to a nappy-like consistency)”), and while you immediately get it, I started wondering whether some of the most imaginative things are standing expressions or what. I mean, “verruca’d potatoes”? While on one level obvious, on another… what would that really be? Warty potatoes? Is that a thing?

Nope: It’s a Sinclair Original. Or is he thinking of a different… dish… called something similar? The expression seems annoyingly familiar in a way.

The cover blurb on this edition is by Michael Moorcock, and the quote from Angela Carter is on the back. In the latest edition, Carter’s quote is on the front. It’s not surprising, but it’s kinda amusing.

I may have mentioned this before, but Sinclair’s go-to literary device is list-making. In this little paragraph I count… five?… lists of things. And there are chapters in this novel (or “tales” as Sinclair calls them for some reason or other; they’re definitely more chapter-ey than tale-ey) that have a surfeit of these paragraphs.

I say “I may have”, because it’s taken me a month to read the first half of this book, so the first bits I wrote in this blog post have been lost in the mists of my bad memory. I decided that enough was enough and forced myself to read the last two hundred pages over two evenings.

And either that helped a lot, or Sinclair changed tack for the last hundred or so pages completely. I mean, that’s what I expected him to do, sort of, so I’m not that surprised, but I acknowledge that the difference may be in the reader and not in the book.

I’ve read more than a handful of books where the author pummels the reader at the start of the book, and then eases up in the last bit, and then we all enjoy ourselves. It’s a Stockholm Syndrome thing combined with a masochistic streak in the reader: It feels so great when the tiresome bits of the novel are over.

Because the last hundred pages or so are a hoot. Sinclair goes all pomo and includes a section of (supposed) notes from the (perhaps imaginary) editor of the first chapter of this novel. Now we’re talking!

In the last chapter, Sinclair sends a letter to one of the characters in the novel and asks him to finish the book. Sinclair’s typewriter, you see, has broken down and he can’t find anybody to repair it.

So now “I” is a different person, which is a callback to the notes from that editor up there. It all ties together!

I’m so enthused by the ending (not shown above; that’s a few pages before it ends) that I contemplated starting to read the novel from the start again. But, by Emacs, no! No!

Bad book!

Bad!

A New Eval Server For Emacs

Emacs has a mechanism for client/server communication (and remote eval) that’s simultaneously too insecure and too secure at the same time.

Here’s the extremely convenient way to start a server:

(setq server-use-tcp t
      server-host (system-name)
      server-name (concat "foo-" (system-name)))
(server-start)

This will create a file (if called on a machine named “stories”)
called ~/.emacs.d/server/foo-stories with the following content:

192.168.1.53:41929 4021
fH?D+M=u=r@N1O^L-`c"c_GYUj%zj,,hc&9QGF+0}0;c}M3>Evc2SdH_N\`SSV\t

If you then say (on the command line)

$ emacsclient --server-file=foo-stories --eval "(tellstick-switch 0)"

the emacsclient binary will read that file, find the IP address and port number there, connect to that address, output the second line (which is a security cookie), and then the form to be evalled. The server will check that the cookie is what it’s expecting, and then eval whatever it’s asked to eval, and will return the result.

Now, for this to work, the host that you’re running the emacsclient on has to have access to that file, which means that (in practice) the entire thing is based on a shared NFS or sshfs setup, which makes it impossible (or at least extremely awkward) to use in many situations. So it’s too secure.

On the other hand, if you do have that cookie, you can make the server eval anything. And the communication is in clear text, so you can man-in-the-middle as much as you’d like. So it’s really very insecure and can’t be used any other place other than a totally locked-down, trusted network.

So Emacs should have a different way to do an eval server. Specs:

  • Don’t rely on a shared file system
  • Communication should be encrypted
  • The server should be able to limit the number of exposed endpoints

      So, ideally starting the server should look something like:

      (start-eval-server "lights" 8100 '(turn-on-lights turn-off-lights))

      where the first parameter is the name of the service, the second is the port number it should listen to, and the third parameter is a list of functions it will allow the caller to have evaluated.

      The client will typically look like:

      (eval-at "lights" "stories" 8100 '(turn-on-lights kitchen))

      For encryption, we could either do TLS or something home-brewed. And as all crypto experts tell us: Always roll your own crypto, so we’ll go with the latter one. But most of all because we’d really only be doing self-signed certificates, so TLS gives us a lot a problems without giving us security.

      But we could rely on an ssh-like setup with pinned self-signed certificates to give the client security, and client certificates to give the server security, but it’s… difficult to see how that could be made to work without a lot of handholding. And Emacs doesn’t have built-in tools to create certificates, anyway…

      Instead we’ll do symmetric encryption with a shared key. We’ll have ~/.authinfo entries like:

      machine lights port 8100 password s0pers3cret

      So… we’re not relying on a shared file system, but we are relying on pre-shared keys.

      I’ve put the results on github, and in addition to the Emacs client/server bits, I’ve also added a shell script that relies on openssh to do the encryption.

      $ ./eval-client lights stories 8710 '(+ 5 4)'
      9
      $ ./eval-client lights stories 8710 '(+ f 4)'
      Error: Got error message from server:
      (number-or-marker-p f)

      Seems to work!

      The client-server communication is plist-based, so they pass around things like:

      I think AES-256-CBC with PKCS#7 padding is a reasonable cipher to use for this type of thing, but I’m not an encryption expert. Does anybody have any input on that bit?

      The sexp specifies what cipher we’re using, so the protocol should be backwards/forwards compatible if we move to a different cipher in the future. The server should use the same cipher the client used, or if that’s not supportet any more, return an error.

      The error message is also encrypted, of course.

      Another design niggle: I’ve made the eval-at function throw errors when the server says an error has occurred, and if the error occurred when evalling the form, eval-at will throw the same error. Like:

      (eval-at "lights" "stories" 8710 '(+ t 2))
      -> (wrong-type-argument . "(number-or-marker-p t)")

      Does that make sense? I mean, eval-at itself didn’t have a wrong-type argument: It made a network connection, squirted some data over, and got some data back. So it was a success! But…

      What do you think?

      When I find some time (and after using this for a while to see whether it makes sense), I’ll probably propose adding this to Emacs and deprecate the old emacsclient stuff.