I’ve moved to Chandler 1.0-rc1. Not a lot different, still looking good. My linux upgrade on gentoo AMD64 (using the Ubuntu “compressed image” build on the linux download page, works great) went without a hitch. On Windows, the 0.7.7 release barfed when it ran low on memory. I started getting the dreaded “Another Chandler is already running” message on startup. Upgrading to 1.0-rc1 didn’t help. The error message is bogus, here‘s my report explaining the problem. I deleted my repository in the [Documents and Settings\(user)\Application Data\Open Source Applications Foundation\Chandler] folder, recreated it by restoring from the most recent backup, and resynced to the Hub.

If you need to get through a proxy, you still need the http workaround. Here it is in a nutshell.

A proxy can be specified in File->Configure HTTP Proxy. After discussion on irc with gbaillie and JeffreyH, I found that chandler uses https by default when syncing with a “Chandler Hub Sharing” account. This does not appear to use the proxy. The workaround is to set up a “Chandler Server Sharing” account, and specify the hub settings manually, using http instead of https:

  Server: [ hub.chandlerproject.org ]
  Path:   [ /                       ]
  Port:   [ 80                      ]
  [ ] Use SSL (unchecked)

If you use a valid hub account username/password and press the Test… button, it should succeed.

Now get yourself organized!

OK, I’m not sure of the protocol on this, but since it’s now released into wild I guess I can brag a little. I’ve done a bit of work on the side for Intense Debate and the first fruits are showing up:

  • the announcement of the beta release of my plugins
  • the Firefox addons showing a couple dozen downloads and 5 5-star reviews (as of today)

I have newer versions and I’m working on a bloglines beta addon now. Fun fun!

UPDATE: Looks like the beta release of the first two addons is official now.

I’ve upgraded this blog to WordPress 2.6, and tried to tidy up a bit. My favorite trick for today came from here, where the author discusses a “geek switch” to turn off his more technical material. I have a Chatter category that’s in the same boat – sometimes I want to see it, sometimes I don’t. And I don’t want first-time visitors to have to see it.

I modified the original author’s toggle approach a bit, widgetized, with a touch more Javascript and updated for WordPress 2.6. You can see the toggle in the sidebar to the right, try clicking on it. Pretty fun eh?

See my Toggle Category wiki article for the gory details on setting this baby up. I <3 WordPress.

Lots of people have been doing this style of web mashup for a long time. Things are now stable enough, even in FF3, that you can jump in and get ramped up super-fast.

  • Install Firefox, along with Greasemonkey and Firebug addons.
  • Grab a starter script from here, save it as [myscript].user.js, and open it in Firefox (Ctrl-O) to install it.
  • Bang on it! Change the script to do your bidding…
    • change the target website
    • browse around for DOM objects to mangle with Firebug’s Inspect
    • you can do cross-site xmlhttprequests, whoop!
    • reload by simply reopening the file and refreshing the page
  • Compile the script into a FF addon in one easy step, here.

Bring all your honed software development skillz, or things will get messy fast. Get mashing!

Also check out chickenfoot for another way to go.

Here are mine, at the moment. These seem to be 3.0-friendly. I’ll update this as more plugins become available/improved.

Everybody loves Tab Mix Plus (including me), but… it’s really just a theft-and-scrub of many other extensions, and the authors haven’t been able to pull it all together for FF3 yet. At least not officially, I’m using this prerelease and it seems OK so far:

And for developing, these speak for themselves. Ready to go for FF3…