Delivery-Date: Tue, 03 Nov 2015 15:10:00 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 1287B1E069A
	for <archiver@seul.org>; Tue,  3 Nov 2015 15:09:59 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0FAAC37A62;
	Tue,  3 Nov 2015 20:09:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 31339376D9
 for <tor-talk@lists.torproject.org>; Tue,  3 Nov 2015 20:09:48 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id EdusgbHByUSF for <tor-talk@lists.torproject.org>;
 Tue,  3 Nov 2015 20:09:48 +0000 (UTC)
Received: from gwaihir.sccs.swarthmore.edu (secure.sccs.swarthmore.edu
 [130.58.218.8])
 by eugeni.torproject.org (Postfix) with ESMTP id 161B3375A5
 for <tor-talk@lists.torproject.org>; Tue,  3 Nov 2015 20:09:48 +0000 (UTC)
Received: by gwaihir.sccs.swarthmore.edu (Postfix, from userid 115)
 id 66263986D2; Tue,  3 Nov 2015 15:09:45 -0500 (EST)
Received: from thinkpad.swarthmore.edu (dhcp-130-58-109-234.swarthmore.edu
 [130.58.109.234])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by gwaihir.sccs.swarthmore.edu (Postfix) with ESMTPSA id 6608A870AC
 for <tor-talk@lists.torproject.org>; Tue,  3 Nov 2015 15:09:44 -0500 (EST)
Date: Tue, 3 Nov 2015 15:09:43 -0500
From: Michael McConville <mmcconv1@sccs.swarthmore.edu>
To: tor-talk@lists.torproject.org
Message-ID: <20151103200942.GA9519@thinkpad.swarthmore.edu>
References: <5638FC31.4090007@openmailbox.org>
 <20151103190946.GA15524@thinkpad.swarthmore.edu>
 <20151103192151.GB13472@riseup.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20151103192151.GB13472@riseup.net>
Subject: Re: [tor-talk] Can't log in to Facebook or use Facebook via Tor
 Messenger
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Sukhbir Singh wrote:
> * Michael McConville:
> 
> > Facebook stopped supporting XMPP and recently broke XMPP
> > compatability. This is likely the problem, and there isn't an easy
> > solution. James Geboski's libpurple plugin is the main open source
> > implementation of their new proprietary protocol, IIUC.
> 
> This is also true. See:
> 
>     https://developers.facebook.com/docs/chat
> 
> But XMPP is still working and so is Tor Messenger. It seems like
> either the docs are outdated, or the service is stil running but maybe
> it's not being maintained, or whatever.
> 
> We got in touch with FB to clarify this and are waiting to hear from
> them.

Recently, their XMPP server silently began assigning authenticating
users strings of random digits (e.g. 0329802437509@facebook.com,
approximately) as usernames. I remember a core Pidgin dev with a lot of
protocol experience saying that accepting this response is either unsafe
or a protocol violation (maybe both). However, most clients do, and
therefore still work with Facebook.

Regardless, having a username like that isn't very usable. I think there
are new issues with fetching buddy lists, too.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

