This incident discredits the FSF's legitimate and usually very good flagging of internet misdeeds.
The FSF started out by saying Google was blocking some federation between domains [and the sky is falling down]. The implication being that because they are big there must be some malicious intent.
Google had mentioned the problem on the XMPP operators lists and, their messaging team are a pleasure to work with (we send a lot of buddycloud messages to Gtalk users over their XMPP network). This FSF post created a shitstorm for no reason.
Of course we should aim for full federation. But let's look at Google's position: When (I'm guessing here) 1% of your XMPP traffic is federated, it's in Google's interest to look after their existing users and protect them from a bunch of spam than to federate with smaller domains. It's a no brainier - not an evil plan.
PS: It's called XMPP. Jabber is a trademark owned by Cisco.
From the original article that you mischaracterise:
"According to a public mailing list thread, Google is doing this on purpose, to handle a spam problem. We sympathize; we spend a disappointing amount of energy combating similar problems on the services we provide for the free software community. But the solution can't be something that breaks legitimate communication channels, and especially not in a way that enhances Google's disproportionate control of the network."
I remember when Google used to have an in-browser GChat app connected directly to XMPP through JavaScript or another frontend language. I still have my hopes that they will release an open source framework to embed a similar IM chat into a website layout.
That does look awesome. I like how it can also work on a custom XMPP server, so that you could have a type of internal buddy list or chat system. Great link! I will keep myself updated on your client and maybe I can use it on an upcoming project.
Earlier this week it only took me less than a business day to add a custom chat window to my site using Firebase. You might consider checking that out.
It was a global chat, not one with friend lists and private messaging, but the API is pretty easy so I'm sure you could do what you want with a little work.
Most live chat products also allow you to integrate with your GMail account easily and give you a small js to add to your website. We do at http://gaglers.com
not that they have any obligation to do so, but: in the absence of some commitment to this remaining available, I'd be hesitant to build reliance on it.
The FSF started out by saying Google was blocking some federation between domains [and the sky is falling down]. The implication being that because they are big there must be some malicious intent. Google had mentioned the problem on the XMPP operators lists and, their messaging team are a pleasure to work with (we send a lot of buddycloud messages to Gtalk users over their XMPP network). This FSF post created a shitstorm for no reason.
Of course we should aim for full federation. But let's look at Google's position: When (I'm guessing here) 1% of your XMPP traffic is federated, it's in Google's interest to look after their existing users and protect them from a bunch of spam than to federate with smaller domains. It's a no brainier - not an evil plan.
PS: It's called XMPP. Jabber is a trademark owned by Cisco.