[forteller]

> This is a bad idea because a web browser should not become a chat or client as well.

Well, the browser already is a chat client for millions of people. It's called Facebook. So since the browser already is the only chat client tons of people use, why not make it a client for a Free/Open chat system instead of Facebooks chat system, that they control, censor, give access to to NSA, etc.

> Remove their like-buttons from your pages!

I agree we should do this. But that won't help people keep in contact with their friends. And so it won't change the thing I'm focusing on here.

[sigzero]

> Well, the browser already is a chat client for millions of people. It's called Facebook.

"Is a" and "has a" are worlds apart.

[antocv]

If your goal is to have a free and open uncontrolled, uncensored chat-system that is NSA kinda proof then lets do that, Im all for it.

I just dont think XMPP fulfills the uncontrolled and uncensored and surveillence resistent parts. We need to look at web of trust, bitmessage and such instead, those are more fun problems than "to spite facebook".

But sure, any solution will benefit greatly if its bundled with the browser since that appears to be the only program most users actually use on their computing devices. Imagine if Tor and a tor-relay or even tor-exit-node came preconfigured with every Firefox and turned on by default. That would be fun.

[forteller]

You might very well be right. Using XMPP is not important to me. The important thing is the goal of moving as many people as possible over from closed to Free/Open systems.

[emn13]

Free would be nice - but it's open that's the key (and if you have open, somebody will make a free version anyhow)

[forteller]

Free as in Freedom :)

[shmerl]

> Well, the browser already is a chat client for millions of people.

I'd rephrase it. Browser is turned into a virtual operating system for millions of people already. While it can be useful, I don't really like when that trend is pushed to the extreme and everyone rushes to run everything through the browser even without clear benefits. The point of that? I always prefer standalone chat clients (as well as e-mail clients and etc.). If some chat service can't interoperate with standalone clients, it's garbage.

Facebook can by the way, since they do use XMPP. Their problem is unwillingness to support federation. They are too selfish. So I never use their service (nor do I use their social network anyway).

[forteller]

You have to remember that just by being a person who read Hacker News you are not a regular person. I really don't mean to be harsh, but it doesn't much matter what you prefer or that you find this trend of running things in the browser problematic. What matters is what normal people do. People who don't even know what a "client" in computer lingo means.

Those are the majority, and if we want them to use Free and Open systems (which is my whole point here), then we have to create those systems in a way normal people will start switching from the closed systems and over to the open ones. And that is only going to happen if the open systems are easier to use and more accessible than the closed ones.

I am aware of the fact that Facebook uses XMPP (I mention it in the post). Still, extremely few people use it through a client. They use it through fb.com.

[shmerl]

> Those are the majority, and if we want them to use Free and Open systems (which is my whole point here), then we have to create those systems in a way normal people will start switching from the closed systems

It's trickier than that. There are many open and federated XMPP services around, including those with web clients / interfaces available. Options are around. It's the sabotage of federation by "big" players which is a problem (or sabotage of interoperable protocols altogether).