For now, since the Google+ API is read-only, I’m borrowing inspiration from Luka Puši?’s GPlus Bot and Dmitry Sandalov’s Twitter 2 Google Plus script.

This means emulating the Google+ mobile web experience using Curl.

WPGPlus adds a box to the post edit screen where you can choose yes/no for publishing to Google+, as well as a place for a message to be used in the body.

(If you provide a Google+ message it is used; if you provide a post excerpt it is used; otherwise post content is used).

Anyway, check it out and let me know what you think!

1. Eliminate the canvas page and tab altogether – make WPBook just focus on cross-posting and comment import, thus potentially eliminating the SSL requirement?
2. Make it optional – keep the canvas page and tab, but make them optional – only for users who want them and have the necessary SSL certificate
3. Fork the plugin – make a version of the plugin which works like the current model, but also a second (WPBook Lite?) that only does cross posting and comment import? That way we could have separate directions for each to simplify setup confusion
4. Stop developing WPBook – There are a number of other plugins which do Facebook posting, and at least one which does Facebook comment importing (probably more). Is it worth continuing to develop WPBook if better alternatives exist?

Ultimately, I settled on Option 3: Fork the plugin, and create a lighter-weight version which did not include the canvas page or tab. The result is WPBook Lite, available now in the WordPress Plugin Repository.

Should I use WPBook, or WPBook Lite?

I suspect this will be the main question folks will face, so here’s a quick comparison table:

Basically, if you are able to access your blog via HTTPS, and you WANT the view of the blog inside Facebook as a canvas application, or you want the page tab feature, you should use WPBook.

If your blog is not accessible via HTTPS, or you don’t want the view of the blog inside Facebook / page tab, then you should be happier with WPBook lite.

I’ll be updating the instructions over at WPBook.net shortly to reflect Facebook’s new look for developer settings shortly, and will also differentiate between WPBook and WPBook Lite. In theory, configuring WPBook Lite should be significantly simpler for most users.

If you’re already using WPBook and shift to WPBook Lite, you will need to regrant permissions.

Migrating from WPBook to WPBook Lite:

1. View your WPBook settings page, and write down your profile ID as well as the IDs of any pages/groups to which you want to cross publish.
2. Deactivate WPBook (but don’t delete it yet)
3. Install and Activate WPBook Lite
4. Set up a new Application for WPBook Lite – this time you should only need the “Website” settings under Integration, not any of the “App on Facebook” section settings
5. Visit the WPBook Lite settings page in WordPress, fill out the required fields (APP ID, Secret, your profile ID), and save the form
6. Re-visit the WPBook Lite settings page, where you should now see an opportunity to grant appropriate permissions

If done correctly, WPBook Lite should pick up right where WPBook left off.

If you run into problems, please comment in the appropriate WordPress Support Forums: WPBook or WPBook Lite.

Pittsfield in the Near Future (from Cameo Wood on flickr, cc-by-nc license)

The first is a change Facebook has made, requiring SSL certificates for “all Canvas and Page tab applications.” (They announced this change earlier this summer, as part of the bizarrely Orwellian “Operation Developer Love” but it went into effect as of October 1st).

This is a problem because many WPBook users’ blogs are not available via https connections (including my own), and with this new Facebook change their WPBook implementation will fail, though how exactly that will be manifest isn’t clear to me yet (see below). Getting an SSL certificate for your blog isn’t an insurmountable task, but if you run your blog on cheap shared hosting, the costs of an SSL certificate (and the dedicated IP it requires) can be nearly as much as you’re paying for hosting! It’s also a task that the non-technical user will find horribly confusing.

The second is a recent report showing that:

Using a 3rd party API to update your Facebook Page decreases your likelihood of engagement per fan (on average) by about 80%

The study results suggest that one of WPBook’s core functions – posting automatically to your wall (or the wall of a fan page, group, or application) whenever new blog posts are published – might not even be a good idea to begin with.

Facebook posts direct versus via 3rd party APIs (Edgeranker study)

If third-party automated postings get de-prioritized by Facebook, you might be better off using a Facebook share button and manually cross posting to Facebook each time you publish. On the other hand, maybe the reason third-party automated postings get less attention is because people post more crap weak content that way. (If what the 10 most popular third-party apps post is lots of nonsense about games, thinly veiled ads, and self-promotion, maybe that is what the study results show people are ignoring – not that good relevant content posted by automated applications gets ignored).

So, what’s the way forward?

The scenario I’m imaging is to split apart the functions of the current WPBook and make some portions optional.

WPBook currently does four main things:

1. Expose a view of your blog as a Facebook application (a canvas page or set of pages). Basically this is an iframe inside Facebook containing your blog content, drawn by WordPress in a theme supplied by WPBook, to make it look more like other Facebook pages.
2. Expose a view of your blog as a “tab” for use on Facebook pages. This is also iframe based, but a bit different in terms of what is allowed in that tab.
3. Cross-post to Facebook whenever a new blog post is published. (To your personal profile wall, or to the wall of a Fan Page, Group, or Application, or some combination thereof).
4. Import comments made against those wall posts, and make them WordPress comments

I believe that the Facebook requirement of SSL only affects numbers 1 and 2 of this list. Even in the current WPBook, if you set “use external permalinks” then users never need know your application canvas page exists – they will just click on the links in wall posts and be taken to your (external) blog. Users without SSL certificate capability (or interest) could still get the benefits of 3 and 4 without having to worry about 1 and 2.

(It’s not clear to me right now how this would impact setup of WPBook-based applications. Facebook’s developer blog clearly indicates that canvas and page-tab applications will require SSL, but that would seem to imply other kinds of applications will not. Is it just a question of choosing a different application type during setup in Facebook? The whole app creation flow has changed so many times it is hard to keep track – maybe it is a question of unchecking some of the boxes in the dialog below?)

New Facebook App Creation Options

So the question becomes, is it worth it to keep WPBook trying to do 1 & 2 above?

Originally this was all WPBook did, and it seemed to me quite useful and distinct from any other Facebook related plugin. In essence you could use WPBook this way to drive a whole in-Facebook experience and never require (or even let!) users go to the blog outside of Facebook (though preventing them from accessing the blog outside Facebook would require some extra work on your part).

Open Parenthesis, as seen outside Facebook (left) and inside Facebook (right) - click for full size

But most users, it seems to me, were confused by this “Facebook view of my blog” approach. They wanted cross posting, and comments import, but didn’t like the application view of the blog (which required all users viewing blog content to consent to application permissions) or worried about it taking traffic away from their external blog.

Should I:

1. Eliminate the canvas page and tab altogether – make WPBook just focus on cross-posting and comment import, thus potentially eliminating the SSL requirement?
2. Make it optional – keep the canvas page and tab, but make them optional – only for users who want them and have the necessary SSL certificate
3. Fork the plugin – make a version of the plugin which works like the current model, but also a second (WPBook Lite?) that only does cross posting and comment import? That way we could have separate directions for each to simplify setup confusion
4. Stop developing WPBook – There are a number of other plugins which do Facebook posting, and at least one which does Facebook comment importing (probably more). Is it worth continuing to develop WPBook if better alternatives exist?

My concern with option 2 (“make it optional”) is just that configuring WPBook is already too complex for many users, given the variety of ways Facebook can be used and the variety of ways WPBook can be configured. Adding yet another set of variants (which would change not just what you have to set inside WordPress but also what choices you make when setting up the corresponding Facebook application) will only increase complexity and therefore support requests, which I honestly just don’t have the time to answer as quickly or extensively as I’d like.

My concern with option 3 (“fork the plugin”) is similar – more work for me, when I’ve had difficulty keeping up with plugin maintenance and maintenance of the instructions as Facebook constantly changes their application settings pages. If maintaining one plugin is difficult, maintaining two will be more so, even if they share some segment of the code base.

So option 1 (“eliminate”) is perhaps the simplest. (I say “perhaps” because I haven’t looked into it in depth yet – how hard will it be to untangle all the permission setting and checking logic, which is currently using a canvas page to display the current permissions? How will that change existing applications built using WPBook?).

But once that’s gone, what distinguishes WPBook from all the other Facebook posting plugins?

The fourth option would be to just declare WPBook obsolete. Existing WPBook installations work, if the user’s blog supports SSL. Currently if users browse Facebook in https mode, my own WPBook-powered applications just don’t work, because I don’t have SSL certificates for any of my blogs – just not worth the effort. But I’m ok with that.

It may be seems that new WPBook users will find they can’t set up a Facebook application (necessary to use WPBook) without an SSL certificate, and if they want to have cross-posting and comment import they’ll need to use an alternative approach, but a quick search of the plugin repository suggests other options are plentiful.

I’d love to hear from you all – especially if you are WPBook users (it’s had over 100,000 downloads, but I’ve no idea how many are in active use).

• Are you using the “Canvas Page” or “Tab Page” views inside Facebook? If so, do you have an SSL certificate for your blog? Would you miss these views if WPBook were revised to eliminate them?
• Have you evaluated other WordPress plugins for accomplishing the same thing? Did they work, or what issues did you run into?

As always, comments (and patches!) welcome.

Here’s the video, including Q&A:

Wish I’d been able to make it!

Now You See it

Cathy Davidson‘s Now You See It argues that the educational system in the US is failing to prepare graduates for the work they will be doing in the 21st century. While I found myself vigorously nodding at the general argument of the book, there were also some places I wished Davidson had developed in greater detail.

The best part of the book for me is the description of the roots of our standard educational approach going back to the early 20th century: Taylorism, the IQ, and standardized testing on a large scale. These approaches made sense when education’s focus was the creation of disciplined, managerial, bureaucratic middle-managers for hierarchical, command-and-control corporations.

Unfortunately, while the workforce is adapting to new realities of globalization, the digital revolution, and commons-based peer production, the educational system has not kept pace.

She’s definitely on to something, and I agree with much of her rant in both its aims and its general tenor. She’s also generally compelling when she talks about the variety of approaches they’ve taken at Duke (distributing iPods, how to crowdsource grading) and that she’s experienced as director of the HASTAC program (and as an all-around digital humanities evangelist).

The book’s a bit weaker, for me, when she tries to describe alternative educational approaches which embody the values and approach she wants to promote: collaboration through difference, game mechanics, and creative expression over standardized testing. They end up resonating as anecdotes but don’t provide a true alternative program which could be managed at any broad scale.

I also found the sections on what the modern workforce is like rang a bit hollow. It’s easy to critique Prof. Davidson as an academic – the old “Ivory Tower” versus “real world of work” contrast – but I think it’s fair to say that Davidson doesn’t reflect deep lived experience here in describing the “average” office worker, whatever that might mean.

If you have a job just about anywhere but Google, you are most likely working in a space designed for a mode of work that is disappearing. . . . We’ve just begun to think about the best ways to restructure the industrial labor values we inherited in order to maximize our productivity in the information age.

Maybe it’s just because I’ve spent the last 12+ years working in interactive agencies, on web projects, and with open source communities, but the descriptions Davidson offers of all the signposts of the new felt immediately familiar to me, as I suspect they would to anyone working in web strategy, design, and development. Global conference calls supplemented by a digital backchannel (irc / IM, over public networks or internal intranets) and web-based collaboration environments (maybe we don’t all use Second Life, but the specific technology isn’t really the point), working toward consensus and community-driven decision making over command and control – this is how everyone I know works!

Again, I don’t think this takes away from Davidson’s primary point about the organization of the educational system in relation to the way work actually happens – I just think the new mode of work is even more widespread than she suggests. It isn’t just the denizens of the Googleplex or Big Blue who are working in a collaborative, technology-embedded, continuous partial attention world. (It’s also not just agencies, based on what I’ve observed at clients).

The second place where I wanted more from Davidson was in what industry likes to call “the solutions space.” Other than reducing class sizes, and decreasing reliance on standardized tests (which drives the behavior of teaching to the test rather than the kind of critical thinking, research, and collaboration skills Davidson emphasizes), what path should educators (or parents) take?

Davidson gestures in the direction of solutions with a few specific cases of schools and a broad discussion of game mechanics (cue Jane McGonical). Would substituting boss challenges for end of grade (standardized) testing be both radically productive in improving education and sustainable at large scale? If every university starting giving students iPods (or perhaps now iPads) and eliminated letter grades, would that magically shift the conversation back to creativity and collaboration?

I was also concerned at Davidson’s fast and loose use of “crowdsourcing” and “open source” as though they were interchangeable or nearly interchangeable references to work done by large groups. (The simple fact that she’s talking about cooperative production and there isn’t a single mention of Yochai Benkler’s The Wealth of Networks or The Penguin and the Leviathan or, for that matter, the Public Library of Science, or Open Courseware). There’s one quick nod to Creative Commons but it’s dismissive: “it’s not always a simple matter in a collaborative endeavor to agree to ‘share alike’” (232).

Instead we get broad references to “open source” via Linux and Mozilla, and crowdsourcing via Wikipedia, but with no clear definition or explanation of how free software and open source communities came to be or organize themselves. There doesn’t really seem to be any recognition of the core freedoms open source is really about. She cites the Cathedral and the Bazaar, but never really explores why or how this mode of production compares to traditional software (which is very much still present and arguably even dominant in education). There doesn’t seem, for example, to be any concern about the involvement of companies like Apple and in driving educational initiatives. What does it mean to train students on a proprietary platform when free platforms are also available? What impact might the free software and free culture movements have on institutional education (elementary on through tertiary) if we took seriously their challenges to proprietary software and big corporate media?

(Starter Recommendations: Chris Kelty’s Two Bits: On the Cultural Significance of Free Software, Gabriella Coleman‘s research on the ethics of hackers and hacking.).

Promising Whiteboard Sketch for Mozilla Education - photo by Mark Surman, cc-by-nc-sa license)

The last major gap I was surprised to see Davidson not explore further is alternative educational approaches. There’s no mention of homeschooling or diy education: increasingly used by significant segments of the population to opt-out of the institutional part of the educational system. Would she support this approach, as it is inline with adaptive learning and flexibility and anti-standardized testing, or would she bemoan the approach as it doesn’t provide enough collaboration? (Of course, home-schooled students could collaborate online with others, which might pretty closely mirror the life of the new IBM consultant – some have said IBM stands for “I’m By Myself”).

In the end, Now You See It is a compelling read if you’re interested in the failings of standardized testing, and exploring more creative, internet-era-appropriate methods of education. The challenge it raises to educators is a signal one: how are we checking our own institutional biases in favor of really exploring what students will need in the workforce, and how can we make school more like the new workplace?

As someone who’s argued that Lolcats belong on your corporate intranet, I’m sympathetic to Davidson’s desire to recuperate the reputations of internet “distractions” and recognize that it is ok that kids like video games and that students might spend part of their school day on thinking that is not immediately measured on a multiple-choice test. I just wish there was a more specific program of actions we could take to get there, as I want to play along.

LOLCats on teh Internet (Click here to expand)
Source: Online Education

Even at a smaller camp there were multiple parallel tracks of presentations, and I found myself wishing talks had been recorded so I could see some of the ones which overlapped, my inability to be simultaneously two places at once hold me back yet again.

Program for DrupalCamp CT 2011 - click for larger

My favorite sessions of the day were Benjamin Melançon‘s “When there isn’t a module for that” and John Zavocki‘s keynote “From the Margins to the Center.”

Ben’s talk, which was an updated version of a talk he gave at Western Mass DrupalCamp (which I was not able to get to, but for which slides are available), covered the basics of Drupal module development using the x-ray module as an example. Nothing new for an experienced developer, but presented with clarity, color commentary promoting the community ethic, and humor, including this graph of “Community Karma Required to Escape Punishment” for specific crimes:

Community Karma Required - from Benjamin Melançon's slides (click for full size)

He was also the lead author (coordinator? driving force?) of The Definitive Guide to Drupal 7, and brought a copy to show. That is one serious tome of Drupal knowledge – over a thousand pages! (Ok, I’m including the index – but it really is massive).

One of Ben’s core themes – the ethics of contributing back to the community in multiple ways and at multiple levels – also ran through John Zavocki’s keynote. (John uses a mindmap to present rather than slides – he’s put two versions of the mindmap up on his site).

Zavocki – an engaging presenter with more than a touch of self-deprecating humor – starting by announcing this was his first keynote, and therefore was either going to go extremely well or suck entirely: turns out it was the former. A self-described fourteenth-century Venetian painter with post-modernist and feminist tendencies (or was it sympathies?), John focused on what professional ethics might mean to those in the Drupal community, the number of web developers who get to open source via non-traditional or ad-hoc career paths (what, my PhD in literature isn’t standard training for web development?), the need for project management and specialization (“find out what you’re good at and do that – hire people to manage you”), and the importance of reputation and long-term relationships.

In the end, the five-point outline he posted on his blog captures all the right themes, but misses all the crucial energy:

1. Your reputation is the most important thing that you have in our development community
2. If you are not allocating human resources for Project Management, you cannot say that you are doing have ethical business practices
3. Clients want software engineering (results) not Computer Science (theory)
4. Get the right person for the right job
5. The most important thing you can do is contribute back to the project.

After the “formal” section of the keynote was over, the audience kept feeding on his energy, asking questions and engaging with him on his sense of where the Drupal community is going. I wish I had some video of Zavocki jumping up and down on stage pointing to the mind-map projected behind him, if only to convey some essence of the experience.

It was also good to see such a strong Drupal community at Yale – yet more evidence of how Drupal is enabling higher education institutions. During the lunch break I had a chance to walk a bit around campus. The camp venue – Luce Hall – is on Hillhouse Avenue, a very storied street which Wikipedia tells me both Charles Dickens and Mark Twain declared “the most beautiful street in America.” Luce Hall itself doesn’t quite fit the description, being instead one of “Yale’s architectural embarrassments.”

(Photo by Adam Solomon, cc-by-nd license)

It’s Henry R. Luce Hall, of course, after the Yale Alumnus, founder of Time, Life, and Fortune, also, later, the staunch anti-community and author of “The American Century” – I wonder what he would have made of the impact of the internet on mass media publishing, as well as the open source movement and its core ethos of cooperation?

What would the “Lord of the Press” have made of citizen journalism, the rise of the hyperlocal, and a real-time web in which nearly anyone can become the source of news?

This year’s camp promises to be even bigger than last years, with content from 30+ speakers spread out over one and half days at the Boston University student union. We’ve even got a pre-conference workshop the Friday before and a reception Saturday evening at the Microsoft NERD center.

If you haven’t already got tickets, you’ve missed regular registration, but you can still get in on late registration (which just means you’re in line after the regular registration folks for lunch and T-Shirts) for just $40.

Back in the beginning of May, I left Optaros and started working across the river in Cambridge at ISITE Design.

I spent five years at Optaros, and learned a tremendous amount from both the leadership and the staff with whom I delivered projects. I spent time in Switzerland, Germany, and London, as well as Austin and San Francisco, working in Optaros offices and on client sites. I wish them continued success in the social commerce / innovative commerce world; but it was time for me to move on.

ISITE Design is a smaller (~60 person) digital agency, which has been delivering to clients for 14 years. We’re headquartered in Portland (OR), with offices in Boston and Los Angeles. I first became aware of ISITE Design when they launched the CMS Myth back at Gilbane Boston in 2007. I’d met the “mythbusters” and other ISITE Design leadership folks over the years, and always respected their commitment to clients, to organic growth, and to putting strategy at the center of the digital conversation. (It’s also the home of El Consultador, one of my personal inspirations as a consultant).

At ISITE, I’ll be focused on digital strategy and account management, helping to grow the ISITE presence nationally and continue to build on ISITE’s core CMS practice. I hope to also help bust some myths about open source CMS’s, if we can just find a cape that fits . . .

Here’s just a bit of what’s been happening at ISITE since I joined – sign up for ISITE Insight to stay informed:

• ISITE Design were finalists in the MITX Innovation Awards, in the “Doing Good” category for Food Hub, a Portland based exchange for connecting local food producers with their customers
• We launched Day2, an optimization service “to help organizations measure and improve their digital channel with data-driven insights and actions”
• ISITE was named (again) to Portland Business Journal’s Fastest Growing 100 Private Companies list – and received a Lighthouse award for having been on the five years in a row!
• We bought a building in Portland, for the new corporate headquarters. Plans, photos and more: breaking ground

In other words, it’s a pretty busy place, full of smart people with a dedication to doing good work and helping clients succeed. Just the way I like it.

Try Again (Photo by Samantha Marx, cc-by license, http://www.flickr.com/photos/spam/3355834452/)

Spent some quality time this weekend with WPBook. As a result, I just released version 2.2.1. (There was briefly a 2.2 release, but something was corrupted in that version of the SVN repo, so use 2.2.1 instead).

Included in 2.2.1:

• Read More is back. Re-enabled the “Read More” action link. Unfortunately, because of a Facebook API bug wpbook can’t add more than one action link to a post, so no “share” button on wall posts until that is fixed. (Facebook doesn’t add the Share link automatically to posts from the Graph API and there’s currently no way to make that happen other than manually adding it as a link, but I think the “Read More” link is more important.)
• Post to Group Walls. Added posting options for Group walls, and comment import form Group walls. Because of the way the Facebook API has changed, posting to a Group feed is distinct from posting to a Page’s feed, and requires different syntax.
• Controlled debugging. Limit the size of debug files created to 500k, so that users who enable debugging and then forget won’t have an unlimited file growing every hour. Also made the debug constant more specific to WPBook so as not to interfere with other plugins potentially using DEBUG as a constant
• Fopen errors. Clean up DEBUG for cases where permissions fail or file is not writeable
• Facebook::$CURL_OPTS . Made “disable ssl verification” an option so that only users who need it will have it and others won’t get conflict
• Required fields are required. Cleanup to the admin screens in general, more clarity around what is required and better language on the admin screens about what is being checked. (Thanks BandonRandon for patches)
• Better check permissions. Improved “Check permissions” page, to show what options mean and enable links to view profiles, pages, links to validate IDs are correct.
• Added wpbook logo which had been missing
• Fix for get_themes() issues with WordPress 3.0.1 through 3.0.5

I realize from the activity in the forums that many users are having trouble with the 2.1 and later WPBook – but I believe all the known errors have been fixed, and most are due to misconfiguration.

A few configuration notes that might help:

1. Your application ID, secret, canvas URL, and Profile ID must be correct or nothing else is going to work. If you load your application canvas page and you don’t see the WPBook theme, but see just your blog in an iframe (unchanged), then something is wrong in your Facebook Application setup, your WPBook setup, or in a plugin conflict.
2. Your personal FB profile is absolutely required, even if you don’t plan to publish to your profile’s wall. It is through the FB profile that the access_token for publishing to pages is retrieved. If your FB profile ID is wrong, nothing else is going to work.
3. Any time you change the Profile ID, the Page ID, or the Group ID to which you are trying to publish, you must visit the Check Permissions page and will most likely need to regrant permissions. Again, if permissions aren’t working, nothing else is going to work.

If you’re stuck, please open a new thread in the wordpress forums and provide the following debugging info:

• The URLs of your Facebook Application and your blog outside FB
• The contents of your check permissions page – verbatim
• What you are trying to publish to – profile, page, group – by ID and by URL
• What error messages you are seeing, in the WordPress interface and/or in the PHP error log

With the right information, we will be able to get it working.

Thanks

Code Bug (Photo by Guilherme Tavares, cc-by license, http://www.flickr.com/photos/guitavares/1703252007/)

Just released WPBook 2.1.4.

Two key bugfixes in this release:

1. Comment Imports. In changing to the Graph API I needed to add an access_token to the FQL calls I’m using to retrieve comments from non-public streams.
2. Facebook Avatars for Pages. Given that you can now comment on wall posts as a page (by using the “use Facebook as page” option if you are the admin of a page) some of your comment authors in FB might be pages themselves. This fix will get the right FB avatar for them, eliminating what was otherwise a broken link image.

There should not be any need to regrant permissions or change any Facebook settings in this release.

Thanks to all the users who’ve provided feedback (and debug files!) in the forums.

Note that if you’ve already made the changes described in upgrading from 2.0.x to 2.1 you do not have to redo them, though you will have to regrant permissions (in order to fix #s 1 and 2 below).

Three significant bug fixes:

1. Access Token storage. In 2.1 and 2.1.1 I had been storing the access_token Facebook returns after granting permissions in the user_meta table, which worked, but only if you were always publishing in WordPress as the same user who granted permissions. (The same WordPress user_id). Now this gets stored in the options table and works regardless of who is logged in, which makes more sense for the publish action in the first place.
2. Publish as a page. This required getting the “manage_pages” permission, so you will need to regrant permissions (visit the WPBook options page, click on the “Check Permissions” link inside the Stream/Wall options section, and then click on “regrant permissions” on the resulting page inside Facebook). Basically once you’ve granted “manage_pages” permissions, WPBook looks for the page you’ve identified as a target, and fetches and stores a new access_token that is specific to acting as that page. This access token is then used to publish to the page’s wall, so that they appear to come from the page, not from your FB user id.
3. Post Thumbnails. This was more badly broken than I thought – not sure how it worked in my testing. (My guess is that FB grabs an image even when you don’t provide one, and may have accidentally grabbed the right one when I test-posted). But it works now, provided you have actually indicated a post-thumbnail (or “featured image” as it is now called in the WordPress admin).

What may still be outstanding is support for WordPress 3.0.1 and potentially other versions between 2.9 and 3.1. Please do open a thread in the forums if you are using an older version of WordPress or having other issues.