summaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* finalise changelog for 1.2.0-1 uploadHEADdebian/1.2.0-1archive/debian/1.2.0-1masterSean Whitton2019-01-24
|
* Commit Debian 3.0 (quilt) metadataSean Whitton2019-01-24
| | | | [dgit (8.3) quilt-fixup]
* changelogSean Whitton2019-01-24
|
* Merge tag 'v1.2.0'Sean Whitton2019-01-24
|\
| * Release 1.2.0 with login fixes and work chat supportdequis2019-01-24
| |
| * README: some tweaksdequis2019-01-24
| |
| * Add instructions for Fedora and RHEL/CentOSRobert Scheck2019-01-24
| |
| * Update FB_ORCA_AGENT version 38 to 192dequis2019-01-07
| | | | | | | | Thanks thorgrin for pointing this out
| * ..properly fix "Failed to read fixed header" with TLS 1.3dequis2019-01-05
| | | | | | | | | | | | | | Since now I can reproduce the thing (not very reliably, but often enough), I see that I was using the wrong function. ssl_pending() means stuff left in the ssl library buffer that we can read, what we want to check is EAGAIN.
| * Merge branch 'master' into developmentdequis2018-12-26
| |\
| | * Load is_work through FbData, fixes api key issues after the first login.dequis2017-10-17
| | | | | | | | | | | | | | | I have no idea what request after login requires api keys, though. This plugin signs all post-login requests pointlessly.
| | * Work chat login support (enable the "work" setting to use it)dequis2017-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This covers three autodetected login types: 1. Work account password Simple, very similar to normal account types 2. Linked personal account This is deprecated but still needed in some companies. Looks just like password auth to users. In rare cases there may be more than one work account linked to a personal account, in which case this will only use the first one. Usually they can be de-linked by assigning a password (see the official docs) 3. SSO This one is awkward. The password can be set to garbage and users will receive a PM with instructions to do an oauth-like login, but there's no explicit auth code screen, just a redirect to a fb-workchat-sso://, which probably results in an error. Users are expected to copy that url, hopefully from the address bar. Not very practical, but works! In all cases, the username is the work account email.
| | * README: mention depsdequis2017-10-16
| | |
| * | Fix "Failed to read fixed header" with TLS 1.3dequis2018-12-26
| |/ | | | | | | | | | | | | | | | | | | | | Ported from a march 2018 commit in purple-facebook, which is when NSS updated to TLS 1.3, and purple often uses NSS. Now it's happening with gnutls 3.6, and bitlbee often uses gnutls. The code is slightly different because bitlbee has ssl_pending(). Unfortunately, I wasn't able to test this, because even with that version it works for me. Who knows. Maybe this doesn't fix anything at all.
| * Replace obsolete m4 macros, thanks to Robert-André MauchinRobert Scheck2017-10-16
| | | | | | | | | | - https://bugzilla.redhat.com/show_bug.cgi?id=1290235#c3 - https://www.gnu.org/software/libtool/manual/html_node/LT_005fINIT.html
| * Document the unknownsAbyr Valg2017-10-16
| |
* | release to unstabledebian/1.1.2-1archive/debian/1.1.2-1Sean Whitton2017-09-09
| |
* | bump std-ver to 4.1.0Sean Whitton2017-09-09
| |
* | Commit Debian 3.0 (quilt) metadataSean Whitton2017-09-09
| | | | | | | | [dgit (3.12) quilt-fixup]
* | changelog for 1.1.2-1Sean Whitton2017-09-09
| |
* | Merge tag 'v1.1.2'Sean Whitton2017-09-09
|\ \ | |/
| * Release 1.1.2 with the thrift unknown field fixdequis2017-08-30
| |
| * README: scratch an itchdequis2017-08-30
| |
| * Fix "Failed to read thrift" with unknown fields in /t_p payloaddequis2017-08-30
| | | | | | | | | | >Login error: Failed to read thrift: facebook-api.c:1815 >fb_api_cb_publish_pt: assertion 'FALSE' failed
| * Fix login hang/timeout when the last page of contacts is emptydequis2017-07-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The contact list is fetched in pages of 500, but non-friends need to be filtered out, so you could end up in a situation where the last page of results is all non-friends. The "contacts" signal was emitted for each page of results, and has a flag that says if it's complete, which lets login continue. So when the last page of the contact list is empty (all non-friends) the contacts signal isn't emitted, and login gets stuck forever. This commit changes it so that the signal is emitted with an empty 'users' GSList when it's complete (and when it's an initial fetch, not when when parsing deltas, which doesn't use the 'users' GSList) Thanks to dcxk for finding this and helping debug it.
| * Add tweak values 1-15, sets orca version in the user agentdequis2017-07-07
| | | | | | | | | | | | | | | | | | | | | | | | | | Since there are some issues I can't reproduce, let's do this experiment properly and figure out if this really matters. Value 1 is slightly newer. Value 2 is newer with the current set of fields. Value 3 is what purple-facebook uses. Adding 4 makes it http only, adding 8 makes it mqtt only. Some values are redundant. I suggest trying 1, 2, 3, 7 and 11.
| * Add "tweak" hidden setting, does nothing for now.dequis2017-07-07
| |
| * Revert "Makefile.am: add -no-undefined for cygwin"dequis2017-05-29
| | | | | | | | | | | | | | | | | | This reverts commit 310de485e9597df35e94cd4020f8b23121cb3904. Turns out it wasn't harmless, and it breaks mac OS. Instead of adding platform checks here, this flag is now included in the cygwin-specific parts of the bitlbee pkg-config file, as of bitlbee commit b9c10a1a (version string 3.5.1+20170529+develop+18-gb9c10a1a-git)
| * Makefile.am: add -no-undefined for cygwindequis2017-05-13
| | | | | | | | | | | | | | | | | | | | Quoting https://cygwin.com/ml/cygwin/2013-07/msg00421.html >despite popular misconception, this flag is harmless on non-PE targets This also depends on changes on the bitlbee side to be able to link to bitlbee itself, see bitlbee commit 54b2a367 (version string 3.5.1+20170513+develop+16-g54b2a367-git)
| * .travis/obs.sh: depend on bitlbee 3.5 for those packages onlydequis2017-04-26
| | | | | | | | | | | | | | | | | | Since bitlbee 3.5.x is not ABI compatible with 3.4.x and those packages are built against 3.5.x. This caused crashes when using fbchats, which accesses irc->b, which is one of the last members of the irc struct, which had another member added in the middle (auth_backend, 8e6ecfe) Fixes #142
| * configure: use argument value variablesdequis2017-04-02
| |
| * README: change homedir instructions to just use pkg-configdequis2017-04-02
| |
* | Commit Debian 3.0 (quilt) metadatadebian/1.1.1-1archive/debian/1.1.1-1Sean Whitton2017-04-02
| | | | | | | | [dgit (4.0) quilt-fixup]
* | changelog for 1.1.1-1Sean Whitton2017-04-02
| |
* | Merge tag 'v1.1.1'Sean Whitton2017-04-02
|\ \ | |/
| * Release 1.1.1 with one last fix to last week's changesdequis2017-04-02
| | | | | | | | I waited for things to settle down with this one
| * Send orca-formatted user agent for all HTTP requests toodequis2017-03-30
| | | | | | | | | | | | | | | | | | | | | | Fixes "Failed to parse thread information" errors when joining channels. Facebook rolled a hotfix update today and they are requiring the same user agent for HTTP requests too. As far as I can see the main affected request is ThreadQuery. Hopefully this also solves issues some a tiny minority of people were still having with sync sequence ids.
* | upload to unstabledebian/1.1.0-1archive/debian/1.1.0-1Sean Whitton2017-03-29
| |
* | Commit Debian 3.0 (quilt) metadataSean Whitton2017-03-29
| | | | | | | | [dgit (3.10) quilt-fixup]
* | changelog for 1.1.0-1Sean Whitton2017-03-29
| |
* | Merge tag 'v1.1.0'Sean Whitton2017-03-29
|\ \ | |/
| * Release 1.1.0 with fixes to server-side changesdequis2017-03-29
| |
| * fb_api_http_query: Handle FB_API_QUERY_SEQ_ID in the switchdequis2017-03-29
| | | | | | | | Last commit was broken
| * Use the new ThreadListQuery hash for seq id only, not for thread queriesdequis2017-03-29
| | | | | | | | | | Since it's used for different things and parameters are all wrong with the newer query hash, but the seq id query doesn't use parameters.
| * Set the MQTT user agent to look like Orca-Android 38.0.0.22.155dequis2017-03-29
| | | | | | | | | | | | | | | | | | | | | | Looks like this is what they use to discontinue older versions. An empty user agent is treated as too old. This fixes following error when sending messages: This app version no longer supports messaging. To continue to send and receive messages, please update your app to a newer version or use the mobile web version of Facebook.
| * Update ThreadListQuery hash, fixes sync_sequence_id issues, thanks Eiondequis2017-03-29
| | | | | | | | | | | | | | | | | | | | | | This hash represents a graphql query cached in the server. We were using an old version of the hash that broke for some reason, possibly related to the fact that fb messenger versions older than 5 are being discontinued. For reference, the oldest parts of the plugin were written when 4 was the latest version, most parts are updated to 33 or 38, and the newest parts are based on 100 or so. Thanks EionRobb for coming up with this fix so quickly.
| * Fix crash when the error signal is raised and glib has G_ENABLE_DEBUGdequis2017-02-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If glib is built with --enable-debug=yes, it will have G_ENABLE_DEBUG set internally This flag changes the g_marshal_value_peek_object() macro to use g_value_get_object(), which performs sanity checks, instead of doing a direct offset access. The definition of our error signal was wrong, using a marshaller with a GObject in the first parameter but setting the type of the GValue to G_TYPE_ERROR. Since we have no marshaller for G_TYPE_ERROR, and that all of those are functionally equivalent (and in fact use the exact same code in non-debug builds), I went with POINTER for both sides. The actual crash happened because of a g_return_val_if_fail() in the sanity checks which made it return NULL after throwing a warning like this: g_value_get_object: assertion 'G_VALUE_HOLDS_OBJECT (value)' failed This was reported by a gentoo user who had the debug use flag. Thanks!
| * Fixed receiving attachmentsKamal Galrani2017-02-24
| |
| * Fix creating threads, inviting, kicking members (misc api changes)dequis2017-02-24
| |
| * Fix setting channel topics (tid=t_id.1234 is no longer valid)dequis2017-02-24
| | | | | | | | The server expects the tid parameter to be just the tid now.