It feels like people who want a decentralized future.where everyone is centralized into a small number of servers who can run a dozen or so Docker containers and such. I don't want to sound too down on Matrix, but it feels a bit off to me. Yes, running on your machine doesn't mean everything is safe, but there's some level of inspection you can do of what is going on.
#Adium gchat software#
When software is just run on a server that the public doesn't have access to, who knows what is happening. Even if you don't trust the maintainer who is compiling, you still have a good idea that they're not sending all your messages to them because someone is more likely to notice the binary doing that (via tools like Wireshark).
#Adium gchat code#
If apps are open source, one can see the source code and even compile one's self. One can use tools like Wireshark to confirm where data is going. Yes, downloaded apps can be malware, but it's a lot more easily discoverable.
I'm not going to run my own Matrix server so that requires me to trust a Matrix server with access to my Facebook. It seems like a puppeted bridge requires me to send the messages to the Matrix server who then has a login to my FB Messenger to read/write messages there. I haven't used it so some of this may be wrong and I'm happy to accept corrections. Portal rooms, plumbed rooms, bridgebot bridges, Bot-API bridges, puppeted bridges, double-puppeted bridges, server-to-server briding, and sidecar bridges. Maybe I'll look into it more, but it feels messy and complicated at first glance. It certainly isn't impossible to adapt this to a design like libpurple/Adium/etc, but it's an awkward fit and is likely to fail to support features which don't fit into that model, like chat messages being edited or deleted by the other party in the conversation. Newer IM networks like Telegram are usually designed from a mobile-first perspective - the Telegram client protocol is designed around the concept that the server has a definitive view of history across all chats, and the client synchronizes portions of that history to local storage to display it.
#Adium gchat Offline#
There was no real support for server-side message history, multiple clients, mobile clients, or offline messaging, so third-party clients often just implemented their own local history instead. "Old-school" IM networks like AIM were simple to work with from a client perspective - you connect to the network, you send and receive messages, and that's it. Next, point the server to "," configure the port to 5222 and un-check the box for "Use SSL."Īfter it's all said and done, you should be able to communicate with your Facebook friends using iChat without being logged in to Facebook with a browser.Modern IM networks aren't a great fit for libpurple because they fundamentally work differently.
#Adium gchat password#
The username to use is your Facebook username (which you can find on the Account Settings page) and the password is the same as your Facebook login password.
First, create a new generic Jabber account pointed at Facebook's Jabber server. Many networks (such as Google Chat) rely on Jabber, and for this reason chat clients like iChat and Adium allow for the setup of a generic Jabber account to facilitate the widespread use of Jabber. Of course, the free Adium client has directly supported Facebook chat since version 1.3 (released in 2008), but this step opens up a much wider range of clients for the service.įacebook's chat service is powered by the Jabber/XMPP open source chat protocol. Last week, the fine Facebook folk let us know (via the Facebook Help Center) that you can now sign in to Facebook's chat service using iChat.
0 kommentar(er)
