And if a contributor were to step forward and add pump.io support, that would be all the more welcome. If you want us to add pump.io support, we invite you to upvote our ticket #16380. Our statistics indicate only a handful of people used this feature, and considering StatusNet is deprecated in favor of pump.io we decided to not put any effort in adding StatusNet support to STTwitter. Sadly, dropping support for version 1.0 of that API also caused us to lose support for StatusNet. You will also notice some extra features like better support for displaying retweets and expanding t.co links. While this means the core of Adium’s Twitter support has been completely rewritten, transition should be automatic and quick. Thanks to Frank Dowsett we are now using STTwitter, which supports version 1.1 of Twitter’s API. We are glad to report that the required changes to continue our Twitter support have been finished with the release of Adium 1.5.7.
Adium extras full#
You can find the full list of changes here.
Adium extras update#
Update via “Check For Updates” from the “Adium” menu or download 1.5.7 here. Changes include the update of Twitter support and the removal of StatusNet support. We are happy to announce the release of Adium 1.5.7. You may need to turn Pidgin’s OTR plugin off and on again, but it should recognize your key, and all of your verified fingerprints should show up as well.You are currently browsing the archives for the release category. The protocol field needs to be changed from libpurple-jabber-gtalk (in the case of a GTalk account) to prpl-jabber.
In the case of Adium to Pidgin key transfer, which both use the standard libotrname field, which is an integer in the Adium config file, needs to be changed to the actual account name.
The tool’s not done, and so far only converts to their Gibberbot mobile IM client, but the README contains all the information you need. I was disappointed at how poorly documented these formats are, but fortunately the always impressive Guardian Project has gone through and documented each program’s file location and format in order to build a tool to convert files between different IM client formats. But that means you have to be extra careful about transferring these files from one computer to another: obviously, sending your key in a cleartext e-mail is not a good idea.Īnyway, harmonizing is just a matter of copying both files from one location to another, and then modifying the key slightly to match the format that each program stores it in. purple folder, you’re already compromised. The threat model assumes that if an attacker has access to your Adium 2.0 or. It’s worth noting that neither application stores these keys encrypted. Pidgin, on GNU/Linux, stores the OTR private key and fingerprints in ~/.purple/otr.private_key ~/Library/Application Support/Adium 2.0/Users/Default/otr.fingerprints The first step is to make sure you’ve got Pidgin and Pidgin-OTR installed on one computer, and Adium on another.Īdium stores the OTR private key and the fingerprints in ~/Library/Application Support/Adium 2.0/Users/Default/otr.private_key I had some trouble, but got it eventually, so I wanted to document the process. I recently re-installed Ubuntu on my home computer, and wanted to move my office Mac’s Adium OTR key and collected fingerprints over to the new install.
0 kommentar(er)
