Adventures in creating online content

My younger sister the children’s librarian has inspired me. Her library is closed, or course, so she’s creating online content by uploading an average of a new video every day to the Harvard (Mass.) Public Library Children’s Room Youtube channel. So far, she’s got a simple craft project, story time that parents can do with young children, and she’s reading aloud the entire Alice’s Adventures in Wonderland.

I like several things about Abby’s videos. First, they’re a great supplement to Zoom calls — some of us are getting Zoom burnout, and it’s nice to be able to watch a video when YOU want to watch it. Second, they’re Goldilocks videos — not too long, not too short, but just the right length. Third, they don’t put a big burden on parents — the crafts project can be done by kids on their own without parental supervision, kids can watch the installments of Alice on their own, and the story time for young children has them doing what they’re going to be doing anyway which is sitting in a parental lap.

So I repurposed this Youtube channel, where I already had some religious education videos. I added a video we used in last Sunday’s service. I created a couple of playlists, one for crafts (Abby’s craft video is included there), and another for story time (Abby’s Alice stories are going there, because Alice in Wonderland is a sacred text). I’ve got a children’s librarian from our congregation half convinced to do a story time, I’m planning a story time (I think I’ll read aloud from an old edition of the Jataka Tales), there will be more crafts projects.

Blog readers, if you know of some videos that you think would be appropriate to share on this Youtube channel, please send me the links. I can’t promise to put everything up, but I’d really like to see your suggestions — send them to danharper then the little “at” sign then uucpa then a dot then org.

Back in time…

This Sunday, during our congregation’s online service, we’re going to go back in time…

…using the congregation’s time machine…

…to the year 29 C.E., to a small town in the land of Judea. There we will meet a fellow named Ishmael, who’s the kind of person who loves to spread rumors.

“They say,” says Ishmael, “that….”

If Ishamael lived today, he’d be the kind of fellow who emails you the latest internet conspiracy theory. But since he lives in the year 29 in Judea, he spreads his rumors face-to-face in the town’s marketplace. He meets up with a woman named Martha. When he learns that Martha’s brother Peter has joined the entourage of the famous rabbi Jesus of Nazareth, not surprisingly he has a few conspiracy-theory-type rumors to tell Martha. This causes Martha to wonder if her brother is going to be OK….

“Now you’ve got me wondering,” says Martha….

Our trip to the past will take less than three minutes, allowing us plenty of time for the usual singing, music, preaching, etc. The whole thing will be livestreamed on the Facebook page of the Unitarian Universalist Church of Palo Alto, this Sunday at 9:30 and 11.

Make yourself look good on camera

With the shelter-in-place order, any socializing we do is on camera. Plus many of us have to use videoconferencing for work. As long as we’re going to be spending lots of time on camera, we might as well look our best. So here are some tips for making yourself look good on your laptop’s (or your phone’s) crappy little web camera.

First of all, and perhaps most importantly, have your laptop or phone sitting on something stable. Ideally, you want to move the camera as little as possible, for two reasons. First, if you’re in a videoconference, you want to focus attention on your face, and if you move the camera around that’s going to be a distraction. Second, unless you have a really fast internet connection you probably want to save bandwidth; if you have a stable backdrop, that will be less information you’re sending out, and so you’re less likely to have degraded audio or video.

Second of all, don’t place your camera too low. If your camera is too far below your face, people will be looking up your nose, and if you’re middle-aged they can see all those incipient jowls that you’ve been trying to hide. In other words, don’t do this:

Camera placed too low, and only one source of lighting

Boy, do I look ugly in the photo above! Don’t make yourself look ugly. Place your computer or phone so that the camera is about at the level of your chin. However, don’t place your camera too high; there’s a psychological disadvantage to giving your viewers the impression that they are higher or taller than you.

In addition, learn about the Rule of Thirds. Imagine that your screen is divided in thirds both horizontally and vertically, sort of like a tic-tac-toe board. Have your eyes placed so that they’re about a third of the way from the top of the screen. Move so that your head is NOT in the center of the frame, but about a third of the way to one side (I like to move to my left, so that my right hand, my dominant hand, can make gestures in the space to my right). Setting up your camera using the Rule of Thirds will make you look more professional, because that’s what we’re used to seeing in movies and on television.

Use the Rule of Thirds to place yourself in the frame of the camera

Now let’s take a look at lighting. In movies and television, they use what’s called “three point lighting.” That just means that they use three light sources to light someone’s head. First, you set up the “key light,” which is the most important light. If you’re at home and on a videoconference during the day, your key light is most likely determined by the nearest window — in that case, try to sit so that the light from the nearest window is coming towards you at about a 30 degree angle — and you want diffuse daylight, so make sure there’s a curtain or something to give diffuse light. At night, sit so that the strongest light in the room becomes your key light.

With only the key light, your head will look a little one dimensional or washed out; and if you have any wrinkles or blemishes, they will tend to stand out. Therefore, you need to set up another light, called the “fill light,” which will fill in the stark shadows cast by the key light. The fill light should be less bright than the key light. The drawing below shows where the key light and the fill light come from:

Diagram of three point lighting

Then if you want really professional lighting, you’ll add what’s called a “back light.” This comes from the same side as the key light, and it lights up the back edge of your head. By lighting up that back edge of your head, it makes you look that much more three dimensional. However, it’s super time consuming to set up a back light, so I don’t bother when I’m on a videoconference.

Now here are some examples of what I look like with these different lights. Here I am with just the key light — it’s adequate, but pretty stark:

Continue reading “Make yourself look good on camera”

Further adventures in livestreaming

The shelter-in-place order has made livestreaming our church’s worship services a little more complex. We just had a tech rehearsal with worship leaders and tech support people each in their own locations, using Zoom as our basic platform. We have learned a lot since we livestreamed last week! Here’s a summary of what is currently working for us:

(1) Before the rehearsal, whoever owns the Zoom account needs to log in to their Zoom account and go over the settings carefully (see the screenshot below to see where to find “Settings” when logged in to Zoom). The critical settings you need to be aware of are as follows:
(a) Do not allow “Join before host.” This is to prevent someone from hijacking the feed with inappropriate screensharing before you take control.
(b) UNtick “Participant video: Start meetings with participant video on.” You want participant videos off, partly to prevent distraction, but also to prevent trolls from putting inappropriate content on their video feed. (Zoom will allow participants to start their video feed again, so you’ll also need someone to monitor participant videos during the service; see below.)
(c) Tick “Mute participants upon entry.”
(d) Tick “Allow co-hosts,” for two reasons: First, you’re going to need 2-3 people to manage the video feeds; second, make all worship leaders co-hosts because that puts them at the top of the participant list so you can more easily find them when switching back and forth between worship leaders and musicians.
(e) Tick “Allow host to put attendee on hold.” Just in case.
(f) Under “Screen sharing,” make sure you select the option where only allow host(s) can share screens. This prevents so-called “Zoombombing,” where trolls put up inappropriate images on your Zoom feed.
(g) Tick “Disable desktop/screen for users.”
(e) Tick “Allow users to select original sound in their client settings.” This improves the audio quality of musicians enormously.

(2) Well before the service starts, make sure you have email addresses for all co-hosts and worship leaders. Cell phone numbers would be a good idea too. If something fails, it’s nice to have a backup communication method besides private chat within Zoom.

(3) Start the Zoom call at least 15 minutes before the stated start time for the worship service, and make sure your co-host(s) who are managing participants also log in early. You want to have at least two hosts managing participants before the stated start time, when you’ll have your big influx of participants log in. Have your worship leaders log in early as well, and assign them co-host status so they appear at the top of the participants list.

(4) During the worship service, you’ll want people in the following tech roles:
(a) One host to “Spotlight video” of whichever worship leader or musician is on.
(b) One or two hosts to manage the participants. If you have a really small service (say, 30 or fewer participants logged in), you might be able to combine this role with the previous role.
(c) One or two people to work on audience engagement; these people will be monitoring the chat. Specific tasks might include monitoring chat for joys and sorrows (we’re going to allow joys and sorrows in chat); pasting hymn/song lyrics into chat at the appropriate moment; watching for newcomers to the service and perhaps greeting them privately in chat; generally monitoring behavior.
(d) Optional: we’ll also have a few knowledgable people monitoring audio and video quality, and providing feedback and/or advice as needed.

(5) Send out a script ahead of time. Our script, which was the basic order of service, proved to be inadequate. The primary worship leader (the senior minister in our case) is going to send out a full script, and our music director is going to insert cues for the host who’s in charge of switching the video feeds.

(6) We did a brief postmortem to talk about what worked and what didn’t work, and of course we’re doing email follow-up as well.

One final point: While putting on a worship service is always a team effort, it becomes even more of a team effort when you’re livestreaming (especially when everyone has to watch from home), because the tech crew becomes an integral part of the worship team. I consider this a major benefit of livestreaming services: in these times, when we’re all feeling a little isolated and scared, being a part of a team effort can be quite comforting.

Browser privacy

I’m not keen on having anyone know my Web browsing habits; I’ll go into my motivations in the last paragraph of this post. I’ve taken the obvious steps to reduce the risks of being tracked online: using DuckDuckGo in private mode as my primary search engine, and Firefox as my Web browser. But online surveillance is only getting worse, and recently I decided to become more resistant to Web tracking.

I had already enabled private browsing and other privacy and security features in Firefox’s preferences, and I had already installed the Privacy Badger add-on in Firefox. I checked what I had done against a number of online privacy checklists (such as this one). Next step was to change advanced about:config settings based on this list.

Now I was ready to test my browser’s privacy using Panopticlick, an online service of the Electronic Frontier Foundation that checks if your browser is safe against tracking. My browser was blocking ads and invisible trackers, but it was not protecting against fingerprinting. Yikes! fingerprinting made it way too easy to track me online. So I installed the NoScript add-on in Firefox: problem solved. Now my browser runs a little differently from what I was used to, but the inconvenience is minor.

Why should anyone care about their Web browsing privacy? For my part, I don’t want to give my information away to for-profit companies: I don’t need targeted advertisements, and I don’t need them accumulating my data. And, in the increasingly polarized political climate of the U.S., even though a philosophical theologian like me should be reading Karl Marx’s works, or a speech by Fred Hampton, or theology essays by William R. Jones, there’s no reason to let others know about it. In short, I decided to give Big Tech (corporations, the Russians, the “Gummint,” whoever) as little information about myself as possible. You will make your own decision of what to do, from freely giving your browsing data away, to being very privacy-conscious by using something like the Tor browser. I suppose this is really an existential point: you define yourself by how much of your data you give away.

Updating Web site security

This site, as is true of many Web sites, has been experiencing attacks for some years now; one such attack took down this site in early 2011. Believe me, having your Web site go down definitely sucks. Since 2011, with the expert help and advice of my Web hosting service, the security on this site has been continually upgraded. Among other measures, Wordfence has been installed on the WordPress installations, Cloudflare is in use, and the site was moved to servers optimized for WordPress.

And now, finally, thanks to Dennis at Deerfield Hosting, this site is using SSL certificates. SSL Labs now gives this Web site an “A+” rating on its SSL report.

Some things to look out for:

1. Dennis writes: “I have purposely limited the cipher suites available to deliver the site. Analysis and specifics here. Some people will and do disagree with doing that. Some visitors will not be able to see your site. I’ve looked at the stats and the numbers are very low, to the point where calling these cases very rare is accurate.” If you can’t see the site, you obviously won’t be reading this. But this is still a reminder to use up-to-date software. Also, one possible browser upgrade you might be interested in is the “HTTPS Everywhere” plugin for Firefox, Chrome, and Opera, available from the Electronic Frontier Foundation here.

2. This Web site should automatically redirect an “http” link to an “https” link, but there may be occasional problems. If you find such a problem, please let me know (so far I’ve heard from one Web manager who found this problem).

3. In a similar vein, I am updating internal links. Until I have finished doing so, some internal links may not work. Please let me know if you find one, and I will fix it ASAP.

4. Web geeks will be interested to know that Dennis also switched this site to HTTP/2. He writes: “Your site is now among the first sites on the Internet to employ HTTP/2, the successor to HTTP/1.1. Only about 2% of sites have this distinction. One of the advantages is faster site delivery. Page components are requested and delivered asynchronously over a single connection. More information here.”

Finally, I can’t thank Dennis at Deerfield Hosting enough. Most Web hosts these days just provide a commodity, and it’s great to be with a Web host that still provides actual customer service.

Update:
To clarify a little, software which will be unable to establish a secure connection with this site includes:
— Android 4.3 and earlier
— Internet Explorer 6-9
— Safari 5-6
If you’re reading this, your browsing software is reasonably up-to-date. Yay, you!

Going from “Oops” to “Yay!”

My denomination recently did an excellent redesign of their Web site, making it completely responsive and easy to view on tablets and smartphones.

My denomination then updated the denominational bylaws so they are now only available as a PDF. Which means the bylaws are now neither responsive nor easy to view on tablets or smartphones.

Improve a Web site. Yay!

Then break it. Oops.

This is why it is essential to have processes in place to continually monitor a Web site’s usability. Because it is way too easy to do something stupid that breaks the functionality of even a modestly complex Web site (he says, speaking from personal experience). And because when you go from “Yay!” to Oops,” you need to be able to get back to “Yay!” as quickly as possible.

Let’s talk UU SEO

Behind the scenes, several Unitarian Universalist bloggers have been discussing how to increase traffic to blog posts that the blogger thinks are useful or important. One UU blogger observed that if you write a post that is some combination of controversial, critical, or ranting, you are more likely to get a lot of hits on that post. But how do you drive traffic to more thoughtful posts that you think are worthy of a wider readership, but which aren’t the kind of traffic you think they deserve? The advice given by several bloggers was to write headlines and titles that are carefully designed to drive appropriate traffic to the blog post.

This is a sound approach to driving traffic to your blog, and I have no intention of following it.

Over the years, I’ve tried this approach a few times, and I’ve written a few blog posts on controversial topics that, judged by my low standards, got a fair amount of traffic. I discovered three things: First, writing controversial blog posts that attract lots of traffic forces me to think about the world in ways that I do not enjoy: you have to start looking for controversies everywhere. Second, once you start getting more than half a dozen comments on controversial blog posts you are going to have to spend time moderating whackos and fending off trolls, activities I find dull and unpleasant. Third, controversial blog posts tend to attract readers who either have an axe to grind or who aren’t interested in nuance, people with whom I have little in common.

So I came up with a different strategy for writing blog posts.

I tend to write carefully-written, well-documented posts designed to have a long shelf life. Such posts might provide information not easily available elsewhere on the Web, e.g., the posts I have done on Black theologian William R. Jones. Or such posts might provide authoritative information on an area where I have some level of expertise, e.g., the post I did on implementing #FergusonSyllabus in Sunday school. Or such posts might provide useful summaries on an obscure topic (note that since Unitarian Universalism is a tiny sect, most UU topics are obscure), e.g., the posts I have done on the theological influence Mary Rotch had on Ralph Waldo Emerson. In SEO (search engine optimization) terms, this is a variant of “long tail search”; my SEO goal is to have lots of authoritative posts with just a few highly specific links going into them.

To put it another way, trying to compete for traffic with Huff Post (or for that matter with Doug Muder and Vicki Weinstein) is a mug’s game, a strategy with a low chance of success. At least, it’s a mug’s game for someone like me, because I’m not that kind of writer.

I’ve spent some time thinking about the kind of writing I am best able to do. My partner, a former freelance writer, talks about being an “information hunter-gatherer,” and I can do some of that. My older sister, a professor of writing and an author, talks about the book by Robert Coles, Doing Documentary Work, and I can do some of what Coles describes. Then too I’m a minister, and every once in a while I’m able to do some writing on spiritual topics.

Once we’ve gone this far, the rest is obvious. Finding out what kind of writer you are means figuring out who your readers are, and what they are interested in reading. Finding out who you are as a writer means learning how to write well for your readers. Depending on who you are as a writer, this could mean learning how to write clickbait headlines, and keyword-rich blog posts. Or if you’re a different kind of writer, this could mean something different. In my case, it means trying to write well-crafted short essays on topics about which I have knowledge. And in your case, it might be something else altogether.

I don’t believe there is one best way to write a blog. I believe what you want to do is know who you are as a writer, know who your readers are, write well-crafted blog posts aimed at your readers, and then find the SEO strategy that best allows you to reach your readers.

Secure video chat

Deborah, another UU minister, told me about VSee, a video chat service with 256-bit encryption. VSee is designed as a “telehealth” app, for use by doctors and other medical professionals; the company claims that it is the first such application that complies with HIPAA.

Clergypersons working in congregations do not have to comply with HIPAA, and certainly HIPAA would not be the right set of standards for congregational work. But maybe we should be thinking more about how to protect the privacy of congregants. Email is far from secure, yet I find myself doing pastoral car via email. I don’t know that VSee is an appropriate product for me to use (I’ll have to experiment with it), but maybe it’s time to research options like this.