Message from discussion
New project idea: Bringing back Twitter SMS
Received: by 10.215.39.19 with SMTP id r19mr8159173qaj.0.1219024787068;
Sun, 17 Aug 2008 18:59:47 -0700 (PDT)
Return-Path: <mark.ne...@gmail.com>
Received: from yx-out-1718.google.com ([172.21.6.34])
by mx.google.com with ESMTP id 39si13688087yxd.2.2008.08.17.18.59.46;
Sun, 17 Aug 2008 18:59:47 -0700 (PDT)
Received-SPF: neutral (google.com: 172.21.6.34 is neither permitted nor denied by domain of mark.ne...@gmail.com) client-ip=172.21.6.34;
Authentication-Results: mx.google.com; spf=neutral (google.com: 172.21.6.34 is neither permitted nor denied by domain of mark.ne...@gmail.com) smtp.mail=mark.ne...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by yx-out-1718.google.com with SMTP id 34so1050204yxf.70
for <silicon-beach-australia@googlegroups.com>; Sun, 17 Aug 2008 18:59:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:received:received:from:to:references:subject
:date:message-id:mime-version:content-type:content-transfer-encoding
:x-mailer:thread-index:x-mimeole:in-reply-to;
bh=aqzmcb4xYBb1I4B3al7LMNqUKcReRG06HplRlCW8Jrs=;
b=dgKL6o/WaSx35H0KBLNFjmoVjOsdEPdwlkd/Y9niKEVDK5dYz5WNRInRzSsVMVWuNA
sMz+MKXtPs31TbC+zb/oXSoucdTdgJndB1R66bCUhRsdWCTw/lbfM+Cx2L6MVG9dIj8P
ut3cvvqN4ZO+f7akiGagtAqEavfNkVLo/uhu0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=from:to:references:subject:date:message-id:mime-version
:content-type:content-transfer-encoding:x-mailer:thread-index
:x-mimeole:in-reply-to;
b=Yrenk8PXASaCjdpNGoasnUU9z0NuNQPxXN/F/Bv0OSqUpjzWfC5mOaOWpjzqKKL/eE
Q7KuV2EYuthjBv0/TyM67xF7SALmNdgtMNgFx0t9SWpeXEjgnwMl+Ju3mBQR9k1bJY78
I50a4OJrqDuEg9uADV2oVjtmjLh85l8T2jf8s=
Received: by 10.151.145.11 with SMTP id x11mr5889623ybn.46.1219024785930;
Sun, 17 Aug 2008 18:59:45 -0700 (PDT)
Return-Path: <mark.ne...@gmail.com>
Received: from HYPERDEXE ( [124.170.94.93])
by mx.google.com with ESMTPS id 34sm2230781yxl.9.2008.08.17.18.59.42
(version=SSLv3 cipher=RC4-MD5);
Sun, 17 Aug 2008 18:59:44 -0700 (PDT)
From: "Mark Neely" <mark.ne...@gmail.com>
To: <silicon-beach-australia@googlegroups.com>
References: <ecf61834-df56-4423-9c64-c90bca61e...@s1g2000pra.googlegroups.com> <5e01c29a0808140457q4b17fcckaab7cc99f790...@mail.gmail.com> <D8D25AE89091A348AF840CCAC9BB1EE14F7665D...@win2k3.local.internetrix.com.au> <be77b7e70808140509q55d25995ra54a5cefa381c...@mail.gmail.com> <5e01c29a0808140511k3f46751x590aa4d6ee700...@mail.gmail.com> <060401c8fe07$4852a0e0$d8f7e2a0$@com> <D8D25AE89091A348AF840CCAC9BB1EE14F7665D...@win2k3.local.internetrix.com.au> <5e01c29a0808141451h6b8b519fs1693e51afef2...@mail.gmail.com> <77a0e382-8092-4629-b77c-337798c15...@v39g2000pro.googlegroups.com> <33035fd4-0d1e-4d50-8b14-6470e6e0b...@r15g2000prh.googlegroups.com> <f610bda80808170341k5f16dfccpd650e75402bfb...@mail.gmail.com> <D8D25AE89091A348AF840CCAC9BB1EE14F7A9E7...@win2k3.local.internetrix.com.au> <a105c345-d8cc-4101-9567-9150d62f4...@z11g2000prl.googlegroups.com>
Subject: RE: [SiliconBeach] Re: New project idea: Bringing back Twitter SMS
Date: Mon, 18 Aug 2008 11:59:36 +1000
Message-ID: <071101c900d6$139bd1b0$0301a8c0@HYPERDEXE>
MIME-Version: 1.0
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AckAerplLHp4CF1CRSSoUArTzzSzngAWYQdg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <a105c345-d8cc-4101-9567-9150d62f4...@z11g2000prl.googlegroups.com>
Hi,
I'm sure that developing a Twitter-to-SMS would be a fairly straightforward
exercise, given their API and the fact they currently support it in other
countries.
I am just wondering if this is a retrograde solution.
Anyone who has dealt with telcos will tell you that they love to skim
profits. The artificially high data rates for mobile data (and SMS for that
matter) is a classic case in point. They charge like wounded bulls because
they can - they own the infrastructure and, in the case of SMS, they own the
billing engine.
Given that 3G is fast becoming a standard globally, why would you develop a
solution based on 1G technology - and force yourself into bed with the
profiteering telcos?
Why not look at the other data channel (IP) and use that to create an
SMS-esque application? Create a solution that gives a SMS-like experience -
beeping/vibrating when incoming messages are received, with a reply service
- but which operates independently of a specific carrier?
And, if you're going to go down that path, why not build the app in such a
way that it can be interfaced with other social services?
The pain that has been articulated - wanting to keep an eye on 'social
updates' when away from your primary computer - is real. But it is felt by a
lot more people than just Twitter users.
Regards,
Mark
-----
Mark Neely
Master Strategist
Infolution Pty Ltd
e: m...@infolution.com.au
m: +61 (0)412 0417 29
skype: mark.neely
Read my blogs --> www.infolution.com.au
www.neelyready.com
Connect on LinkedIn --> www.linkedin.com/in/markneely
-----Original Message-----
From: silicon-beach-australia@googlegroups.com
[mailto:silicon-beach-australia@googlegroups.com] On Behalf Of Bart Jellema
Sent: Monday, 18 August 2008 1:06 AM
To: Silicon Beach Australia
Subject: [SiliconBeach] Re: New project idea: Bringing back Twitter SMS
I don't think pricing is an issue at all... I just build it with my modem
for fun... using a gateway is just as easy and just as cheap...
5c to 7c per message... http://www.clickatell.com/pricing/pricing_wizard.php
|
