131–140 of 143 posts
Earlier quoted context omitted.
For now.
Despite the clear warning signs, I am willing to put money on people whinging in a year or two when they shut down those servers, just like everyone got all upset about Reader.
Considering that XMPP federation has been turned off for some time now, this really only hurts users using XMPP clients. I was wondering why my friends with non-Google Jabber IDs were never showing up as online, and one day figured out federation was turned off. This is as if a few months ago your email provider silently discarded emails to and from other domains, and just today abandoned SMTP and IMAP. The true fail…
Federation was turned off temporarily to fix an exploit then turned back on. I guess it's moot now.
1) Subscription requests to/from other domains were blocked.
2) Only for a short period (about a month, tops).
Earlier quoted context omitted.
It's definitely not the lack of features, since XMPP is extendable. I've heard that the protocol is quite chatty and would cause power drain on phones. That could probably be solved with a binary serialization alternative to XML, though.
While the use of XML in the protocol might be considered verbose, stream-level compression from TLS quite makes up for that. With many contacts, the number of presence stanzas might indeed drain the battery because the antenna will be 'up' quite a bit. However, the XMPP community has been active in quantifying such issues and providing solutions. The beginning of a document with background information is available as…
Facebook also have a private extension, as I understand things.
I should actually submit that extension - I wrote it up as a XEP ages back, but various things have held it up.
1) Competitors use Google's APIs based on open standards for their own advantage.
2) Google gets annoyed.
3) Google stops supporting open standards.
Well, that's my honeymoon with Google over.
It seems a naive mistake to have assume an enlarging Google would stay true to their roots.
It's time for those roots to move. Onwards and upwards.
So, 1) Competitors use Google's APIs based on open standards for their own advantage. 2) Google gets annoyed. 3) Google stops supporting open standards. Well, that's my honeymoon with Google over. It seems a naive mistake to have assume an enlarging Google would stay true to their roots. It's time for those roots to move. Onwards and upwards.
It turns out Open Source's weird uncle was right again.
Earlier quoted context omitted.
Personally I'd love to see a community driven extension to XMPP, with its corresponding RFC, which would allow feature parity with Google's proprietary crap while keeping interoperability and federation, so people could give Google the finger on this one.
I've long dreamed of a resurgence in the open source community, attacking big media much as the community attacked Microsoft in the late 1990s. It's depressing that the PR machine has so thoroughly succeeded that most of those who still call themselves "geeks" now consider building throwaway hacks on big media services cooler and more meaningful than coordinated efforts to replace the services themselves (in the name…
Priv.ly has an interesting approach to this somewhat analogous to the above: http://www.kickstarter.com/projects/229630898/protect-your-c...
Tent is a protocol for distributed social networking that I'm very optimistic about. You can message me at https://elimisteve.tent.is (sign up at tent.is).
Earlier quoted context omitted.
So, what do you propose as a realistic alternative?
http://www.jabber.org/ maybe? Or run your own xmpp service, if you are a business/company. I personally use prosody. Works great.
Earlier quoted context omitted.
Hangouts supports xmpp clients (but not federation), so it's similar to facebook afaik.
No, if you have a client connecting to Google's XMPP servers, your messages will not show up if the other user is only logged in on Hangouts. Hangouts ALSO can't send messages to an XMPP only user (even if Google is hosting the talk servers, as is the case for my Google Apps domains).
Earlier quoted context omitted.
As a user, I am upset that it is getting harder to communicate with people. Everyone has their own non-interoperable (but cross platform!) protocols/networks/gardens now. * blackberry bbm * apple imessage * google hangouts * skype * whatsapp, etc. As a user, am I supposed to have an account with one of each of these things? Have nine different apps open all the time? This is as bad as icq/messenger/aim/etc was back i…
It's very simple: no XMPP? Then I'm not IM'ing with you. No SMTP? Then I'm not emailing with you. I might be the exception, but I don't care. I encourage others to do the same, and don't support in any way, shape, or form companies that keep doing these things. Someone comes to you with a problem caused by this BS (or just a problem with, say, the offender's platform in general), refuse to support them. Tell them to…