Hey guys, I want take this time to note that I'm bout to take several tangents of my own thread, the relevance here is it what the pandaphone will become once I start working on it agian. I'm taking a break from ripping apart code all night to write this. Kind of a breather.
but anyway to the good stuff.. I got some updates on my understanding of google voice and technically speaking where and how this is going to go. Before I mentioned google voice will probally use SIP, this is incorrect they use a technology called XMPP (Extensible Messaging and Presence Protocol) which is similar to SIP but more robust. you've all heard of jabbertalk the protocol google talk uses. This is what google's whole communication structure is built off of. Extremely expandable both technically and infrastructure speaking, it's an open source protocol, like I was sure they were going to use and they've been using it for quite some time. Take skype's concept (mesh p2p) with no mothership, and add to it some ftp, smtp, voip and other protocols. This is where google wave comes in. The grandfather, of end alls, of all in one communication applications. But don't worry about that right now. That story is for another time. The next big jump is google talk mixing it up with google voice. Google engineers have confirmed this (although almost little to no knowledge of it exists) I found this tucked away in a blog http://googlesystem.blogspot.com/2007/05/phone-calls-in-google-talk.html Progressively speaking this is the next big step is to integrate the two technologies. This will mean free/cheap calls via any google talk interface to anyone anywhere. And if widely addopted, will be the first step to destroy the grip mobile communication companies have on us right now. There are APIs exist now to make your own google talk application and with this new functionality comming, we are on the door step of free voip to landline/mobile communication. So this specifically and technically is going to be how it's done.
Speaking a bit on destroying the grip mobile comms companies have on us right now. Remember the fuss google stirred with apple and att over the rejection of their google voice app? Well, I was reading up on this. The plot thickens my friends... this wasn't just about att/apple stopping google from giving it's users free sms messaging. Nono... this was ALSO about exclusiveness between mobile carriers and phone manufacturers over hot commodity phones. The little smack down us gov did on Microsoft a while back about being too successful and making a monopoly of the computer industry? This runs down the same line as that. Is is quazi unconstitutional? yes, does it go against the free market enterprise mentality? yes, but is it again going to loosen the hold mobile carriers have on us? um yup. I can say one thing about our government, they are quick to jump in the big guy's ass when they start taking advantage of the little guys. Now about those gas companies....
Interesting thing that has come up recently, android's official google voice application talks directly to google voice to place calls, no "man in the middle" from the user's perspective. Although thats exactly what is happening, but user perception is everything. I would really really like to get my hands on the API or source code of this little app to find out how it's done. Google still hasn't released all their apis yet for google voice. This would really help me in what I'm working on with the pre. I'm ripping apart the palm's unencrypted source code now for it's dialer app to see how palm does it, with an end result to make my own dual dialer (google + sprint) The more I dig, the more promising it looks. Copying and pasting the code would be copywrite infringement, but using their format and borrowing a line of code here and there is not. It's mainly just well documented commands, and palm seems to have a sence of hummor in their remarks "this whole section is rubbish, but it will do for now" I still would like to see how google did theirs officially though, I'm learning how it can be done via talking over http, it's rubbish but it will work for now
I guess we're all playing the waiting game at this point, I'm beefing up on my java coding skills in the meantime. I hear it's a dying language, but for right now it's good for the stuff i'm working on for the pre. First open phone I ever owned. In both sences of the word haha. If you guys don't got one, I'd strongly recommend the pre or android, you don't have to be a rocket scientist to jump into either one of those bad boys and really open them up. And me being a very novice programmer have found a nice home with their mojo sdk and aptana studio. The homebrew community on both platforms have strong linux ties too so it's generally a pretty friendly environment as long as you don't approach the community like a total idiot. noob=yes idiot=no
back to the pandaphone, my findings with my pre I'll do my best to bring back with me over here when this guy gets released in the next couple months hopefully. I'll try to keep you guys updated on new findings and the progression of google voice as a voip solution. I'd also like to hear whatever progression is being made on the hardware modifications side of the house for 3g/cdma radios. Any more ideas? Making any progress? *cheers*