Slashdot Mirror
Google Talk Claims Openness, Lacks S2S Support
rm writes "This LiveJournal entry by Nugget quite well sums up the disappointment in Google Talk among many Jabber users, caused by the service's complete lack of XMPP server-to-server communication support: '...Google has uncharacteristically missed the real strength of the Jabber design. Despite all their self-congratulation about open communications they've only embraced the smaller, less important aspect of the Jabber openness.'"
Select Quotes FTA...
When do we get to the "rant" part? This is boring.
It was a nice trip down memory lane, so don't knock yourself about it. I have fond memories of ICQ with buddies on Captured.com, planetquake.com and late nite mapping sessions with the UH-OH echoing into my brain. And then there was that dreaded song -- you know what I'm talking about. ICQ invaded MTV. Ack -- **flips channel**.
What makes Jabber truly great is that it is a decentralized system.
You can't really make any money in a decentralized system, which proves Google is still looking to captivate us because they have always been quite central. They may have a bottom line to think about, yet we are not in business as free-thinking human beings to serve the needs of one company. What we tend to want always comes first, we are all very selfish -- centralized and independant. We do not want to give control to anyone. We want to save it for ourselves, because we have learned from our mistakes and we know what happens when you trust something far bigger than you.
We want to be free, open, decentralized.
But at Google, it's all about centralization. That's their way. The information they have access to at any given moment is insane, and I think it's the primary reason they believe so strongly in centralization, so that they can collect more information.
It's time to embrace a truly workable and distributed topology that will move us past these ridiculous incompatibilities.
I concur.
The dangers of knowledge trigger emotional distress in human beings.
That is, after all, the point of open source, is it not?
Surely it's too early to be slating what they're doing with this technology. Don't you think they might be taking an incremental approach?
Then again, I *do* sound like another Google apologist, don't I?
Remember this is still in a very early beta stage. On the developer page, they claim that they're moving toward interoperability with other networks and fully documenting the custom VOIP protocol they use.
They encourage people to comment in the Google
Talk Interoperability Google Group. It seems like they're trying to determine how to balance openness with security, privacy concerns (i.e., avoiding spam). I frankly don't know enough about Jabber, etc. to know if this is BS or not, but it sounds reasonable enough to me.
Nonsense. When it comes to editorials, there's little difference between an "official" shill/idiot like Dvorak, and a valid opinion from a blogger. In fact, the blogger may tend to make more sense because he's not serving other masters. (Note: This isn't ALWAYS true.) In other words, the editorial should be judged on its content, not necessarily who wrote it.
The problem is that blogging has a stigma attached to it. It's seen as a method through which people can voluntarily make their private lives public, making it the oddest form of online voyuerism available. However, the concept of publishing articles on a regular basis is not new, and there is no real division made between "blogging" and "writing regular articles". Thus it can be difficult to tell if a "blog" is actually something that can be safely ignored as a poor form of entertainment, or a reasonable attempt at serious writing.
Javascript + Nintendo DSi = DSiCade
It has been out for a week or so, and we should cut them some slack as they work out the kinks and add new features. GMail lacked a number of things I wanted it to have when it first came out, but Google seems to be slowly adding them with time. Google seems too happy to call things beta for just about forever, but at this stage I think we all should consider it as a real beta and just wait and see
What do you know I wrote a novel
If only S2S was the only Jabber feature that Google "left out" when rolling out GTalk... but they also forgot to activate all these standard jabber features
"The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
I'm getting freaking tired of people trashing google everytime they put out a beta!
Yes..it might not be the greatest thing since sliced bread but the POINT of releasing test software is for TESTING and feedback!
It's OK to trash the BETA, but don't mistake that by saying "Well....it sucks gonads. Google failed...I'll never use it again"
I'm pretty sure that if you actually read the google talk FAQ that they mention linking up with other networks in the future but they haven't implemented it yet. But why should we let facts get in the way of a good rant?
Something I've noticed with the whole Google talk thing is that even the people I know who are hardcore Linux geeks say "How is this better than AIM?"
I must say this is somewhat surprising... one of the tenets of the greatness of Linux is the openness and freedom to innovate - why does nobody care about the fact that IM has had almost no innovations lately?
Google promoting Jabber could be a great thing, assuming they will enable the server to server support. IM could become more of an open service where people actually CAN innovate, rather than a closed protocol run on some corporation's servers.
So, even if you are afraid of Google becoming powerful, or if you think that IM innovation is dead, I'm willing to carry at least some hope that getting Jabber into wider use could be a big deal in evolving how IM works. Just a thought...
I thought it was a Google product family
Gmail Beta
Gmaps Beta
Gtalk Beta
As I said, it isn't always true that a blogger isn't serving other masters. However, I have a hard time believing that Google is one of them. Google doesn't demand any sort of articles out of a blogger. It's completely up to the blogger what he wants to write about. The most that Google might do to a technologist is cause him to "optimize" his language for adwords.
OTOH, someone might look at the "Top 100 Keyword List" and decide to create a blog on that. If he has something interesting to say about viagra or bankruptcy, then he may very well make money on it. Otherwise this is hardly a workable business plan.
At the end of the day though, you have to judge the article on content. A blogger *may* be better because he's not serving other masters, or he may not. If you judge on the content itself, it really doesn't matter in the end, does it?
Javascript + Nintendo DSi = DSiCade
Have you EVER used e-mail before? Same concept here. Read the article before you trash what you don't understand.
Imagine if google would open it's talk.google.com for server-to-server communication with other jabbers around.
..
Y! opens a jabber2yahoo bridge
MSN opens a jabber2msn bridge
AOL opens a jabber2aol bridge
..
Everybody would be happy, except for Y!, MSN and AOL.
Happend before, with Inbox size!
And they could keep their voice algorithms for their use, a hell with them! for a couple of years, until it becomes a standard feature, I can agree with that.
Then they should open this too:D
gtkaml.org
Exactly. It's all the same steaming pile of self-important crap.
I used to use e-mail constantly, but the signal to noise ratio is like 1:300 these days.
Same concept here.
"The problem is that blogging has a stigma attached to it."
No, I think the problem is that blogging deserves the stigma attached to it.
Without the ability to identify credible sources (yes, I know it is sometimes possible with blogs) a piece of information is essentially worthless.
Everyone come down out of their ivory towers and quit trumpeting how great they are for pointing out yet another reason why Google ain't the bees knees. Climb down out of your ivory towers and take a nice dose of reality.
Incremental improvements are a good thing - Starting w/ the absolute minimum feature set and building on it, all along making sure it works as advertised is a sound strategy. This approach allows you to continuously improve the software, and focus on addressing the issues that arise with the current feature set in a manageable way instead of having to address a mass of problems from all of the half-assed features you had to squeeze in because you had to have all of the bells, whistles, and even legit features. A frequent improvement/release cycle is a common practice for open source software products and Google is adopting a similar approach for its service.
You can't simulate this kind of load accurately - Sure you can run computer models of how the traffic load will behave and how the infrastructure will handle it, but you really don't know how it's going to work until you start putting some real user load on the system. By limiting the feature set, and in particular limiting inter-server communications you naturally limit the amount of load on the system. The users aren't going to switch completely from their current service to GTalk all in one day... so as traffic builds they can adjust the service settings, tweak the servers, do whatever to make sure they can continue to provide a quality service. And back to point #1... once you have a good understanding of the traffic patterns and capacity you can begin introducing new features that may change those patterns in a controlled way.
You can't predict how people will abuse the system - By limiting the feature set Google can better ensure that the system is not seriously abused by individuals who would want to use the system in a way that would annoy/harm the general user population or impact system performance. Connecting to other servers is a risky proposition that deserves careful attention and control to ensure that it works correctly. If Google make a misstep here and allows spammers to spam all of their users, and virii to spread across their system, and poorly managed Jabber servers to cause their messages to not reach their intended destinations you'll have a system that most people wouldn't want to trouble themselves with using. Google can start by controlling the environment while providing a base set of services... and then expand in a way that they can monitor and control to ensure that service is not impacted.
Get real feedback from real users - Instead of dreaming up a hundred things users probably want and squabbling over them internally, why not just release a base product that people will use and get direct feedback from them on what they want. This is what Google has setup... now they can ask their users do you want to jabber w/ other non-GTalk servers? Do you want more emoticons? What about real voice call capabilities? What about being able to search your conversations? What about... The point is let the users help direct the next round of development instead of spending a lot of time developing features for people who don't use the product.
Protect the service the customers want - The underlying principle behind all of this is that you have customers who want a service. The way to attract and keep those customers is by offering them a service they want and that works. Google has started by offering GTalk to a group of users. They'll hone the system, make sure it works, and if it meets their objectives and draws in customers they'll continue to expand on it's feature set in a way that keeps their customers from moving to some other service and continues to attract other customers... all the while being very careful not to make the service unstable or give something to their customers only to have to take it away (premature release of poorly test
No, with IM you only receive messages from people you have authorised (your friends). And if you're getting a SNR or 300:1 with them, it's time to find some new friends.
Malike Bamiyi wanted my assistance.