Goal

This tutorial shows you how to edit digitized video captures into smaller clips that you can publish on your own password-protected MediaGoblin server. You’ll use a free Heroku dyno, so your only ongoing cost for running this private media server is the cost of storage on Google Cloud Storage, which is 2.3 cents per GB.

I used this workflow to edit and share my family’s home videos at a cost of only $0.77 per month. For the detailed backstory, check out the blog post, “My Eight-Year Quest to Digitize 45 Videotapes.” You can use this workflow for any kind of video file that contains lots of subclips that you’d like to chop out and share.

For the last eight years, I’ve carried around this box of videotapes through four different apartments and one house. They’re family home videos from my childhood.

After 600+ hours of work, I finally digitized and organized them well enough to throw away the original tapes. Here’s what the footage looks like now:

Nonviolent Communication describes a communication style centered around sharing vulnerability and offering empathy. One of its biggest strengths is in how it highlights common patterns of lazy communication that exclude personal feelings or critical thinking. I also found its discussion of empathy illuminating, as it made me realize ways that I could improve my skills at listening empathetically.

Let’s be real: most developers decide what to blog about on a whim. Our blogs cover tons of topics, and there’s a good chance that the only person interested in ALL of them is, well, us. That’s just one reason it’s handy to tag and segment subscribers to your email list. Basically this means assigning tags to people based on what blog post made them decide to subscribe. You can use tags and segments to:

If you maintain an open-source project, there’s a good chance the pull requests you receive need a little bit of work before they’re ready to merge. Here’s a quick step-by-step guide for how to modify commits on a pull request when it’s coming from a fork of your repo. In this guide, we’ll assume the following: Your repo: github.com/your-username/your-repo-name Your contributor: their-username Their PR’s branch: bugfix-branch Step 1. Add their fork as a remote You can name the rew remote whatever you want to (in the example below it’s called “anything”, but I’ve been using the contributor’s username in practice):