21–30 of 41 posts
I'm implementing a Google Talk jabber client and I'm curious whether or not it allows sending messages as links. It doesn't seem to automatically parse them into clickable ones. Not much luck on the XML alteration....
What I've really wanted to figure out for awhile now is how XMPP might work as a replacement for email. Even as new IMAP or Gmail clients appear on the market seemingly every few months now, I can't shake the idea that it's time for a new protocol, alas an impossibly tall order. Yet XMPP seems like the closest thing to an existing, modern standard to build upon. Am I tilting at windmills, or is there any validity to…
What, exactly, do you want to do with it, and how does it replace email? (Genuinely curious - I see suggestions for replacing email on a regular basis, but rarely ones that are deeply thought out.)
One of big potential benefits I see is the XMPP concept of contact requests. Simply separating new senders from existing senders at an architectural level seems like a great start for an email replacement, both in terms of user experience ("who I know" is fundamentally separate from "who I don't know" regardless of the client), and in network utilization (spam is only ever as long as a request header instead of an entire message).
I'm implementing a Google Talk jabber client and I'm curious whether or not it allows sending messages as links. It doesn't seem to automatically parse them into clickable ones. Not much luck on the XML alteration....
Earlier quoted context omitted.
Seemly Whatsapp is, and what they are doing is genius, I would pay even more for the service than what they are charging (99 cents year). At first I did not understood, what it had in special, until I figured that it was the fact that it used your phone contact list, thus taking out the boring task of managing that, and making adding people to your list easy as finding someone phone number. Yet, I would not use it as…
Why would you pay for such service if one can get a normal secure and federated XMPP service for free? Whatsapp offers no advantages of XMPP (no interoperability and no federation) and only adds problems (flawed security). Paying money for such kind of disservice is simply strange.
I'm implementing a Google Talk jabber client and I'm curious whether or not it allows sending messages as links. It doesn't seem to automatically parse them into clickable ones. Not much luck on the XML alteration....
I don't have a problem with it, although it would've been nice if the title had made it clear that it was a primer.
Earlier quoted context omitted.
What, exactly, do you want to do with it, and how does it replace email? (Genuinely curious - I see suggestions for replacing email on a regular basis, but rarely ones that are deeply thought out.)
There are some fairly general reasons, like XMPP being a much newer, extensible (it's in the name!), yet mature messaging protocol with a big community, but there are also some specific ones. One of big potential benefits I see is the XMPP concept of contact requests. Simply separating new senders from existing senders at an architectural level seems like a great start for an email replacement, both in terms of user…
Because in the end, and despite all its kludges, e-mail doesn't need replacement. Its biggest problem remains spam, and even that is under control by all the major providers.
Is it me or doest this read like it's half an article? I got through to the end expecting it to be about something that you can do with XMPP and Jabber, rather than a rather basic primer on Jabber and XMPP themselves. I don't have a problem with it, although it would've been nice if the title had made it clear that it was a primer.
The main article is about creating a Google Talk bot with Node.js so if you want to create something with XMPP then please have a read through of that article: http://news.ycombinator.com/item?id=5175913
Also when I submitted this article to Hacker News I entitled it "A short history of XMPP and Jabber" so I am not sure how or when it got renamed.
Earlier quoted context omitted.
Why would you pay for such service if one can get a normal secure and federated XMPP service for free? Whatsapp offers no advantages of XMPP (no interoperability and no federation) and only adds problems (flawed security). Paying money for such kind of disservice is simply strange.
Adoption. That is one of the main reasons why most people won't mind paying for whatsapp ; almost everyone on their contacts list already uses the app and frankly most people don't know or care much about whatsapp's security measures.
I've long been fascinated with XMPP, because it is so flexible. Rather than focusing solely on a specific purpose (like IM), Junction exposes a middleware framework similar to Express so that you can develop applications on top of XMPP.
I've been happy with the approach, and I'd be curious to get feedback from other developers who've had similar thoughts regarding XMPP.