For the record, I don't give a shit.

If anyone is interested in helping out, there is the talklock project. I started it a little over a year ago to do voice encryption for Blackberries, and as many mobile Java devices as possible.

Most of the pieces are there now, but it is not complete. There are screenshots available and it is GPL.

It can record audio and play audio, and send and receive audio from a web server. I even hacked together a shell script on my Mac to listen to the audio so I could test the code with only one phone :)

I agree, this technology is too important to wait for, we should develop it ourselves! Then it can't be taken away from us.

And yet, you come across as nerdier than the nerds. Comic book guy from the Simpsons.

I don't care for martial arts, but I do enjoy marital arts.

Also I have guns. They work well for slow-moving lazy bastards like me, without all that exercise nonsense involved with martial arts.

So while you are all jerking yourselves off, I actually "thought" when reading this review. Two thoughts boiled to the top.
First, the reviewer needs to get over the randomly ordered tip thing. They did it on purpose, it's random. Next.
Second, when you rm a file in Ubuntu now, it goes to the trash can? Is that right? Because if that's true, that is like the horror, the horror. Making Linux do brain-dead shit like that will kill it.
Third, I'm not sure how useful the part of the book about gconf would be. In reality, the desktop folks need to get over themselves. NetworkManager is a broken piece of shit, network connectivity has nothing to do with runlevel 5. A box is a box, you can do everything you need to do without GNOME or KDE. Personally, I'm glad Red Hat still has linuxconf.
Now go away, or I shall taunt you a second time.

Maybe they won't get to build it, but it will be totally entertwined with Telstra's existing network. Lots of last mile hops will be Telstra, and many of the backbone fibers will be leased from Telstra, or bought from them.

We did the same thing in Ohio, and AT&T wasn't allowed to build it, but we are totally intertwined with them anyway. We don't even peer with them, it's all layer 1 or 2 service.

Yeah, the Blackberry does J2ME. Of course there are the usual platform oddities. I have been writing a voice encryption app for J2ME and testing on the Blackberry. The RIM SDK might make things easier to run on Blackberrys (Blackberries?) but sticking with the J2ME libraries makes for better compatibility.

I am using the Netbeans + Mobility Pack IDE. Totally free, and I can publish Over The Air using a webserver. No wierd restrictions like the RIM stuff.