I’ve started putting together a Developer’s Guide to working with Keyring in your WordPress plugins and themes. Check it out.
If you haven’t seen Keyring yet, then check it out at the WordPress.org Plugin Repository.
I’ve started putting together a Developer’s Guide to working with Keyring in your WordPress plugins and themes. Check it out.
If you haven’t seen Keyring yet, then check it out at the WordPress.org Plugin Repository.
It’s true, I really want to love the Pebble that I got from being a Kickstarter backer. I want to, but right now I can’t. I can only like it. And I can like it a lot — there’s a lot to like!
So why can’t I love it? Let me count the ways (biggest reasons first): Read the rest of this post…
I used to maintain a wiki full of personal ideas using DokuWiki, but at some point just gave up with wiki syntax entirely. A few months ago when I was moving all of my sites and content over to a new server and trying to consolidate things as much as possible, I decided to import all of that old content into a WordPress install (which was actually a single site within the same Multi-site install that runs Dented Reality). I ended up writing the following super-rough script to just scrape the contents of the pages and throw them into WordPress. Scraping the pages meant that I could get the actual output of all plugins etc, and also get full links between pages.

I should be getting my Pebble soon, and I can’t wait. I don’t really care about the fancy watch faces, I care about bringing timely information and notifications out of my pocket and onto my wrist. As far a I’m concerned, this is one step closer to something like Google Glass.
On Saturday, I attended the 2012 New Times/TimesOpen Hack Day. It was a long day, but I had a lot of fun. I sat in on an intro session to Arduino which was pretty cool, and also a session on the EchoNest API, which I ended up using in my project. You can find out all about my project on the Readtrack project page.
It’s a bookmarklet-powered little app that analyzes the page you’re looking at (using the AlchemyAPI) and then tries to find related music (using the EchoNest API) which it then plays back to you in your browser (using rdio). I got a “runner up”/honorable mention prize
One of the most visually-polished projects was “Story Arc”, which showed a visual representation of the frequency of mentions of keywords over the NYT archives. Probably the most fun one was a set of drivers for a DDR pad, hooked up to commands for things like deploying code!
I’ve made a bunch of updates to WP Email Login (local project page) recently, and it’s still rocking along. If you’d prefer to log into your WordPress install using the email address associated with your user account, you should check it out.

Last night, I preemptively tweeted about the upcoming release of Jetpack 2.0:
I can’t wait for the very-near release of @jetpack 2.0. It is loaded with awesomeness and magic.
— Beau (@beaulebens) November 7, 2012
I’ve been using WordPress to power my own website for a while now, and working with it in some way or another for even longer. Over the years, I’ve developed the belief that it’s a pretty perfect platform for people to build their own “digital home on the web”, considering the range of plugins and themes available, the flexibility of the publishing options it offers, and the fact that it’s completely open source, so you can do whatever you want with it.
That last bit is important in more ways than you might immediately think. Apart from just being able to write my own plugins or tweak my themes, this also means that I own my own data. I think in this MySpace/Facebook generation, people are all too loose with the data trails they create — giving up ownership of their digital self at the drop of a hat. In case you didn’t realize, when you use something like Facebook, it is not the product, you and your data are the product.
I’m working on a new WordPress theme (for this site, and it’ll be released for download once complete). The theme is deeply integrated with Jetpack, and one of the things I wanted to do was have the Jetpack Sharing buttons appear in a location other than the very end of the content. Normally they are applied as a filter on the_content, so they just appear right at the end. I wanted to relocate them into a different location, and it turns out that’s really easy to do with the power of jQuery.
jQuery( document ).ready( function( $ ) {
// Relocate Jetpack sharing buttons down into the comments form
jQuery( '#sharing' ).html( jQuery( '.sharedaddy' ).detach() );
} );
The #sharing selector is just the DOM location where I want to move the buttons to, and the .sharedaddy one is the container that Jetpack places its buttons in normally. We just detach it from the normal position and then dump it into the new location exactly as it was.
I’ve finally gotten around to moving this site (along with all my other random sites) onto a single server. It’s all now hosted at Media Temple, on a 512MB (dv). We’ll see how that goes. I’ve got a bunch of things to write up once the move is complete, but if you’re seeing this then it looks like we’re most of the way there.
There’s definitely some more tuning and tweaking to happen, but at least I have my memory usage below 100%