Hi Eileen! Thanks for dropping by and reading; glad you enjoyed. Hope
your travels have continued to treat you well and that perhaps we'll
cross paths again (in SF or otherwise!).

Yeah that's a major stumbling block actually. Not sure that there's a good solution to it given the way that OAuth works. For part of what I'm doing, it's looking like I might have to use the HTTP Basic approach, as much as I hate that.

That's a very good point. In most of the cases above, there's no such thing as a pure authentication API, although I guess depending on the privileges your application requested (especially for something like OAuth), then it could act as an authentication API if it was just "verify your account details" privileges.

I completely agree :) http://backpress.org/discuss/

Sadly, you're right about the being turned into a city slicker thing.
It's horrible.

I need to get back into the outback and spend some time in the bush!

Yep, you should definitely be able to just drop this script into your
header or footer if you prefer (or if you're not already loading an
external JS file). Just make sure that you're loading jQuery as well,
and it should work just the same.

Hah, glad to hear it. We'll see what we can do about a tutorial
covering that particular part of BackPress. Ideally I'd like to have
tutorials covering every "concept" available within BP, but that will
take some time to put together, obviously. Slowly, slowly!

Hi Brian -- you do indeed need to include a couple of files to get things running, and I'm actually planning to write up a quick tutorial on how to get started using certain parts of BackPress.

In the meantime, I have a project where I'm doing it something like this;

- load configuration file with database details similar to wp-config.php
- include a series of backpress files
- start doing custom app stuff

The second step there, in my case, involves loading these files (in this order);

require_once dirname( __FILE__ ) . '/backpress/functions.core.php';
require_once dirname( __FILE__ ) . '/backpress/class.wp-error.php';
require_once dirname( __FILE__ ) . '/backpress/class.bpdb.php';
require_once dirname( __FILE__ ) . '/backpress/functions.formatting.php';
require_once dirname( __FILE__ ) . '/backpress/class.wp-taxonomy.php';
require_once dirname( __FILE__ ) . '/backpress/functions.wp-taxonomy.php';
require_once dirname( __FILE__ ) . '/backpress/functions.plugin-api.php';
require_once dirname( __FILE__ ) . '/backpress/loader.wp-object-cache.php';

depending on what you're doing, you'd definitely be able to leave out a bunch of them, probably everything from wp-taxonomy onwards (perhaps also formatting).

Keep an eye out here for the tutorial I'll post with more/better detail :)

Court - there are a variety of tools (TortoiseSVN is the first that comes to mind) that can help SVN become a part of your workflow on Windows in particular. Using some sort of version control (e.g. SVN) is critical to a project like this, where there are different people all over the world contributing and working on the code.

We may also offer downloadable ZIP/TAR.GZ files at some point, but right now we don't because the library is still maturing as a project of its own, so it doesn't make too much sense (there are no specific version numbers or "releases" in the common sense).

We have some volunteers working on a Norwegian translation currently,
but if you'd like to help out, please email labs@intensedebate.com and
let us know!