I *think* I’ve worked out the necessary changes for WP 3.6 post formats compatibility in FavePersonal (the theme used on alexking.org).

The true measure of a new best practice is how painful it is to return to projects that don’t use it.

When experiencing the issue, I was on my (retina) MacBook Pro disconnected from an external monitor. I had been previously connected to a Dell monitor multiple times between then and my last reboot. Based on some tips I saw online, my first step was a reboot which restored Screeny to normal operation.

To test the “external monitor as cause”, I reconnected to my monitor and tried recording on both screens:

- laptop screen: success
- external monitor: success

Then I disconnected from the external monitor and tried again on just the laptop screen: success.

So I have no idea what happened, or how it got “fixed”, but I recommend trying a reboot if you see this issue.

I’ve been finding App.net making it’s way into my social stream more and more these days. With the folks I’m following, I’ve seen engagement ramp from around 5 posts/day to 25-30 posts/day – seemingly overnight. It definitely has that “early Twitter” feel at the moment.

I’ve been looking into some of their technical bits too because I’ll probably create an App.net Tools plugin for WordPress to enable the same “post here, participate there and my data is my data” workflow I use with Twitter and Facebook.

The recent implementation of two-factor authentication is quite nicely done and my experience asking questions in the developer Patter room was extremely positive.

Give it a try, see if it’s for you.

My day always brightens a bit when the API I’m talking to will send back JSON data.

#

What is a simple screen recording app for the Mac that works with retina? Screeny (my previous go-to) fails, as does Voila. #lazytweet

#

Happy Friday!

#

If you create them wisely, everything fits together neatly and you have a lovely creation you can build upon and adapt in the future.

If you create them foolishly you can still mash them together to create your thing, but it will be a real bear the next time you need to make an adjustment to it.

This is something that I put off for three years because I was having all sorts of weirdness with time calculations on my local machine vs. the server GameTonight is running on. Thanks to Joe and his incessant nagging constant encouragement, I slogged through the necessary debugging this morning and finally got things set.

I know enough to know that whenever you’re working with dates and times, you want to do everything in GMT then convert out to a local timezone as a very last step. I also know that you probably want your app code to run in GMT rather than looking at the server’s timezone.

In trying to be careful about doing these things right, I learned a bunch of things that didn’t work. Ultimately the issue was with how mktime(), gmmktime(), gmdate() and date() do or do not use the timezone declared for the app vs. the server’s timezone.

Pro tip: use these in pairs (gmmktime() goes with gmdate() while mktime() goes with date()) and create useful logging functions to test their output on various machines/servers. Or not, your mileage may vary.

Your first step when you think “I want to do a project that involves dates, times and events.” should be to slap yourself in the face.