And I've been thinking about this quite a bit since then. What would I have done in that situation?

There's several options available to you. You can simply leave. You can be quiet about it, or be loud about it. You can stand up and speak about about it. You can ask the representatives of the conference in the room to step in and throw the bum off the stage.

Or, of course, you can do nothing, which is what most of us do most of the time.

Speaking out is hard. It's uncomfortable. It's deeply awkward. You'll look like an idiot. People will resent you. You'll have nasty things said about you online. It's much easier to sink back into your chair and let it happen - perhaps even participate in the nervous laughter around you.

But it only takes one person to stand up and say, no, this isn't on. This isn't how we do things in our community. You are on the outside, and you won't be allowed to paint us all with your brush.

Several years ago, I was attending a conference. As it happens, it's one of my favorite conferences. I've spoken there numerous times, and a lot of my friends attend. This particular time, my wife was attending with me.

We stepped into an elevator and another conference attendee was in the elevator wearing a tshirt depicting a woman pole dancing, with the text "I support single mothers".

I didn't say anything.

I think about that frequently. Why didn't I say anything? I'm a respected member of the community. My words carry weight there. I could have made a point that he was making people uncomfortable. That he was being disrespectful to the women in the community. That, since he was on the way up to his room, perhaps this was a good time to change his shirt. I could have used my privilege as a man, as a community elder, as a speaker at the conference, to right a small wrong.

But I didn't. And so I was complicit in the women that were made uncomfortable, or didn't come to the conference next year, because this guy thought his little joke was more important than someone's dignity.

He was the middle schooler, and I was the grownup in that situation. When my son misbehaves in public, it is my job to correct him and make sure it doesn't happen again. This is not to say that he's not responsible for his actions - he is - but I'm responsible for my response. The young man in the elevator was responsible for his tshirt. He chose to put it on. I presume he thought it was funny. It was my job to educate him, and I missed the opportunity.

And so we come back to you, and how you respond to indignities and injustices that happen around you. Did anyone in the audience stand up and protest? I don't hear them on the video. Was anyone even uncomfortable? Did anyone think that it was a problem?

If you're one of the elder statesmen who, like me, attend a lot of these events, and have a loud voice in the community, you have an obligation to stand up to this kind of thing, rather than sink into your seat and cringe. Stand up. Say for the whole room to hear, we don't do that kind of thing here. Risk being uncomfortable. Risk feeling awkward. Risk people being angry with you, or not understanding why you thought it was important to spoil a "harmless prank" or "just a bit of fun." Because it's not fun to the people who are being othered by this kind of behavior. And, in the long run (and the not-so-long), it is harmful to the future of our industry when we make it clear that women aren't welcome.

Various of our friends post articles now and then about the joys of marrying young and growing up together in harmony. The most recent of these was here, and is a beautiful story, full of sweet moments and good advice.

We are truly, deeply happy for our friends who had that experience.

There were times, of course, when we each, separately, assumed that they were lying, just as we were, in order to tell the story that everyone around them expected to hear. Twenty years on, it's both delightful and deeply humbling to see that they weren't - or that, even if they were, they managed to work through it and build happiness on top of the sad times.

But that's not our story. This one is for those of us who married young and watched it fall apart. Because you need to know that there’s more to your story than regret, and watching other people get lucky and find happy--hard, but happy--the first time around.

We both married young and unwise, and, although beautiful things came from those years (most obviously our beautiful, brilliant, talented older children), those decisions were terrible, terrible mistakes. Mistakes that could have been avoided, at least for one of us, if we'd listened to those same dear friends, and actually opened our eyes to the various red flags.

But, as we mentioned, we were young, and so very unwise.

Our mistakes are put squarely in front of us, every single day of our lives. This is true even though my now-wife and I have found in each other a best friend, and each day is better than the one before. Our mistakes influence decisions we make every single day. My mistakes have a profound effect on my wife, and hers on me.

And so when we see these articles encouraging people to jump in with both feet while they're young and unwise, naturally, we don't have the same teary-eyed response that others might have. Our teary-eyed response is for years and opportunities lost. It is for the pain that our kids go through every time they talk about their parents, every time someone asks what their mailing address is, every time someone invites them to a birthday party and they have to figure out which home they're in that weekend. For the confusion that our youngest has when her siblings go away for days at a time and she doesn't understand why, and the stab of anger and sadness and whatever-it-is when she asks why she doesn't get to have two houses, too.

Please, don't stop posting those articles, particularly if they are written as compassionately as the one mentioned above. The compassion for those of us who failed made that one readable. And the advice in the article was also relevant to those of us trying to make another go of it.

And please don't ever, ever hear us saying that if you are having a hard time of it, move on and you'll find someone better. We are, as the Bible puts it, "as one escaping through the flames." Neither of us recommends it to anyone. Every time someone comes to us, as the presumed expert, to ask our advice about whether they should leave their spouse, it breaks our hearts. We can identify with the pain, but it is a jump from one flame to another, and nobody can tell you which fire is worse.

Please also understand if we don't "like" or comment on posts about early marriage on Facebook, or share them with our friends. Even on the other side of our respective tragedies, the flames can still burn.

But as we said, our story does not end with us looking back over our shoulder at what was irretrievably lost.

If you share our brand of brokenness, you need to know (if you haven’t learned it already) that there’s more to it than regret. There’s opportunity for healing and redemption (with or without remarriage); to see the glory of a Thing Made Whole Again, and when the light shines through the pieces, it’s a breathtaking sight to behold, especially from the Inside.

Problem: Vanilla Forums sends out email on new messages and when a message has been commented on. The subject line is:

[Forum Name] rbowen started a discussion

or

[Forum Name] rbowen commented on your bookmarked discussion

Because the actual forum post title is missing, the chance of someone actually responding is pretty low.

So, I want to modify the subject line. However, Vanilla doesn't provide a simple way to do this, so I'll have to hack on the code itself.

Seemed like a good idea to document this, since I see the question asked a few places, but no answers.

Solution:

1) Track down where that subject line is created.

Looking for the various phrases, it appears that the subject lines are created in applications/vanilla/settings/structure.php, around line 180. Look for the comment:

// Insert some activity types

2) Where is the email sent?

After some digging, it appears that this is actually done in the EmailSubscribe plugin, which would have been more evident, I suppose, if I had been the one that set up the forum. Oh well.

The trouble is, however, that the subject line is created in applications/vanilla/settings/structure.php (around line 180) as part of the event logging, and so we may have to recreate the subject line ourselves, rather than using the one that's passed in.

Around line 79 of plugins/EMailSubscribe/default.php, you'll see:

$Email->Subject(sprintf(T('[%1$s] %2$s'), Gdn::Config('Garden.Title'), $ActivityHeadline));
and I think that's where I'm going to want to ctually set the subject line. If it's a new post, I want it to be
POST_TITLE
, whereas, if it's a reply to a post, I'll want to have it be:
Re: POST_TITLE
So, first pass is to just do this:

When I finally got printing working on my new HP5520, I discovered that apps like xpdf that print by invoking lpr directly would only work if I told them to use 'lpr -Php5520', which was a hassle. After some poking around, I discovered that the Cups web interface, at http://localhost:631/ let me set the default printer quite easily. Of course, you can do this via some config file or other, but this was easier. Here's how you do it.

15 years ago, I attended the first OSCon, in Santa Clara, I think. I was there for the Perl content, and managed to pay my way by giving a full day tutorial on the Apache web server. Amazingly, they kept asking me to come back and do it again, and I gave one talk or another every OSCon until 2006, after which I skipped a few years. Last year I made it back to OSCon again, and I'll be going this year too.

This will be my first OSCon when I have no speaking responsibilities at all, although last year I only had a BOF, not an actual session.

This year, I'll be working the Red Hat booth, and the OpenStack pavilion, as well as, hopefully, a little bit at the Apache Software foundation booth. Between that, and various evening events, and various meetings, I expect this to be another OSCon where I don't actually sleep. I can't quite manage that like I used to in 1998. But I'm really looking forward to the conference this year, and seeing the folks that I only see at OSCon.

Last evening we had a small gathering around the fire pit to read poetry. I started with Pablo Neruda's Ode to Ironing. My Beloved asked if there was an ode to shoelaces, and thus began an odyssey. For the rest of the evening, I read nothing but odes to shoelaces.

I was asked this morning for some information that I get asked for a lot, so it seemed reasonable to write it down once so that I can refer to it later.

I don't claim to be an expert on this. If anything, this is intended to be resources for folks who aren't experts, and don't really aspire to being experts in audio production, but just want to know how to do a podcast, or other simple recording, with whatever tools they might already have, or can get free or cheap.

So, here's the response I sent. No doubt I'll update this from time to time.

The cool thing about podcasting is that you don't have to be a recording expert any more. Just have to have some patience and a decent microphone.

I'm a big fan of the Blue microphone line. Their USB microphones are supported by whatever OS you're running, and are so simple to use. It's a little bit of an investment, but the results are worth it.

Just don't try to use one of those headphone/microphone combo things. They are universally awful.

I often do an interview on Skype and use a skype recorder to capture it. Unfortunately, the recorder I was using is Mac only, and I've recently switched to Linux and am having no luck, so far, getting anything working to record skype calls.

For editing, I have tried a number of things, and keep coming back to Audacity. It is simple to use, and has all of the tools that the more expensive options. It's available for whatever OS you're running.

Quick notes about my video editing woes, so that I don't have to keep repeating myself

I'm recording the original content with RecordMyDesktop, which outputs ogv format. Have had no luck with other recording tools. ffmpeg seems to be the one most frequently requested, but getting it to record a window, or even a frame, rather than the whole screen, has evaded me so far.

OpenShot: Nice interface, but audio is always either double-speed or garbled, even when I record it externally (Audacity) and then try to insert it.

Avidemux: Won't open ogv video, and I can't get the necessary libraries/plugins to install.

It's mostly in pretty good shape, although at some point the stem broke off, and has been repaired, and has broken off again. We're investigating ways to fix it without further damaging it. It's very cool to have a piece of Internet history, although I expect that now that I've told the world where it is, someone on the Trademarks team will say that they should have it. ;-)