Lift Up Your Hearts!

I didn't expect to like this Wall Street Journal article about the board game, Risk. Unlike nearly all the rest of my extended family, I am not a fan of most board games, especially if they involve intricate strategy and take a long time to complete. It's even worse if I'm playing with people who care whether they win or lose. If I ever played Risk, it wasn't more than once.

But I enjoyed the article, and I understood most of it because of having been surrounded by so many people who love to play the game. The author makes a good case that playing the game taught many of us "everything we know about geography and politics."

A certain kind of brainy kid will reach adulthood with a few general rules for foreign policy: Don’t mass your troops in Asia, stay out of New Guinea, never base an empire in Ukraine. It is the wisdom of Metternich condensed to a few phrases and taught by the game Risk.

The game could be played with up to six players, each representing their own would-be empire, and could last hours. The competition could turn ugly, stressing friendships, but we all came away with the same few lessons. ... In the end, no matter who you call an ally, there can only be one winner, meaning that every partnership is one of convenience. If you are not betraying someone, you are being betrayed. Also: No matter what the numbers suggest, you never know what will happen when the dice are rolled. ... Regardless of technological advances, America will always be protected by its oceans. It is a hard place to invade. What they say about avoiding a land war in Asia is true. It is too big and desolate to control. Ukraine is a riddle ... stupid to invade and tough to subdue because it can be attacked from so many directions, making it seem, to the player of Risk, like nothing but border.

Here's my favorite:

The best players ask themselves what they really want, which means seeing beyond the board. I learned this from my father in the course of an epic game that started on a Friday night and was still going when dawn broke on Saturday. His troops surrounded the last of my armies, crowded in Ukraine. I begged for a reprieve.

“What can I give you?” I asked.
He looked at the board, then at me, then said, “Your Snickers bar.”
“My Snickers bar? But that’s not part of the game.”
“Lesson one,” he said, reaching for the dice. “Everything is part of the game.”

And finally, one amazing side note. The man who invented Risk, French filmmaker Albert Lamorisse, also created the award-winning short film, The Red Balloon.

I like Shutterfly, for making books, greeting cards, and other photo-themed gifts. My experience with them hasn't been perfect, but they have a good track record, both in general and in customer service when things go wrong. Recently I had a good, and somewhat amusing, experience with the latter.

On November 27, I placed an order for a set of greeting cards. It was shipped the next day. with an expected delivery date of December 5.

My experience has generally been that Shutterfly items arrive earlier than the expected delivery. But not this time.

I had ordered several sets of cards, and the ones that were to be Christmas gifts arrived in plenty of time. This order was for my own use, and there was no hurry, so I did not pay much attention to it. But eventually I realized that December 5 had come and gone with no sign of my order.

So I checked out its tracking, and discovered that it had been travelling via UPS, in partnership with the USPS, and had arrived in Orlando November 29. By 1 p.m. of that day, it was "enroute to USPS."

And there it remained.

I tried to trace it via UPS, but they said it was no longer their problem, since as far as they were concerned, the USPS had it. But no one could give me a USPS tracking number, so that was a dead end. I didn't worry; as I said, it wasn't a Christmas gift, and I could wait for it to make its slow way through the busy holiday traffic.

By December 23, however, I decided that my package was hopelessly lost, and contacted Shutterfly. The Customer Service rep was great, and immediately sent me a replacement order, high priority. It wouldn't arrive till after Christmas, but I was fine with that.

Sure enough, on December 29, exactly one month after the original order had arrived in Orlando, I held in my hand the familiar, bright orange Shutterfly package. The cards looked great, and I was happy.

Imaging my surprise, however, when a couple of hours later the doorbell rang, and I was handed another bright orange Shutterfly package, identical except for the shipping label. Inside were the same lovely cards!

Yes, on the same day that the replacement order arrived, so did the original order! Who knows where it was hiding all that time? As far as Shutterfly's tracking is concerned, it's still "on the way." But someone in the system found it, kicked it loose, and "neither snow, nor rain, nor gloom of night" came through once again.

It's that time again: Here's my annual compilation of books read during the past year.

• Total books: 83
• Fiction: 65 (78.3%)
• Non-fiction: 16 (19.3%)
• Other: 2 (2.4%)
• Months with most books: February (27)
• Month with fewest books: A tie between April and October (2 each)
• Most frequent authors: Brandon Sanderson (24), Randall Garrett (23), Brian Jacques (9). As with last year, Randall Garrett is an anomaly; he makes such a strong showing because he was the subject of a particular focus and—thanks to the way I've accounted for them—his books are generally quite short. Actually, each of the runaway leaders was part of a special focus.  Both Jacques (with his Redwall series) and Sanderson (with his seemingly infinite collection) combine very interesting stories with books that my grandchildren are currently reading, which makes them especially attractive.  These two authors made up 40% of this year's total reading.  That's by number of books; if you count pages, Sanderson is immeasurably ahead.  (That's "immeasurably" as in "I am not going to bother to do the calculations.")

Here's the list, grouped by title; links are to reviews. The different colors in the titles only reflect whether or not you've followed a hyperlink. The ratings (★) and warnings (☢) are on a scale from 1 to 5, with 1 being the lowest/mildest. Warnings, like the ratings,  are highly subjective and reflect context, perceived intended audience, and my own biases. Nor are they completely consistent. They may be for sexual content, language, violence, worldview, or anything else that I find objectionable. Your mileage may vary.  Ratings in red indicate books I found particularly recommendable this year.

Our church is having an event this New Year's Eve. I'm not thrilled, but we'll probably show up for a little while, since it starts early. But until the very end, it's just a party. I love the idea of starting the new year with a Communion service, but I have to confess  I don't love it enough to stay up past midnight tonight. I'd have done that for a Christmas Midnight Mass (which we didn't have) but not on this night—being on the road on a night that our society dedicates to the abuse of alcohol seems just dumb.

That said, my favorite New Year's Eve event took place 30 years ago, at another church service: the baptisms of our children. It wasn't an Episcopal church, but we made it as much like the Episcopal service as we could. Including the baptismal candles, which they have made a point of relighting every New Year's Eve since then. As New Year's Eves go, that one is unsurpassable.

For a while, we enjoyed a quiet get-together with friends on the day, but our dislike of staying up late and driving with drunks on the road made that less attractive over the years. Sometimes we're with my brother's family in Connecticut at this time of year, and that's always great: lots of good food, an evening of game playing (for those who like games), a few Top Gear videos to watch together (back when Top Gear was good), and just being with family. We don't have to drive anywhere, and are free to doze on the couch whenever we feel  like it. Good times.

But for the most part, this is my idea of a great New Year's Eve:

However you celebrate (or don't),

May  God  bless  you  greatly  in  2023!

Having overheard someone questioning why Coventry Carol was included in our church's Lessons and Carols service earlier this month, I knew it was time to reprise our story of why this song of immeasurable grief belongs in this season of festive joy.

Coventry Carol is an ancient song that tells a story almost as old as Christmas. The events take place sometime after the birth of Christ—after the arrival of the Wise Men, from whom King Herod learns of the birth of a potential rival, and decides to do what kings were wont to do to rivals: kill him. Don't know which baby boy is the threat? No problem, just kill them all.

This song is a lament, a lullaby of the mothers of Bethlehem, whose baby boys would be killed in what came to be called the Massacre of the Innocents. (Jesus escaped, Joseph having been warned in a dream to get out of Dodge; the others are considered the first Christian martyrs—people whose association with Jesus led to their deaths.)

Lully, lullay, Thou little tiny Child,
Bye, bye, lully, lullay.
Lullay, thou little tiny Child,
Bye, bye, lully, lullay.

O sisters two, how may we do,
For to preserve this day
This poor youngling for whom we do sing
Bye, bye, lully, lullay.

Herod, the king, in his raging,
Charged he hath this day
His men of might, in his own sight,
All young children to slay.

That woe is me, poor Child for Thee!
And ever mourn and may,
For thy parting neither say nor sing,
Bye, bye, lully, lullay

Why sing such a gloomy song at Christmas?

Several reasons, maybe. Chief of which is that the Christian Christmas is not like the secular Christmas. It is, indeed, "tidings of great joy," but it is complicated, messy, profound, anything but simplistic and lighthearted. It breaks into the midst of a broken world, and even Jesus' escape from death here is only a short reprieve. There's more to Christmas than the joy of new birth, or even "peace on earth, good will to men." We have to tell the whole story.

Twenty years ago, as the world was beginning in earnest to "ring out the tidings of good cheer," our firstborn daughter gave birth to our first grandchild.

Isaac lived two days.

It was in that season of unspeakable grief that the haunting Coventry Carol touched me as none other could. Frankly, I could not handle all the happy songs about a newborn baby boy; with Coventry Carol I felt merged into an ancient and universal grief, the grief that made Christmas necessary. 

Until the Day when all is set right, there will be pain and grief that won't go away just because the calendar says it's December. The last few years, especially, have wounded us all and broken not a few. This reminder that the First Christmas was not a facile Peace on Earth and Joy to the World, and that the first Christian martyrs were Jewish children, is for all whose pain threatens to overwhelm them.

Blessed are they that mourn: for they shall be comforted.

YouTube is not exactly reliable when it comes to recommending videos for me to watch, but look what showed up in my sidebar tonight:

As most of my readers know, I'm a huge fan of J.R.R. Tolkien's Lord of the Rings books, but not of the movies for a number of reasons. Even though I feel the film story line and characterization are a betrayal of the spirit Tolkien put into his world, I can't deny that there are parts of the movies that are excellent, from the New Zealand setting to the music, and of course I adore this version.

The big news is—there is no big news.

Nicole, now a tropical depression, is marching through Georgia rather more peacefully than General Sherman did. It slipped by to the west of us, and although we were theoretically in its grip for much of yesterday, it might have been an unnamed, minor storm, or possibly the effects of a hurricane passing far off at sea. The rains gradually diminished as the day progressed, and only an occasional gust of wind reminded us that something meteorological was going on.

We even went out for lunch in the middle of it all, and noticed only a slight diminution in traffic, although some places were still closed. Not too surprisingly, these were mostly government, church, and medical facilities, institutions not known for being able to turn around on a dime and say, "Okay, it's all good, let's re-open."

There is still risk of flooding, as runoff from already-saturated ground fills already-flooded rivers, but in our own neighborhood we travelled on dry ground the roads that had been so devastatingly flooded by Hurricane Ian.

Were this a century ago, my relatives who lived in Deland would likely have thought it a pretty ordinary day, at least until they heard news from my great-grandfather, the mayor of Daytona Beach. That city, along with others on the east coast, took some significant property damage, though no loss of life.

We are grateful.

Nicole, having become a hurricane long enough to harrass the western Bahamas and southeast Florida, made landfall around 3 a.m. just south of Vero Beach, a little further north than we expected. I had been awakened a few times during the night by wind gusts and the steady sound of rain. When I got up for real around 4:30 (normal for me), it was clear that our decision to take in the wind chimes, orchid, and trash cans last night was the right thing to do, but everything else was fine.

Of course the day is not over yet; Nicole is currently around Davenport (where we ourselves were on Monday for a friend's birthday party), and heading our way at about 14 mph. But it's now a tropical storm again, and although we are still warned of gusts up to 70 mph, sustained winds where we are look to be less scary than predicted. (I'll take that!)

I greatly enjoyed a few early-morning hours on our back porch, watching what we've had so far from the storm. Because our porch faces west, and the winds were largely from the east, I enjoyed a safe haven with barely an occasional light breeze, while watching the trees whip around somewhat impressively.

Once again, the biggest damage to our neighborhood is likely to be flooding, but we haven't ventured out yet to investigate.  Power outages usually come after the storm has passed, so we're not out of the clear there by any means.

Many thanks to those of you who have expressed your concerns, and offered their prayers.  I expect to do at least one more update, more if anything untoward happens.

Nicole is not a hurricane yet, but looks to become one in the Bahamas, and come on shore around Ft. Pierce in the early hours of tomorrow morning, aka the middle of the night tonight. I fully expect to be awakened at least once by our ear-splitting weather radio, hopefully for nothing more serious than that for which it awakened us during Hurricane Ian, and again two days ago.

We were briefly out of "the cone" but are currently back in it, as the predicted path shifts. Of course, the area of strong winds is a lot broader than the cone, and we've been feeling its rain for days. They are still predicting peak sustained winds of 45-60 mph with gusts to 75 mph, which is a "strong tropical storm." Nicole should be off our west coast by 1 p.m. tomorrow, and I'll give an update when I can.

There's a reason we hadn't packed the generator up from the last storm. I hope we don't need it, but with the storm coming straight at us, the ground once again completely saturated, and rivers and lakes still at flood level or very close....

We're still pretty much prepared from last time, though we're waiting till tomorrow to bring things in from outside. My concern when I awoke this morning was for an appointment I had this afternoon at 3 o'clock. Based on today's weather, there was no reason I shouldn't have been able to take it: there's almost no wind yet, and the rain has been steady but not heavy. However, when it was clear that many businesses were deciding to close early, I chose to go in the morning as a "walk-in." I say I chose, but really, I didn't feel I had much choice. Call it a nudge from God, call it hyperactive anxiety—but I couldn't rest about it, and decided I might as well wait for hours there than be unproductive at home. As it turned out, they were able to fit me in quickly and I even made it to the library to pick up The Bellmaker, before it closed at noon.  It was definitely the right decision.

Now we wait, hoping that our decision to wait till morning to batten the final hatches turns out to be a good one, too.

Happy Columbus Day!

In my heart, Columbus Day is always October 12, no matter what the calendar says. It's a better day, anyway, because we get mail today, and we didn't Monday.

If you don't think Columbus Day is worth celebrating, feel free to have a miserable day. Or not. Your choice.

It began a month ago, when we made the decision to switch our phones from AT&T to Spectrum. Spectrum is our cable internet provider, and now offers mobile phone service, which through some sleight of hand is actually Verizon.

We had been loyal AT&T customers all our long lives, from back when "Ma Bell" was the only way to go for long distance; through the forced breakup of AT&T that led to our move to Florida in the mid-1980's and Porter's 17 years of employment with the company; to our very first cell phone ("car phone") in the early 90's, and many changes of phones and phone service since—wherever we were, whatever our phones, it was all AT&T. I do know that there's really nothing left of the original AT&T besides the name, but still, it hurt to leave.

But recently we had two very annoying and expensive experiences with AT&T:

• "I don't care what the e-mail we sent you says, our system says differently so we're not going to honor the deal you signed up for."
• "Whatever made you think that making a call using Wi-fi Calling would not cost an arm and a leg when calling Switzerland?")

When these were quickly followed by

•  A shockingly high price increase,

that was it for the camel's back. Spectrum/Verizon offered a price/service combination that was such an improvement we decided it was worth trying.

However, our AT&T root system was apparently stronger than we knew.

We made the account switch with ease, or so it seemed. When our new SIM cards arrived from Spectrum, Porter's phone made the switch without a hitch. My phone, on the other hand....

As I powered my phone back on after inserting the new SIM card, the phone insisted that I enter an unlock code. This was a bit concerning, as the phone was supposed to have been unlocked already. Thus began more than three weeks of struggle (mostly Porter's heroic work) with AT&T, Spectrum, and Samsung.

We tried multiple times to unlock the phone using AT&T's website. A few days after each try, we'd get an e-mail telling us there was a problem.

Next level: phone calls. Many phone calls, countless hours. Each time we'd be assured that an unlock code would come by e-mail "in a few days." Each time the result was failure.

By this time, we were on vacation in Connecticut, thankful to have one working phone as we continued the adventure. Hoping that being physically present might move things along, we took my phone to the local AT&T store. Although the sales clerk was friendly and tried to help, there wasn't much he could do as a simple reseller of AT&T services. So he sent us to a true AT&T store, half an hour down the road in Branford. As we drove along, we tried another phone call, ending up on hold for about an hour and a half in total, before giving up.

The Branford guy started our visit optimistically: "I can fix anything." Before we were done he'd gone so far as to drag the District Manager from another store out of a meeting to help. She was able to confirm that there was absolutely no reason we shouldn't be able to unlock the phone, and she said it shouldn't be necessary for us to drive to her store. We were grateful, as it was at that point rush hour, which in New Haven is nothing to be trifled with, and would have more than doubled the nominal 20-minute drive time. She escalated our problem up to highest priority, and we left the store armed with her telephone number. 

Unfortunately, in the end, even that came to nothing. We went home to Florida.

Several more phone calls and no progress later, we learned that, while our problem was stilll "highest priority," it no longer had a person attached to it but had been kicked back to being assigned to a group. Knowing AT&T's trouble ticketing system from the inside out, Porter recognized this as the place insoluble problems are sent to die.

I'm half convinced the various companies hired someone's creative writing class to invent the reasons why they couldn't give me an unlock code.

• (AT&T) "Something went wrong, try again."
• (AT&T) "We can't give you a code because we can't get one from Samsung."
• (Samsung) "We can't give you a code because we don't do that; the code has to come from the carrier." (True, but it turns out that there is actually a code that must come from the manufacturer to the carrier, first.)
• (Samsung) "We can't give you a code because you bought the phone directly from us and all our phones ship unlocked already." (True, though it appears AT&T subsequently locked it, because we paid for it through our AT&T bill.)
• (AT&T) "We can't give you a code because your phone is already unlocked." (That's what their system kept telling them, but it was clearly untrue.)
• (Spectrum) "We can't help you because it was locked by AT&T."
• (AT&T) "Success! Here's your unlock code." That might have been encouraging, except that the code was simply "0." Right. An unconvincing null. With infinitesimal faith that it would work, we used up two of the five allowed attempts (after which the phone would become "permanantly locked") trying both a simple 0 and enough 0's to fill in the requested number of digits. As expected, it didn't work.

My all-time favorite of their excuses I reproduce below:

What on earth was the problem? We had bought the phone new, directly from Samsung, and it's hardly been out of my presence ever since. For a long time, this one had me looking over my shoulder for the FBI. Hey, if they can raid the private residence of a former U.S. president on the flimsiest of excuses, what chance do the rest of us have? Are they still mad about the grainy picture of Osama bin Laden that so annoyed Facebook?

After learning that there was little to no chance of our problem getting out of the trouble ticket graveyard, Porter employed a different tactic, one I would have given no chance at all of making any difference: He filed a complaint with the Federal Communications Commission.

Have you ever wondered if governmental agencies actually do anything to earn their tax dollars? In this case, Porter's complaint generated near-immediate action, first by the FCC itself and then by AT&T.

I'm not kidding: in a very short time he received both an e-mail and a phone call from the office of the president. (Of AT&T, that is, not Joe Biden.) A friendly and competent-sounding person promised to see what she could do.

At this point we began seriously debating how we would proceed if AT&T decided they were spending 'way too much money on this problem and offered to give us a new phone instead. It was not an easy decision. The lower-level folks who had no power to do so were, of course all in favor of giving away a phone. The mid-level folks grudgingly acknowledged that it might be a possibility, but only if I turned over my phone to them first. There was absolutely no way that was going to happen; my phone was not going to leave my possession until I had a working replacement with all my settings, apps, and data successfully transferred.  Maybe they would be willing to send the new phone to our local AT&T store until we could successfully make the switch.

Then there was the problem of which phone? I didn't expect an upgrade to a more current phone: my Galaxy S9, even though it was the lastest thing in 2018, is now so old it's almost useless as a trade-in. I'd have been happy with a new S9, but do they even have any of those hanging around? Would I be offered a used, reconditioned phone, and would I be okay with that?

As it turned out, all that speculating was unnecessary. In only a few days, Porter received an e-mail with a non-zero unlock code.

Not without some trembling, we carefully, step by step, followed the instructions and entered the code into my mobile phone.

I have a working, Spectrum-serviced, cell phone.

A small part of me is reluctant to admit that. It was surprisingly easy to get along for nearly a month without one. Certainly it helped that I could do almost anything I wanted to with my phone, as long as I had wi-fi, which these days is nearly ubiquitous, even here.

I only missed a couple of things:

• The ability to make non-911 phone calls. (All phones work for emergencies, or so my phone told me.) If I were designing something named "Wi-Fi Calling," it would work using wi-fi when one does not have cell service. I mean, otherwise, what's the point? Especially if carriers are going to charge the same price as for regular cell calls (see above). But I wasn't the designer on that one. Even though I drove for decades without having cell service, I couldn't drive this past month without being aware of the lack.
• The ability to send and receive texts. That, too, should be possible over wi-fi.

Grateful as I am to have a fully-functioning phone, I have to say that a month without phone calls and texts was not all bad, It was rather nice, in fact—especially during political season.

Many thanks to all those ordinary people at AT&T and other places who were friendly and cheerful, and truly seemed to be doing what they could to help us. And deep gratitude to the one person at AT&T who somehow cut through the nonsense and got the job done. As Porter said in his thank you note to her, "If everyone at AT&T were as effective as you are, we'd still be customers."

I took a COVID test this week.

I try to avoid those things as much as possible: I hadn't taken one since April, when I needed it to get back into the United States. But I picked up a mild cold in Connecticut, and as sometimes happens I have a cough that is still hanging on. I never seriously thought it might be COVID, especially since our grandson (who was hit harder than the rest of us), had tested negative.

However, I couldn't deny that the symptoms I experienced were exactly the same as when I genuinely had COVID-19, back in April. When I sing with them on Sunday, my fellow choir members will be happier if I can assure them that my cough is not due to the Dread Disease. So I took the test.

No surprises. It was negative.

Apparently, getting random colds is a thing again. I suppose we could go back to dropping all contact with the outside world—which gave us two years totally free of such annoyances. But I'm sure our immune systems are much better for the stimulation.

We have a lot of experience in our little choir, from many churches in many states over many years. What we saw in last Sunday's bulletin is completely unprecedented, anywhere, in our combined experience—at least as far as we all could remember.

We were so excited, we all gathered at the altar after the service to have our picture taken with the flowers and the donors!

(Appreciation is greatly appreciated.)

Happy Bastille Day to our French and Francophile friends—though frankly, for at least two of you this day is more about your own birthdays. Happy Birthday, then!

The French still celebrate the Storming of the Bastille, despite the fact that—as evidenced by their extremely strict gun regulations—they don't want such a thing ever to happen again. They're no more hypocrites than we are: there are a great many people in this country who work frantically to disarm Americans, yet still indulge in our own Independence Day activities.

Those in power are not fond of sharing that power with anyone who might unseat them. I'm certain that King Louis XVI wasn't keen on the idea of an armed citizenry.

I'm not all that fond of the idea myself. I'm just a lot more frightened of the alternative.

On Saturday, for some reason that I have forgotten, I wrote this story to Facebook instead of here. Usually I cross-post the other way around. Below is the story, followed by an update.

Here's a reminder that when we pray at church for those travelling in the next week, it is no meaningless exercise. Travel is dangerous!

Early this morning, Porter was driving a choir friend to the airport. At about the time he should have been on his way home again, my phone rang. It was Porter, asking if I could find out if something major had happened at the airport. They had been almost there when traffic ground to a halt and Google claimed the road ahead was closed. It sent them on a very long detour to the other side of the airport, where traffic had also ground to a halt.

I tried several sources of news with no success. I looked on Google Maps and saw that indeed the traffic was a total mess all around the airport. But I couldn't help except with moral support, as the clock ticked away the minutes before our friend's flight. Porter saw people getting out of their cars and walking to the airport.

Eventually, however, Porter crept his way to the B side of the airport, where he could drop our friend off. He then drove to the nearest Panera Bread and ordered himself a drink and a breakfast soufflé, figuring there was no point in making the (nominally) 45-minute drive home if he was just going to have to turn around and pick our friend up again.

By that point we knew that whatever the problem was, it wasn't inside the airport, because the security lines were short, and soon our friend let us know that he did make it to the gate on time.

It wasn't till after Porter was home and I could see him, safe and sound, that the news caught up with the story and we learned that the cause of the mess was a fatal car crash immediately ahead of where our guys had been shunted to the alternate route.

Seconds earlier and they might have been in the crash themselves; seconds later they would not have been able to take the detour and been like the drivers who reported sitting in their cars for two hours.

One thing I know for sure: I'm really, really glad that I already knew our guys were fine by the time I read that two people had died in a car crash exactly where and when I expected them to be.

[knees still weak at the thought]

UPDATE: I know now that the guys actually didn't just miss the accident, which occurred at 2:30 a.m. I'm still trying to wrap my mind around how a one-vehicle accident at that hour could have the roads still closed six hours later. Granted, it was nasty—four people in a Land Rover had crashed into a concrete barrier and flipped into a canal. Two passengers were killed, the driver and another passenger had minor injuries. The surprise isn't that two people were killed, but that two people only had minor injuries after smashing into concrete and ending up in a canal.

Despite—probably because of—Google making some bizarre suggestions for the detour, our guys' delay was apparently much less than most people's. And it wasn't just passengers who couldn't make their planes—lots of flights were affected, I assume because flight crews were stuck in the traffic, too. We don't have the whole story yet, but I know the takeoff of our friend's flight was delayed by half an hour, and since his connection was going to be a tight one anyway, he probably missed that. However, we do know that he arrived safely at his destination.