Delivery-Date: Tue, 15 Sep 2015 06:34:55 -0400
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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,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 A63FB1E0C9F;
	Tue, 15 Sep 2015 06:34:53 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 514E935957;
	Tue, 15 Sep 2015 10:34:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B87B8358E2
 for <tor-talk@lists.torproject.org>; Tue, 15 Sep 2015 10:34:43 +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 LFzOlsPhwRqr for <tor-talk@lists.torproject.org>;
 Tue, 15 Sep 2015 10:34:43 +0000 (UTC)
Received: from mail.bitmessage.ch (mail.bitmessage.ch [146.228.112.252])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 5444335648
 for <tor-talk@lists.torproject.org>; Tue, 15 Sep 2015 10:34:43 +0000 (UTC)
dkim-signature: v=1; a=rsa-sha256; d=bitmessage.ch; s=mail;
 c=relaxed/relaxed; q=dns/txt;
 h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References;
 bh=RKQy51+KBUDjK1Fu+kKvOk0u1B8A5BNQB4OF8yQ4BmM=;
 b=XRtGPm7LOViXuDk/zs91JaMAsqmCWRXlhrGS0z4Ya7tuy+bnux2fkdH+IhEz1zk+R3zvMKPfUpomCcCxyw4xxnzVr8zE7lqFubSKc+L/ThARfiPMl4mrUVykmzbEhS709W1DchCTubM7ukO9wY7ZjzhXtvKM5mSGlz1Z0pcUMFY=
Received: from 127.0.0.1 (BITMESSAGE [127.0.0.1])
 by mail.bitmessage.ch with ESMTPSA
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128)
 ; Tue, 15 Sep 2015 12:34:19 +0200
Message-ID: <55F7F43B.1060502@bitmessage.ch>
Date: Tue, 15 Sep 2015 10:34:35 +0000
From: Tempest <tempest@bitmessage.ch>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <55F6100C.5030200@bitmessage.ch>
 <20150914011907.GA30016@riseup.net> <20150915032734.GL8355@torproject.org>
 <alpine.BSF.2.11.1509150902100.41605@z.fncre.vasb>
In-Reply-To: <alpine.BSF.2.11.1509150902100.41605@z.fncre.vasb>
Subject: Re: [tor-talk] tor + twitter issues
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>

Marcin Cieslak:
> I don't have a phone number behind my Twitter account and it just
> asks me to confirm my email address.
> 
> Not perfect, but way better.

i've never once given twitter a phone number. when it asked me for a
phone number to unlock an account, this was a new measure i hadn't
experienced before. plus, while it may be subjective ignorance on my
part, i was unaware of other users running into this problem unless they
were trying to create an account on twitter. i simply hadn't come across
a use case where a user who already had an account that was in use was
required to provide a phone number after it got locked. twitter support
did end up eventually addressing the issue. however, my experiences with
twitter support have been very hit or miss. sometimes they respond.
sometimes they simply ignore you.

-- 
gpg key - 0x2A49578A7291BB34
fingerprint - 63C4 E106 AC6A 5F2F DDB2 3840 2A49 578A 7291 BB34

-- 
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

