Category Archives: Drupal

Owning our work

I worry when I see that the brilliant words, images, and other creative works of so many folks are only posted on Facebook, Twitter, Tumblr, and other corporately-owned services. Posting such content to those services only, and nowhere else, has two worrisome consequences.

First, whenever we post our words, photos, videos, or other things that constitute intellectual property to these services, we’re automatically giving these for-profit corporations various rights and licenses to store, use, reproduce, display, modify, and share our work. We agree to that when we accept the Terms of Service (ToS) when signing up for a new account; these Facebook, Twitter, Tumblr ToS are examples that many of us have accepted. They’re all a little different and some are better constrained, better written, or better explained than others; the Tumblr ToS seemed particularly clear to me. In each case we still retain ownership of all intellectual property rights for our content, but the companies still gain a good deal of freedom over what they do with our content and how they can make a profit from it. (Profit that we’ll never see a cent of, of course.)

That squicks me out, but I worry more that many of these services — Facebook, Twitter, and Tumblr in particular — make it difficult to transfer all of that content out of their systems and into other ones, including systems that we have way more ownership or control over: our own hosted blogs or websites or our own computers. It takes a fair amount of time and tech know-how to set up any automated system for pushing content from those services to something else that we control more. And some of those systems don’t make it very easy to get to your older content, either.

So to me, it always feels like my content is disappearing into the cloud, a very dark cloud, perhaps never to be seen again. I don’t know how it will be used exactly, I don’t know how long it will be around for, and I don’t have any easy way to get back to it later.

That’s one of the motivations for this blog: it’s a WordPress blog hosted on servers maintained by a web host that I know and trust well with my data. I’m able to back up the whole thing automatically and redundantly (I’ve got a few backup systems so my backups are backed up). I can do that in part because free WordPress plugins like BackUpWordPress make it really easy for anyone to do, and in part because my tech knowledge of things like git gives me easy options for having multiple copies of my site and data stored in many physical locations, including my own computer and backup drives.

I’m trying to always copy the more thoughtful, interesting, meaningful or funny things I post on Facebook or Twitter to this blog, too. That doesn’t undo the fact that Facebook and Twitter both have somewhat creepy rights to what I’ve posted there, but it does make sure that my content is also stored in many places where I can truly own, control, and trust what’s going to happen to it.

It also turns out to be a good way to get me to write more; this post started out as something that was Facebook-ready, meaning short — three sentences, maybe. Even though Facebook status updates can now be more than 60,000 characters long, Facebook still seems to work better with short posts, in part because folks are more likely to read, “Like,” and comment on shorter things. But after getting used to writing for Facebook and the 140-character-tops Twitter, I’m really enjoying having some more room to stretch out into with my posts.

If other folks are wondering what they could do to deal with problems like the ones I’ve brought up here, I’ve got a few suggestions (and would welcome more from others!)

  • Learn how to get set up with your own website or blog using self-hosted open source software. That’s a daunting task, but it’s doable, and there may be resources in your own communities — friends, fellow activists and organizers, fellow students, family members, etc — that can help you get started. I highly recommend WordPress for getting started and rather like WordPress for blogging, even though I love building websites in Drupal.
  • Use online services that give you better options for exporting or re-publishing your content. WordPress.com and Drupal Gardens let you get started with your own free site without setting up your own web hosting or buying a domain name. If you want to move to your own self-hosted solution later, both services make it pretty easy to move your whole site off their servers and onto your own. You can also use services like Twitter and Tumblr that provide RSS feeds and APIs that let you re-publish your content automatically to other websites and services.
  • Cross-post your content. I really like using Facebook and Twitter; they make it easy to share content with tons of people. But I still want to be able to own and keep track of my content, so if it’s good I post it to this WordPress blog, too. Soon I’ll get around to setting up automated feeds from Twitter (and maybe Facebook, if that is possible?) to this blog in a way that actually creates posts on the site (rather than simply displaying content that’s still trapped in Twitter or Facebook.)
  • Save your content on your own computer. This is a really easy way to make sure that you’ve always got a copy of your content under your own control. Save all your photos locally instead of only leaving them up on Twitpic or Instagram; copy and paste your good Tumblr, Facebook, or Twitter content into text files or documents on your own computer. (For bonus points, learn how to do regular backups of your own computer, too!)

Any other good solutions out there?