This conception of the problem suggests two broad strategies. First: attempt to change the political structures that allow campaign and lobbying money to play such a significant role in the legislative process. Primarily, this is an argument about campaign finance reform. For a very readable outline of the problem, as well as the sketch of a few specific strategies for combatting it, I highly recommend Lawrence Lessig’s recent book Republic, Lost. Needless to say, solving the problems of money in politics is enormously difficult and complex, so I’ll set it aside for the moment.

The strategy that I want to consider here focuses more directly on the fact that media companies are very rich, and can afford political canoodling. (Operating here on the admittedly oversimplified assumption that media companies – TV, movie, music, book publishers – are driving the legislation.) These companies get their money from the people who buy their wares. So, in theory, if everyone stopped going to the movies, buying music, watching TV, etc, then they’d have no money. In other words, a boycott.

A few days ago, I tweeted something suggestive along these lines:

When you buy music, watch TV, or see a movie, don’t forget: the makers hate the free internet & will spend huge amounts of money to kill it.

Assume that the premise here is right (namely, that the people who make media – by which I mean, those who choose which media gets created in the first place, who fund its creation, who are responsible for its distribution and marketing, etc – hate the internet as it currently stands). That means that when you make them richer by buying their stuff, you are increasing their ability to fight the internet. All things being equal, then, someone who values the open internet should not spend money in this way – that is, you’d be morally obligated to boycott.

But all things are not equal. (Such is life.) There are some factors that may mitigate the obligation to boycott:

• How valuable is the open internet, really?

  I’m assuming that an open internet is valuable enough to defend. I may be totally wrong about this, or I may be overestimating how valuable it is. The less valuable the internet, the less obliged we are to fight against the forces that would wreck it.

• How much collateral damage would a boycott cause?

  The supporters of SOPA/PIPA talked a lot about the zillions of Americans who make their livings working for media conglomerates. If boycotting media companies would put them all out of work and out on the street, that’d be a bad thing. Of course, this is a complete caricature. For one thing, you can (and should, and hopefully did) make the very same argument about the zillions of Internet professionals who would be harmed by stifling legislation. More importantly, it’s not as if SOPA vs non-SOPA is a zero-sum game, where media professionals all lose their jobs if SOPAesque bills don’t pass. It’s likely that piracy is not as financially harmful as these companies complain, and it’s likely that there are anti-piracy measures that would not harm Internet professionals.

  There’s another kind of collateral damage you might be worried about: the damage caused to the creative people (musicians, writers, actors) who are directly responsible for the media that people love, and the subsequent damage to the “art” itself. In addition to the general points made in the foregoing paragraph, I’ll add that this assumes that the stuff produced by these companies is worth saving. For every The Wire (or whatever your favorite piece of popular media is), there are thousands upon thousands of pieces of trash. Taking these turds out of circulation is probably a *good* thing. Moreover, new models of direct funding for quality art (think Radiohead, Louis CK, projects taking place on Kickstarter) reduce collateral damage even further.

• How much do you value the media produced by these companies?

  If you’re a TV junkie, or you love the movies, then it’s certainly rational for you to cling to them a bit more than someone who doesn’t care about these media (see the ‘turd’ comment above).

• How likely is it that a boycott will make a difference?

  Probably hundreds of millions of Americans are consumers of TV, movies, books, and music. For a company like NBC Universal to take notice of a boycott, much less to change corporate policies as a result of the boycott, would require huge numbers of boycotters. You might thus argue that your individual boycott would have no positive value.

  Sadly, this is at least partly true – I’m sure there are many times more people who would go to bat for their TV shows than for the kind of heady internet freedoms that intellectuals get excited about. That said, January’s blackouts demonstrated a deep dependence on the Internet for a broader swath of Americans than I might have guessed. In any case, even a single dollar kept out of media company coffers is one dollar they can’t use to fight the open internet. The “everybody else is buying media anyway” argument is the same kind of reasoning that leads to looting during blackouts. (See also Kant.)

So what does this all mean? I think that there are a couple of takeaways:

1. I think there’s a decent case to be made for a broad boycott.
2. Even in the absence of an organized boycott, I think there’s a decent case to be made for individuals to boycott.
3. If you care about the internet (if you’re reading this blog post, you probably do), you cannot continue to patronize these media companies without at least recognizing the indirect effects of your actions.

This last point is the most important. Every meaningful decision that you make is an ethical trade-off, and this one is no different. When you continue to patronize media conglomerates, you are saying that what you get from them is worth the damage that you thereby do to the cause of an open internet. You may be right about the value of this trade-off, or you may be wrong, but you can’t in good faith continue to consume without at least thinking about it.

Related posts:

1. Tensions between disciplinary and media instruction
2. Social Media and General Education: My Queens College Presidential Roundtable talk

“Proper” standing desks – those that are built for the purpose – tended, in my research, to fall short in a couple of ways. The first is cost. Decent standing desks seemed to start around four or five hundred bucks, and go (way) up from there. The vagaries of New York living mean that I didn’t want to lay out huge amounts of cash on something that might not fit in my next place. I wanted something cheaper. The second shortcoming of manufactured standing desks is size. It’s pretty easy to find what they call “workstations”, which have a surface of about two feet squared. My 27″ monitor by itself requires nearly that much space, and I wanted surface area for writing, a second computer, coffee, etc, yet full-size tables seemed pretty hard to find. Lame surface size is related to my third problem with existing standing desks, which is the paltry storage underneath. I wanted lots of it, and commercially produced standing desks seemed, at best, to dedicate vertical storage to a printer (BOOO PRINTERS).

So I needed something fairly cheap, fairly big, and with a lot of storage underneath. A bit of trawling turned up this hack, which made a desk by combining a few different kinds of Ikea bookshelves. Unfortunately, that desk was too big for my space (I have about 66″ of horizontal space to deal with, and that setup requries a minimum of 73″). But it made me think I could do something similar using IKEA bookshelves.

Here’s the finished product:

And here are the details:

• 3x BILLY bookcase – Two of these bookcases serve as the ends of the desk. Since I knew I’d have a bunch of additional space underneath, I bought a third, which is just slid underneath for extra storage.
• 1x VIKA AMON table top – They didn’t have this in the same wood tone of my BILLY bookcases, so I got bright red instead.
• 1x BILLY wall shelf – I needed something to raise my monitor and laptop up to eye level, and this gives me some nice desktop storage to boot. I couldn’t find something that spanned the full width of the table top, so I just centered this one, and used the extra space for speakers.

Total cost for these pieces was, as of yesterday, about $230+tax.

One of the big bonuses of using bookshelves as table legs is that I don’t need to worry about stability (like I would with regular table legs). The only fasteners I used were the four drywall screws I drove up through the bookshelves to keep the table top from sliding, and the two I drove down through the wall shelf to keep it in place.

If you’re looking to do something like this yourself, make sure you think carefully about height. I chose this combination in large part because the resulting table height (about 43″) works for me: in bare feet, standing on my anti-fatigue mat, my elbows are at almost exactly a 90 degree angle while typing. I’m between 6’3″ and 6’4″, so your ideal desk height may vary.

Related posts:

1. Stand for something
2. How the internet works: A case study

• I quit graduate school
• I traveled a bit: WordCamp Phoenix, API Workshop at MITH, Jamaica, NC barbecue roadtrip, THATCamp
• I co-taught a class about WordPress in the graphic design program at Queens College
• I proved myself the 76th best crossword solver in the universe
• I taught an intro to philosophy class at my alma mater
• I started Project Reclaim
• I hit the top 3 on Hacker News with a post about CUNY, Blackboard, and the inspiration to develop free software
• I switched to a standing desk
• I co-wrote a successful grant application
• I shipped mountains of code.
• Finally, and most importantly, I became a father

Like 2010, 2011 was a year of transitions for me: in my relationship with academia, in the way I earn a living, in the way I present myself as a citizen-builder of the internet. Being a parent is the biggest transition of all, forcing me to put into perspective the ways I spend my energy and the ways in which I define myself and what has value to me. (This transition has been overwhelmingly a Good Thing.) Continuing to strive for the right balance in these areas will, I’m sure, be a hallmark of my 2012. (Thankfully, I have no plans to have a child or get married in 2012. A man needs a year off from major life events!)

Happy new year!

Related posts:

1. Looking back at 2010
2. I develop free software because of CUNY and Blackboard
3. Dropout

The Stop Online Privacy Act (and its cousin in the Senate, the PROTECT IP Act) are inching closer to passage. Time is running short for you to do what you can to stymie this legislation, which could very well destroy the open internet as we know it. (Don’t know about SOPA? Get a nice overview in this short video, or check out Jeff Sayre’s helpful bibliography of resources about the bill.)

Why you should care about this

If you are reading my blog, you likely fall into one of a few camps, each of which has a vested interest in preventing the passage of SOPA and PROTECTIP:

• If you are a developer, user, or advocate of free and open source software, you have several reasons to be concerned about the proposed legislation.

  For one thing, the small-to-medium sized web organizations that are most likely to be targets of SOPA’s blacklisting protocols make up the bulk of the clientele for many web developers I know. These organizations generally do not have the visibility or high profile to put up a stink when and if they fall prey to overzealous “copyright” claims, nor do they have the deep pockets to fund the necessary legal defenses. The danger is especially great for websites that accept – or are built on – user-generated content, like many WordPress and BuddyPress sites; SOPA provides for the blacklisting of entire domains, based merely on the a few pieces of “offending” content, even if the content was not created or posted by the domain owners. Over time, these threats and constraints are bound to make the development of these kinds of sites far less feasible and attractive, resulting in less work for developers – and less development on the open source projects that are largely subsidized by this kind of work.

  On a deeper level, those who are interested in the philosophical underpinnings of free software – the rights of the user – should be terrified by the prospect of media corporations gaining what amounts to veto power over our most fecund channels for the exercise of free expression. Free software lives and dies alongside a free internet. When one level of our internet infrastructure (DNS) is under the control of a self-interested few, it makes “freedom” at higher levels of abstraction – like the level of the user-facing software – into an illusion.

• If you are an educator or an instructional technologist, especially one who endorses the spirit of open educational movements like (the OG) edupunk and ds106, you should be flipping out about SOPA.

  At an institutional level, thoughtful folks in higher ed and edtech have been fighting for years against a FERPA-fueled obsession with privacy and closedness. They’ve made strides. Platforms that foster learning in open spaces – stuff like institutional blog and wiki installations – have become increasingly commonplace, demonstrating to the powers that be that, for one thing, the legal dangers are not so great, and for another, whatever legal concerns there may be are far outweighed by the pedagogical benefits to be reaped from the open nature of the systems. The threats put into place by SOPA are likely to undo much of this work, by tipping the scales back in the direction of fear-driven policy written by CYA-focused university lawyers. Advocates of open education, and the platforms that support it, should be keen not to let their efforts go to waste.

  At the level of the individual student, the case is more profound. The most promising thread in the story of higher ed and the internet – the thread running through Gardner Campbell’s Bags of Gold and Jim Groom’s a domain of one’s own – is, in my understanding, founded on notions about student power and agency. Users of the internet are not, and should not be, passive actors and consumers of content. Instead, they should take control of their (digital) selves, becoming active participants in the construction of the web, the web’s content, and their own avatars. SOPA and its ilk are an endorsement of the opposite idea: the “ownership” of creative content on the internet is heavily weighted toward media companies, which is to say that you are allowed to be in control of your digital self until it causes a problem for a suit at MPAA or RIAA. The entire remix/mashup culture of ds106 is impossible in such a scenario. If you think that this culture, and the ideology of student personhood that underscores the culture, is worth saving, you should be fighting SOPA tooth and nail.

What can you do? Write a blog post. Join or support the Electronic Frontier Foundation. Most importantly, if you are an American, contact your representatives in Congress. The Stop American Censorship site makes this easy, and gives you all the talking points you’ll need. (“This bill is a job killer!”)

Do it now!

Related posts:

1. SOPA, Media Conglomerates, and the Moral Obligation to Boycott
2. Lessons from the Google Summer of Code Mentor Summit
3. The GPL is for users

It’s true that, compared to the cost of private schools – and maybe even other public institutions, I’m not sure – CUNY is pretty cheap. But it’s unwarranted to leap from the observation that CUNY tuition is relatively less expensive to the judgment that CUNY students have nothing to complain about.

The first reason is that, for many students in CUNY’s target demographic, $300/year is a significant amount of money. When you consider that the $300 hike is slated to happen once per year for the next five years, it becomes less controvertible that the increase is significant. A student in her first year at a four-year CUNY school will pay an additional $1,800 over her next three years, an increase of about 11% over what her tuition would be at current rates. (The percentage is higher at community colleges.) Even if you know nothing about CUNY students, there’s no question that an 11% (or higher) increase is something worth getting upset about.

And there’s something more insidious lurking behind the “they’re spoiled” sentiments: the idea that the insane costs of higher education are somehow “normal”, or even “the way things ought to be”. Charts like this one (assembled here from Consumer Price Index data) suggest that tuition increases have outpaced inflation by about two to one in the past decade or so. Unless wages have also outpaced inflation in this way (which, ahem, I doubt they have), it means that college tuition is, in some objective sense, a greater proportion of income than it used to be. Why should this seem right? Is higher education is a privilege that should be available only to people with financial means? In what way is income a meaningful indicator of who should be able to go to college?

Look at it another way. If the “CUNY students are spoiled” comments comes from people who are pissed off about the fact that they pay far more for their private schools – if it’s sour grapes – then it’s downright idiotic. People paying outrageous tuition to private schools, scraping by only by recourse to enormous student loans, should be right alongside of CUNY students, fighting the cultural sentiment that allows their $40K tuition to seem somehow acceptable. I fall into this category myself. My student loan debt is staggering. My wife and I make good money, and pay off large amounts of principle on our loans every month – but still we’ll be 40 before they’re paid off. If this is normal, then “normal” is something that we should all be resisting.

No related posts.

It’s taken me a while to make the move, though, for two main reasons.

1. Email is tricky. Good, free mail server software is easy to find. But it’s not necessarily easy to set up and maintain. If the outgoing server isn’t configured correctly, your messages will get marked as spam. If you haven’t got constantly monitored spam filters on your incoming mail, you’ll be inundated with garbage. And the issues of backups and reliability, while certainly important in the case of (say) self-hosted websites, are many times more important with email: if the server goes down, emails may get altogether lost in the ether.

   I’ve set up and configured email servers before, and it hasn’t been very fun. When deciding how to solve the Gmail conundrum, I needed to take this fact into consideration. I started to do a bit of research on paid email hosting, and found good reviews of Rackspace’s hosted email service. The service is pretty affordable, and I knew from years of Slicehost use (now owned by Rackspace) that customer service and support would be good.

2. I needed a good address. I own a lot of domain names, but most of them are lame, and none lent themselves very neatly to an email address. For instance, when your domain name is boonebgorges.com, what’s the email account name? ‘boone’? The cool factor there is pretty low. And I am a cool guy, so that’s important.

   Some of the obvious domains are taken. boone.com is wasted on dry-erase boards. gorges.com could never be wrested from the clutches of “one of the oldest family owned Volvo franchises in the United States”. But there was hope – or should I say había esperanza – that I might get the fairly unused gorg.es. In fact, my brother and I had been working on that project for a couple of years, but it was only a few months ago that the owner finally relented, and the domain name was transferred to the Gorges boys.

So, about two months ago, I made the switch. For now, I just set it up as another account in Thunderbird (more on my Thunderbird setup). I created a generic “Archive” directory on my gorg.es account (to mimic Gmail’s All Mail) and pointed my ‘Y’ shortcut to that directory. I’m using K-9 Mail on my Android phone, which I set up to save the entire Archive directory, so I’d have good local email search on my phone. Little by little, I’m moving over my email correspondence to the new, awesome address. Bye bye, Gmail!

Related posts:

1. Project Reclaim
2. Making the Thunderbird interface more Gmail-y
3. Automated and redundant Wordpress backup via email

First is my ongoing project to move away from proprietary software in general. All things being equal, it’s better to use software whose source code I can view and modify; even if, in fact, I never do these things, the fact that I could is a kind of safeguard against a number of frequent aspects of closed-source software: data lock-in, data rot, restrictions on hardware compatibility, secret surveillance, etc. As the operating system is in many ways the foundation of all other tasks I do on a computer, so it is of fundamental importance to use an open OS.

Second. I believe in the Web as an open platform for communication and expression, and Apple is increasingly anti-web.

You often hear hoopla about how digital technologies can radically democratize and transform x (fill in your favorite x: scholarship, education, publication, politics, etc). The success or failure of these transformations is tied up with the Web’s openness as a platform: open standards like TCP/IP, enablers of decentralization like distributed DNS, free software like Linux and Apache to run servers. Putting any of these technical details under the control of a single agent, especially a corporate agent that answers only to shareholders, threatens to limit free expression and disenfranchise vulnerable groups of potential users. If a robust, widely-used, open Web is important to the future of equality and democracy, and if such a Web can only be defended by keeping out proprietary interests, then it’s important to fight against interference from those interests.

I take it as fairly obvious that Apple (and not only Apple, though they seem to be the trendsetters) is anti-Web. Consider their distribution models. iTunes makes it so that you have to buy apps, music, and movies through an application, rather than through web pages. Know that annoying “feature” where, when you click on an iPhone app link on the web, you get a page informing you that you’ve clicked on an iTunes link, whereupon iTunes proceeds to open? That’s anti-web. The increasing focus on “apps” is a more troubling anti-web move. As was nicely illustrated by an article I read a while back (can’t find the link), you can spend a whole day doing stuff on an iPad – using Twitter, Facebook, WordPress, Yelp, email, Google Maps, etc – without ever viewing a web page (though they all use web services that use HTTP as a transport). In this way, Apple is doing an end run around the web.

The nature of the end run is particularly troubling. Apple is the arbiter of the software that runs on its devices (completely, in the case of iThings; increasingly, in the case of the AppStorified Mac). This creates unnecessary bottlenecks when it comes to bugfix or security releases. It creates a single point of failure for apps and therefore for devices; if Apple goes under tomorrow (or, more likely, changes their mind completely about whatever they please), how will you continue to update your apps? Worst, it puts Apple in the position of policing for content, which, whether driven by a well-intentioned desire to avoid offensive content or by a malevolent puritanism, is a Bad Thing.

Anyway, all of these points have been made over and over again, by many different people. My own bottom line: I believe in the value of the open web to such an extent that I’ve devoted my career to it. Thus, it feels wrong to keep using, and indirectly encouraging the use of, technologies like Apple’s. That goes especially for iOS and its devices, the area where I think the threat to the web is worst. But it extends to the Mac as well. Even if you maintain that the Mac will never merge into iOS (a position I find disingenuous), there’s no question that spending money on Mac hardware is a way of indirectly feeding the beast. Next time I buy a laptop, I’ll be sad not to be getting a pretty MacBook, but, on balance, I feel more comfortable giving my money to a hardware manufacturer that’s less pernicious.

For what it’s worth, I don’t think that mine is a decision that everyone must, or even should, make. Using Apple products brings pleasure to a lot of people, even people who largely share my ideologies about the free web. It’s perfectly legitimate to decide that the benefits you get from using those products outweigh the downsides. But, for me, it’s past the tipping point, which is why I’m done buying Apple products.

No related posts.

The very cute card was inscribed, in part: “Commissioned by Paul Gibbs. Made by Andrea Rennick”. Paul and the Rennicks are a few of my friends from the WordPress and BuddyPress world, each of whom I’ve met in person exactly once. Lately there has been no shortage of reminders that online friends are the real deal; having some of that kindness directed toward me and my family brings it all home. It’s a nice reminder that our geographical distribution – Paul is in Old Blighty, and the Rennicks are in the frozen north – doesn’t change the fact that we’re real coworkers, and real friends.

As a bonus, you can check out a set of making-of photos.

Thanks, Paul, Andrea, and Ron!

Related posts:

1. It’s here – BuddyPress 1.5!!
2. Building a baby photo site with WordPress

The criteria

There were a few things I wanted out of the baby site.

1. Easy (or zero) login for users
2. Control over who has access
3. Optional email notification for new content
4. Easy, javascripty gallery browsing

When I started, I was pretty sure that I’d be able to get all of these things pretty easily, using existing WordPress plugins. I was both right and wrong about this: plugins exist for all of these purposes, but none of them were very easy to implement. As a result, I ended up building several pieces from scratch. I’ll go through each of the criteria, talk a bit more about what I was looking for, and then say something about how it was achieved. By doing this, and sharing the code (spoiler alert: https://github.com/boonebgorges/Hard-G/tree/master/wp-content), I’m hoping that I can help others with similar sensibilities to get started on their own sites.

Non-sucky registration and login

I love WordPress, and I understand the important reasoning behind the decisions that led to the design, but WP’s user registration system sucks. I didn’t want just anyone to be able to create and activate an account. I didn’t want users to have to click an activation link. I didn’t want users to have randomly generated passwords that would need changing later on. And I wanted users to have the option of logging in a non-WP way.

Several of these problems could be solved by using Facebook logins. I’m not willing to give my photos over to the horrific FB leviathan, but I’m happy to piggyback on their login APIs if it will save my family and friends a few headaches. I wanted my users to have the option of clicking a single button that would give my site the ability to provision them based on their persistent Facebook login.

I started by looking at some popular Facebook Connect plugins from the wordpress.org plugin repository. I didn’t really like them. Most were linked to the Comments section of blog posts, while I wanted to use the logins for overall site access. Most were dependent on Javascript for logins, while I wanted to handle logins on the server side. Most used an outdated version of FB’s API (or at least of the PHP API classes that FB offers). And, to be blunt, most were too much of a mess, having been retrofitted many times over, and as a result next to impossible to extend. I tried modifying one or two of the more popular FB-WP plugins to do what I wanted, but I ended up writing so much garbage spaghetti code that I decided to cut my losses and start from scratch.

So I boned up a bit on the FB API, and wrote a small plugin that I call Wally Login. Together with the registration page template from my custom theme (a child of TwentyEleven), it does a couple of key things.

Your choice

• Rudimentary access control · If a non-logged-in user tries to visit any page on the site (other than the registration page), he is redirected to the Register page.
• FB login integration · If a user clicks the “Log me in using Facebook” link, they’re directed to the FB authorization page for my website (which is registered as a Facebook app). There, they’re asked to approve the app – a one-time process – and are then returned to my site. Based on the display name, email address, etc that I get from FB, I create a WP user corresponding to the FB account. On future visits, approved users who are logged into Facebook will be automatically logged into my WP site whenever they visit it (an important point, because FB cookies are persistent over browser sessions, while WP logins, by default, are not). As a result, in the best-case scenario, a user will authorize their FB account with my site one time, and will never again have to think about authorization on Wally’s page.
• A customized WP registration process · If users opt not to go the FB route, they can create a WP account directly on the site. I wanted to avoid sending users to an unthemed wp-login.php or wp-signup.php page, so I cribbed a few lines of code from BuddyPress and made my own registration and login dialogs. Wally’s site is part of a larger WP network, but I wanted to bypass WPMS’s built-in registration stuff (which requires users to activate their accounts, and is thus generally too hard for newbies to grok). My custom registration therefore creates the user directly (with wp_insert_user()), using a password that he provides, and skips the activation email. (By bypassing account activation, I’m removing an important spam prevention tool. More on that in the next section.)
• Customized email notifications · Because I’m not using the built-in registration process, I needed to write my own email notifications for account applications and approvals.

If you decide to use my code, keep in mind that it’s not particulary beautiful. I wrote it for my own use, which means that it will take a bit of elbow grease to get it to work on your own site. In particular, if I were writing something for more general distribution, I would not be so reliant on a theme template as I am here. But if you’re looking to create a site like mine, this code is a great place to start – especially the FB integration stuff, which has made the registration and login process about as smooth as it can get.

Access control

The final important thing that the Wally Login plugin does is to provide me (the site admin) with control over who has access to the site. There are a couple ways I could have approached this issue. One is to whitelist users ahead of time. The problem with this is that I’m bound to forget some names, get email addresses wrong, and run into other problems that stem from my unfortunate lack of omniscience. Another strategy is the invitation code. When unique to the individual, this method suffers from the same drawbacks of the whitelist; when non-unique (ie when everyone uses the same invitation code) it takes away much of the security, as the code can be passed around quite easily; either way, invitation codes are clunky, easily misplaced, and all too often mistyped.

Thanks for applying

As a result, I ended up going with a third option: an application and approval process. Here’s the idea, conceptually. Anyone who wants can create an account on my site (either through Facebook or natively; see the previous section). However, the account does not actually allow access to the site unless the account is also approved by the administrators. Thus, after the initial application, two emails are sent: one to the applicant saying “thanks for applying, please be patient”, and one to me saying “there’s a new applicant, please approve them”. Then I go to my approval interface and click the Approve button (if I want), which marks the user as approved in my database and sends them an email saying “You’re in!”

Here’s a brief description of how it works technically. All applicants have a WP account created for them. Every new account is marked, at the time of creation, with user_status = ’2′, and I make sure that no page other than Register can be viewed by an account with user_status = ’2′. In this way, I am turning the idea of activation around a bit – natively, WP makes the user do the activation, but in my case I do it. The admin tool I use to activate users is my Unconfirmed plugin, designed for a slightly different purpose but quite at home here. (For technical reasons, Unconfirmed needs users to have activation keys; thus Wally Login also generates some dummy keys during the user creation process so that Unconfirmed will work right.) Unconfirmed, in turn, does the work of flipping user_status to 0 upon approval.

Taken together, Wally Login and Unconfirmed (with custom WP registration, FB integration, user approval by admin, etc) has given me a comfortable level of access control, without making the process unduly difficult for my users.

Email notification for new content

One of the biggest drawbacks of creating a standalone picture site instead of using an all-purpose social network (in practice, this means Facebook) is that the standalone site is likely to be forgotten. FB collects all of your network’s activity into a single stream; it’s highly unlikely, on the other hand, that Wally’s site will become part of anyone’s daily routine, so that they stop by to check for new content. For that reason, good email notification of new content is essential to making the site work.

Dead simple email subscription

I first tried using the popular Subscribe2 to handle these notifications. But I ran into a bunch of problems. For one thing, I didn’t like that S2′s subscription management happened in the Dashboard – I want to keep my users on the front end. S2′s category-based subscription is too complicated for my site, where people are either going to want to subscribe to all posts or to none at all. And the widget that comes with S2, for display on the front-end of the site, is pretty much atrocious. (Sorry. The rest of the plugin is nice. But that widget sucks.) At first I tried solving these problems just by building my own widget for S2, one that would tell the user whether he was currently subscribed, and show an Unsubscribe/Subscribe button, as appropriate. But, given the structure of S2′s data (which is somewhat arcane, and in any case far too complicated for my purposes), it ended up being a lot harder than it should have been.

So – wait for it – I wrote something from scratch. It is dead simple. Two parts: (1) a widget, which does exactly what I describe in the foregoing paragraph; and (2) hooks into publish_post to send an email to all subscribed users (along with some gentle checks to make sure dupes are not sent). This plugin has no admin UI and no options, because I don’t need any of those things.

Pretty galleries

Since the main point of the site would be to look at lots of pictures, it was quite important to have an easy, pretty way to do so. By “easy” I mean, primarily, navigable by keyboard; by “pretty”, I mean, primarily, bigger than the content area of a typical blog post. Less important, but still desirable, was the admin interface: I wanted it to be easy to upload lots of pictures at once, to add captions and other metadata if necessary, and to turn it all into a gallery that would look good on the front end.

Pretty, easy

You know the drill: I tried a couple of the more popular free plugins, but all of them were annoying in one way or another, and each one was way overengineered for my meager needs. I was especially disappointed by the back-end admin for the popular gallery plugins, which I found lugubrious, unintuitive, and impossible to extend. After some consideration, I decided that I actually preferred WP’s native Add Media interface for uploading photos and adding metadata, and that I was perfectly happy with the way that WP’s gallery shortcode displayed content on the front end, at least when viewing thumbnails.

So the only thing I really needed was to implement the javascript that would allow for keyboard navigation and lightboxing of gallery photos. Thanks in part to his extremely uncreative and literal plugin naming schema, I found Viper007Bond’s jQuery Lightbox For Native Galleries plugin. It does almost exactly what I want, right out of the box.

I did make a few minor mods, though. First, the plugin is a bit greedy in the way that it filters the output of get_attachment_link(), which was either breaking things (as in the case of comment_post_redirect on attachment posts) or making it hard to display links to the attachment page instead of the raw attachment file. The former problem I solved with a filter; for the latter problem, I was a bit lazy, so I modded the plugin itself in addition to adding an explicit ‘lightbox’ class to attachment links. This combination of hacks makes it work perfectly for my purposes.

Odds and ends

A little bonus

With my absolute requirements met, I was able to add a few other goodies to the site. My theme is a child of Twenty Eleven, which I’m pretty much using as-is. But I’ve added a few fun bits. First, on each attachment page, I added Download links, so that users could download images of various resolutions for printing or editing. I messed with the WP Admin Bar so that users coming from Facebook wouldn’t see Log Out and some other inappropriate links. And under each thumbnail in Gallery view, I’ve added Download/Comments links, so that users could bypass the jQuery lightbox and go straight to the attachment permalink if they wanted.

It took some work, but I think I’ve ended up with a site that is nice to use and easy to maintain, without resorting to the extreme discomfort associated with Facebook. Hooray!

Related posts:

1. Moving my photo site to a new URL and server
2. New WordPress plugin: Simple Import Users
3. BuddyPress and the YOURLS: WordPress to Twitter plugin

He decided to surprise us four weeks ahead of schedule. How’s that for dramatic? Mom and baby are doing great.

Walter Joseph Gorges
6lb 8oz
June 28 2011

Related posts:

1. Project Reclaim and the email dilemma