DISQUS

Jennifer,

Your evaluation of Spaz is inaccurate. It does support uploading images, to a number of different services. You can either drag a photo onto the window, or click Spaz>>Upload Image.

http://skitch.com/funkatron/bi2ud/spaz-upload-i...

Feel free to contact us at spaz@funkatron.com or http://spaz.tenderapp.com if you have other questions.

Thanks for the review, Nick. I've already made a number of performance improvements since 0.4.2 came out, and I really hope to get support for Identi.ca in the next release as well.

The best way to request a feature or support something already requested is to visit our issue tracker. It's on GitHub, the same as our source code.

http://github.com/funkatron/spaz-webos/issues

I encourage you and your readers to participate in the development of Spaz in any way they can, including filing issues, testing, supporting other users, and contributing code. The Spaz project has already developed a rich user community on the desktop, and I really want to see that happen on webOS as well.

John,

We have a couple good projects going that way already, with Laconica (http://laconi.ca/trac/) and the OpenMicroBlogging protocol (http://openmicroblogger.org/). I can't comment on their current extensibility, but folks who are motivated will surely be appreciated for their interest.

This is why, somewhat along these lines, I created Spaz two years ago. Of course, it actually predates Tweetdeck, Nambu, and even Twhirl (err, Seesmic Desktop, sorry). But is has from day 1 been fully open-source under a New BSD-style license. Spaz enjoys some popularity, although it lacks the VC funding that helps drive the promotion engine of other clients. There is a small but dedicated team of folks who help out with development and support, and people are *always* welcome to check out the source and submit patches for new features. Most don't, but a few do, and it's how we've gotten support for numerous url shortening and image hosting services.

More recently I've started the SpazCore project to provide a base set of libraries that work across browser engine platforms like AIR, Titanium, and webOS. We have the same license and policies for submission as the original Spaz codebase. SpazCore will serve as the basis for a full rewrite of Spaz (the current codebase is a bit icky) that will start after version 0.8.0 comes out this week.

While it may not fit all of your needs -- I'd argue that nothing is going to do *everything* you want, unless you write it yourself -- a project like you describe exists, and has for a while. You can learn more about it at http://funkatron.com/spaz

I posted on Twitter that I bought my fiancee a ring. Does that make it appropriate for my clients of employer to question my priorities publicly? If this was really a concern, a private inquiry would have been far more appropriate.

This is beyond tacky. You owe Alex an apology.

Thanks for the note. Keep in mind that you're talking about the current state of our *test releases,* which are not designed for general consumption and will certainly contain bugs and rough edges (well, more than the "public" releases). We think having a transparent development process that involves the community in testing is important, but these test release should *not* be mistaken for ones ready for public consumption. There is *no way* I would ask average users to hack prefs files to get these things working, for example.

If they're not lying scumbags, they're already one-up on SG.