Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Message from discussion New project idea: Bringing back Twitter SMS

View parsed - Show only message text

Received: by 10.214.182.1 with SMTP id e1mr1596733qaf.23.1218715079930;
        Thu, 14 Aug 2008 04:57:59 -0700 (PDT)
Return-Path: <michaelsli...@gmail.com>
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.191])
        by mx.google.com with ESMTP id 7si3576660yxg.0.2008.08.14.04.57.58;
        Thu, 14 Aug 2008 04:57:59 -0700 (PDT)
Received-SPF: pass (google.com: domain of michaelsli...@gmail.com designates 209.85.142.191 as permitted sender) client-ip=209.85.142.191;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of michaelsli...@gmail.com designates 209.85.142.191 as permitted sender) smtp.mail=michaelsli...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by ti-out-0910.google.com with SMTP id d10so213435tib.22
        for <silicon-beach-australia@googlegroups.com>; Thu, 14 Aug 2008 04:57:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:reply-to
         :to:subject:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references;
        bh=XsNhoWtukZ987EAcA+DA/xA6lIM3euRNvbY4HFlFQpQ=;
        b=J8VEPdb7lo2/1ZNyxH67rP5PekUteVMa7CS3iJ0ai1DOtMp1p3kKBqRJIHzoJuTv/M
         zm4MyzIMI5UUvsskiwCRpJVU8vGyrWU84WKRek5Chh1acXZgYVGF/jEjxjnlyk768NPq
         2prLKQB7qSrwwM3gb1ALwAxYIuuXyUqKXIasA=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=HjRo+SidEeXTe66DRDvXAGysMdMNF4x9rRUCdzpItVchAu9094MNH60Xk43vOKa4ip
         C4gP+TSB7Dfind6iBI1W2j2/D8aRSFkSy27NAZxPw5GVHCmG5ljRX5eyBB+vjNz9Sohr
         12n/e7akA6XJf6WAGiZjx5ShkLyWKdHA8TY68=
Received: by 10.110.95.15 with SMTP id s15mr1042235tib.40.1218715077623;
        Thu, 14 Aug 2008 04:57:57 -0700 (PDT)
Received: by 10.110.57.18 with HTTP; Thu, 14 Aug 2008 04:57:57 -0700 (PDT)
Message-ID: <5e01c29a0808140457q4b17fcckaab7cc99f790...@mail.gmail.com>
Date: Thu, 14 Aug 2008 21:57:57 +1000
From: silky <michaelsli...@gmail.com>
Reply-To: michaelsli...@gmail.com
To: silicon-beach-australia@googlegroups.com
Subject: Re: [SiliconBeach] Re: New project idea: Bringing back Twitter SMS
In-Reply-To: <9764bcf2-6690-433a-a43f-dcd02972f...@z11g2000prl.googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <ecf61834-df56-4423-9c64-c90bca61e...@s1g2000pra.googlegroups.com>
	 <9764bcf2-6690-433a-a43f-dcd02972f...@z11g2000prl.googlegroups.com>

the main problem i see with this is that making people pay for
incoming sms' *sucks* majorly. they can't control it (except by
incuring a cost).

you're free to ignore this and do it, but what it will result in is a
backlash against twitter itself. people will start to associate a cost
with it's use.

big mistake, imho.

-- 
noon silk

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google