purple-facebook

This release fixes these two recent issues:

• "Failed to get sync_sequence_id" (#449)
  • Facebook increased the version number requirement for a significant fraction of users (but not everyone, at least not yet)
• "Failed to read fixed header" (#410 for nss, #444 for gnutls)
  • NSS and GnuTLS, the two TLS/SSL libraries that libpurple supports, enabled TLS 1.3 support in recent versions...

This release fixes "Failed to read thrift" errors which some users may get on login (and probably all users in the next weeks)

It also contains a bunch of long overdue patches that were stuck in backporting hell (first from bitlbee-facebook, then from purple3 to purple2) and now can be free. This is also why the hash in the release name changed from c9b74a765767 to 9ff9acf9fa14 - the pr...

• Add content-type header to all requests, fixes http error 400
• Change error message when sync_sequence_id is missing, for clarity
• Bump orca version. Purely speculative, may not help with anything.

Windows users: get the latest build from the usual place: https://github.com/dequis/purple-facebook/wiki/Installing-on-Windows

Fixes groupchat join errors

• Send orca-formatted user agent for all HTTP requests too. Fixes "Failed to parse thread information" errors when joining channels.

This is in addition to the connection error fixes mentioned in the previous release that happened earlier today. Quoting from the previous release:

It fixes connection errors after facebook discontinued support for old versions o...

This is now the minimum required version.

It fixes connection errors after facebook discontinued support for old versions of facebook messenger for android. While most of the protocol implementation was already above that version, there was a subtle change that broke fetching of sync_sequence_id, and the previously empty MQTT user agent string is now considered an old version too. See ticket #3...