--- ---

Verbatim Alpha Release

Last week I connected Verbatim to the addons.mozilla.org SVN repository and with great help from #verbatim on IRC the blocker bugs have been ironed out. Special thanks to Rubén Martín (Nukeador) for making the maiden commit. The server is a bit more unstable than I'd like[1] but it's usable. If you'd like to give it a shot to localize the latest AMO changes follow these steps: Log in with your LDAP</a> account (no need to register separately)</li> Click "change options" and choose "addons.mozilla.org" and your language Join #verbatim on IRC and let me know you registered and I'll make you an admin for the locale. After that other options will appear in the interface. </ol> One side note: To update the .po file from SVN or commit your changes to SVN you need to click "Show Editing Functions" when viewing the LC_MESSAGES folder. I'm coming up with a plan to make both the registration process simpler and the updating/commiting more intuitive but for now that's what we've got. If you'd prefer to keep updating the way you're used to feel free; this is an alpha version and I'm primarily seeking feedback (and hopefully offering some convenience). If you're interested in learning more about Verbatim there is information on the wiki including the current time line in the meeting notepad section. [1] Due to the way jToolkit works I have to restart the server every time I push a code update which breaks everyone's sessions.

Committing to SVN securely from a web application

Verbatim is the second project I've been the lead on recently where the requirements included people committing to SVN as themselves via the application. At first glance this means storing the authentication tokens of the user in plain text since we'll need to pass them along to SVN whenever they commit. I wasn't happy with that solution so after a bit of thinking we came up with an idea that leaves everything encrypted and doesn't cache any credentials. It involved minimal code in Verbatim and minor work on the SVN server.

Planning your API is important

I'm upgrading some code I wrote to talk to a new version of the Citrix NetScaler's API. The NetScaler's manuals (that's right, plural) weigh in at a combined 1114 pages so documentation isn't a problem and their implementation is a breeze using WSDL over SOAP. However, some of the core changes left me scratching my head. Case in point:

ThreadBubble 0.8 Released

A new version of ThreadBubble is available. Changes include:

Any Firefox fans in Morocco?

I'll be in Morocco at the end of next week and noticed there wasn't a single Mozilla Party in the country! There were over 36,000 download pledges though, so there must be Firefox supporters somewhere. :)