Delivery-Date: Sun, 20 Sep 2015 16:33:57 -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 7D2831E0834;
	Sun, 20 Sep 2015 16:33:55 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id BDDE136BE2;
	Sun, 20 Sep 2015 20:33:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 79D1836BDF
 for <tor-talk@lists.torproject.org>; Sun, 20 Sep 2015 20:33:44 +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 Cd6Lv1C7mHGX for <tor-talk@lists.torproject.org>;
 Sun, 20 Sep 2015 20:33:44 +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 1415A35A7F
 for <tor-talk@lists.torproject.org>; Sun, 20 Sep 2015 20:33: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=wR3pzPCJHimtIIzmRu2nGua45dvR81/ckGFRVJAzZ6o=;
 b=sc7ZHoO+9LffOWJKQ6BVIYLDLByj3jLT+AnhKV+VO/oQiHKV1qRfz7UptEPxlOSovrAKQosMKOPTGwfhZtImUKKQc90zNAKQGEbnBfS3PlggEeCQHahH81+vl5VR3llHidOrVvudS5oXkEa24Jhf5lCXX7ww1nSz21afF2K3nk8=
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)
 ; Sun, 20 Sep 2015 22:33:16 +0200
Message-ID: <55FF1810.5080808@bitmessage.ch>
Date: Sun, 20 Sep 2015 20:33:20 +0000
From: Tempest <tempest@bitmessage.ch>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <55F6100C.5030200@bitmessage.ch>
 <20150920201055.8991.94484@solidarity.enteig.net>
In-Reply-To: <20150920201055.8991.94484@solidarity.enteig.net>
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>

malte@wk3.org:
> Maybe this is a good opportunity to invite people to Diaspora again.
> It's still not perfect, but it's running for something like 5 years now
> without major glitches and is only getting better.
> 
> It is tor-friendly (some admins even run relays and exits) and not
> censorable in whole (admins of a Diaspora instance can take measures,
> though, to block posts from another pod or a specific user).

i whole heartedly agree and i am considering including diaspora
instructions in a guide i work on in the near future. i am entirely
sympathetic to twitter's frustration with bots that use tor for purposes
that conflict with their terms of service. however, their recent
approach to dealing with that is simply ensnaring too many users who,
upon a cursory glance at their time line, are clearly not bots. rather,
they are simply using tor, which twitter can distinguish by the
connection logs. thus, i am increasingly unsatisfied with twitter's
response that they "aren't targeting tor users." while this may have a
modicum of truth to it, they clearly aren't doing enough to protect tor
users either, and have adopted a solution that uses a nuclear bomb,
rather than a fly swatter, to deal with spambots. the fact remains that
their recent changes in security procedures have made it increasingly
difficult for average tor users to maintain a presence on twitter.
meanwhile, some diaspora pods are going as far as offering onion
services. twitter needs to get its act together since, over the past 37
days, the shortest response time i've had for their mistaken security
protocol took 12 hours. the longest took 2 weeks, where twitter support
had simply given up on responding to me and i sorted it by changing an
email address associated with my account, which is pretty much a joke
security mechanism in the first place.

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

