Message from discussion
New project idea: Bringing back Twitter SMS
Received: by 10.215.40.2 with SMTP id s2mr6953294qaj.26.1218969715255;
Sun, 17 Aug 2008 03:41:55 -0700 (PDT)
Return-Path: <dwe...@gmail.com>
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.229])
by mx.google.com with ESMTP id 39si11934270yxd.2.2008.08.17.03.41.54;
Sun, 17 Aug 2008 03:41:55 -0700 (PDT)
Received-SPF: pass (google.com: domain of dwe...@gmail.com designates 64.233.184.229 as permitted sender) client-ip=64.233.184.229;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of dwe...@gmail.com designates 64.233.184.229 as permitted sender) smtp.mail=dwe...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by wr-out-0506.google.com with SMTP id 50so1718280wra.13
for <silicon-beach-australia@googlegroups.com>; Sun, 17 Aug 2008 03:41:54 -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:to
:subject:in-reply-to:mime-version:content-type:references;
bh=En9+JUHeVw/IioW+aQkghLyYUYu/CdfN61xjtTU94oI=;
b=oHTIZpvqZdT2wlXk4WwJ09y709SluTi1Ev1zpCJD684TzSoAOmZDLX1SQwP7TEiNJN
QlXc19UYRvX6M77ZjkebqCLomJtDS0MTuqk6RVdWtvgy1OWXi+5HqVhsYfKquKts7QaR
J4f/J53KB0glB7l8lTsFh1ECuJRyEBo56PJQ4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:in-reply-to:mime-version
:content-type:references;
b=sjYKb8PVGPjKQnyBTWL8ZXyLFmJAfH9Rai3+lGF9DMp7r/F68wiai5EwtAc2/eXHn4
AEn4Vi6Mi/ZHHL+UzSvbsi0EssuLaXE+NVwPOf3UsClN5dqeWU8/weiJ18VdTYBuzg4a
GmLMx0qbYwJ9vGH40BMMsQX7eXpdvxg4mxaXg=
Received: by 10.90.53.1 with SMTP id b1mr6180433aga.56.1218969713242;
Sun, 17 Aug 2008 03:41:53 -0700 (PDT)
Received: by 10.90.117.13 with HTTP; Sun, 17 Aug 2008 03:41:53 -0700 (PDT)
Message-ID: <f610bda80808170341k5f16dfccpd650e75402bfb0f8@mail.gmail.com>
Date: Sun, 17 Aug 2008 13:41:53 +0300
From: "Davis Weddi" <dwe...@gmail.com>
To: silicon-beach-australia@googlegroups.com
Subject: Re: [SiliconBeach] Re: New project idea: Bringing back Twitter SMS
In-Reply-To: <33035fd4-0d1e-4d50-8b14-6470e6e0b...@r15g2000prh.googlegroups.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_16045_32983473.1218969713230"
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>
------=_Part_16045_32983473.1218969713230
Content-Type: text/plain; charset=ISO-8859-1
Interesting stuff here on SMS.
As a newbie here, I am looking forward to seeing this SMS idea mature into a
realtime projection.
Davis
On Fri, Aug 15, 2008 at 8:59 PM, Bart Jellema <bart.jell...@tjoos.com>wrote:
>
> Just got home from official friday and read (parts of) this thread...
> Decided to give it a whirl and got it working just fine...
>
> http://www.tjoos.com/Img/Tweet2Sms.png
>
> Twitter sends notifications to my email. I poll my email every 30 secs
> and if a new twitter direct mail arrives I'm sending out an SMS using
> my Huawei E220 USB HSDPA Modem. I can put any SIM in this device, so
> could load a prepaid vodafone one with $49 maxicap = $310 = 1240 smses
> = 4 cents per sms. Obviously you'd set limits on both total number per
> day/week and total number from 1 person per day/week to prevent
> someone creating a crazy bill.
>
> So..... who would pay something like 10 cents per received sms? Should
> I build this prototype into a real solution? Does anyone really care?
>
> Time for bed.
>
> On Aug 15, 10:09 am, Elias Bizannes <elias.bizan...@gmail.com> wrote:
> >
> -------------------------------------------------------------------------------------------
> > Adding Ivo's message which for some reason didn't post - Elias
> >
> -------------------------------------------------------------------------------------------
> >
> > Hi Elias and Geoff,
> >
> > I tried posting to the group but got an error message - maybe I'm not
> > allowed post. I've joined the group on google. Does someone need to
> > set me up to post?
> >
> > Anyways heres my email.
> > Ivo
> >
> > ---------- Forwarded message ----------
> > From: Ivo Brett <ivo.br...@gmail.com>
> > Date: Thu, 14 Aug 2008 19:38:12 +0100
> > Subject: Re: [SiliconBeach] New project idea: Bringing back Twitter
> >
> > SMS
> > To: "silicon-beach-australia@googlegroups.com"
> > <silicon-beach-australia@googlegroups.com>
> >
> > Hi there,
> >
> > Thanks for including me on this email and thanks to Elias for
> > introducing me2mobile.com. Premium SMS and bulk SMS is an area I know
> > quite a bit about after having struggled with many different business
> > models in this area. Its interesting that you've mentioned this as I
> > have spent the last couple of weeks looking into the area of SMS
> > enabling 'life streaming' services.
> >
> > A few things I've learnt about running a premium SMS business that you
> > might not already know. Firstly, the costs for a shortcode with a
> > carrier is expensive to setup and maintain. The revenue share is
> > stacked in favour of the operators and they take a large share for no
> > risk. Secondly, you need to be doing a large volume of SMS for any
> > business case to pay off. This means that the only people who make
> > money out of premium SMS are the companies that can afford massive
> > marketing (e.g. late night text for a babe type services). This has
> > resulted in premium SMS being considered a slightly "grubby" service.
> > For all these reasons me2mobile has moved away from premium SMS as our
> > core offering. We now make most of our money out of selling
> > interactive SMS services to businesses (i.e. SMS campaigns using bulk
> > SMS) rather than premium SMS.
> >
> > That being said, I think that your idea has a lot of merit. Twitter
> > have done the hard work of creating a market for this idea (they've
> > just withdrawn their own heavily used sms service). There is also a
> > sizable and well connected twitter user base so it would be relatively
> > easy to get this service 'out there'.
> >
> > Geoff and some of the other posters correctly pointed out some of the
> > necessary mechanics of how premium SMS works so I wont go over them.
> > But you thing that wasnt mentioned was the ability to send a low
> > charged premium SMS (MT) to each follower. This could be as low as 25
> > cents. I do, however, accept the point from Silky that its a pain to
> > have to pay for incoming tweets especially since you dont know how
> > many there'll be but as Elias says you can give people the option to
> > opt out (or set a daily limit on how many they'll receive).
> >
> > Not too make it sound too trivial as I know there'll be some gotchas
> > but I reckon I've implemented about 75% of what needs to be done for
> > this project. I also have an agreement with one of the top premium SMS
> > and bulk SMS aggregators. I selected them after indepth selection
> > process and I reckon I have the best rates and revenue share that one
> > can get. The best thing about this aggregator is that they have
> > premium SMS connectivity in 28 countries so if this offering proven
> > successful in Australia it would be very simple to roll out
> > internationally.
> >
> > I have a good premium SMS shortcode already set up (19961996) with
> > this aggregator (its 55 cents MO). Note: If you were to set up a
> > shortcode yourself it normally takes 6 to 8 weeks to get a shortcode
> > set up and sometimes operators knock back the applications.
> >
> > To be perfectly honest - the most expensive part of my agreement is
> > maintaining the premium shortcode and I have been considering closing
> > this part down altogether. There is one customer using it extensively
> > but I dont push our premium sms offering anymore. Therefore, ne
> > possibility is that I share my current agreement with others that want
> > to take advantage of this shortcode. I'll be a transparent as possible
> > and even share the contract details I have with the aggregator just to
> > show that I wont be creaming any margin off the top. All I'd ask is to
> > be involved in the service and any revenues generated by it.
> >
> > I'd like to be involved in this project as I think its got a lot of
> > legs. I'm back in Ireland at the moment but I can have a call with
> > others if that helps speed things up.
> >
> > Ivo
> >
> > On 8/14/08, Geoff McQueen <geoff.mcqu...@internetrix.com.au> wrote:
> >
> > - Show quoted text -
> > > Elias,
> >
> > > Sounds interesting. As someone who's messed around with premium SMS
> before,
> > > could I confirm the idea is:
> >
> > > 1. A "short code" or 19 number be registered in AU
> > > 2. People who send to this number pay a premium to send their SMS
> > > 3. Some of this premium is revenue that goes to the "owner" of the 19
> number
> > > 4. This revenue be re-invested in the community, in whatever form that
> is?
> >
> > > If that is the plan, this would require:
> > > 1. Account setup with a carrier, which I take it you're suggesting
> mobileme
> > > (although [3] wasn't referenced in your post)
> > > 2. Some glue to tie submission posts to the short code as submitting to
> the
> > > Twitter API
> > > 3. Resolving who's going to pay for broadcast/outgoing messages from
> Twitter
> > > (unless people agree to cop a fee per message they get delivered a la
> late
> > > nite adult tv commercials)
> >
> > > I see aspect 3 of the requirements above as the hard bit financially;
> this
> > > is why Twitter is removing support for international 'sending', and
> unless
> > > I'm missing something, the premium SMS creature is more to collecting a
> form
> > > of premium revenue on the user sending you a message, not the other way
> > > around.
> >
> > > Of course, this AU gateway could truncate the messages and fund the
> outbound
> > > transmissions via advertising, but that might be a bit hard to swallow.
> >
> > > Or, am I missing something really important here?
> >
> > > Geoff
> >
> > > -----Original Message-----
> > > From: silicon-beach-australia@googlegroups.com
> > > [mailto:silicon-beach-australia@googlegroups.com] On Behalf Of Elias
> > > Bizannes
> > > Sent: Thursday, 14 August 2008 9:46 PM
> > > To: Silicon Beach Australia
> > > Cc: ivo.br...@gmail.com
> > > Subject: [SiliconBeach] New project idea: Bringing back Twitter SMS
> >
> > > Boys and girls,
> >
> > > <rant>
> > > Since our discussions, things have predictably settled. It was never
> > > the intention that this mailing list becomes a 'chat' forum - there
> > > are plenty of other places for that. Instead, it's a way for us to
> > > have a central node as a community to collaborate on. I'm quite proud
> > > of what's become of it.
> >
> > > One new initiate has been born - the distributed database - which
> > > several silicon beacher's having picked this up and are experimenting
> > > with now. It's going to be interesting to see what we can cook up for
> > > release later this year.
> > > </rant>
> >
> > > But I've now got a new proposal. Building on some thoughts I tweeted
> > > before[1], I have a solution that will do three separate things that
> > > will help our industry.
> >
> > > Background
> > > Twitter has become the most important social networking site for the
> > > Australia tech community. It facilitates meet ups, keeps people up to
> > > date, breaks news, and generally builds community.
> >
> > > Today - news was announced that twitter would be shutting off its SMS
> > > service for international numbers because they now long can
> > > sustain[2] . This leaves Australian users completely out in the cold
> > > on one of the most valuable features of the technology. Separately,
> > > the micro-blogging revolution that Twitter has created is going to
> > > create transformative impacts on the industry. The embrace of Plurk
> > > and Identi.ca by Australia's twitter community to name but two
> > > examples, of how things are happening. However what these open source
> > > solutions lack is an SMS solution.
> >
> > > The idea
> > > What I propose, is that as a community, we create a SMS solution that
> > > brings back Twitter to the phone for us as well as supporting other
> > > twitter clones.
> >
> > > SMS gateways, including an Australian startup in Sydney, allow you to
> > > set up premium SMS plans. So for example, if people subscribe to your
> > > plan - it will cost you 55 cents. However, as the organiser of that
> > > plan, you get 18 cents for every message you get. It's an innovative
> > > revenue model, which I have explored in the past as part of my
> > > research into the mobile web opportunity.
> >
> > > If we can hack together something that links the twitter API and a SMS
> > > gateway API like that of Ivo Brett's startup[2], we can restore SMS
> > > functionality. Oh, and make a bit of money.
> >
> > > Sure, this is a market opportunity for a entrepreneur. I reckon you
> > > could make a quick buck, until a phone company or Twitter wakes up.
> > > But personally, I think it's too small scale an idea to launch a
> > > business, but too big an opportunity to pass up.
> >
> > > So by building this service, as Silicon Beach - we've now got a
> > > revenue stream...for the comunity. The revenue raised, will be 100%
> > > reinvested into the community. Sponsoring conferences, meetups - heck
> > > wherever there is value to support effort in the community.
> >
> > > Twitter becomes useful + we make opensource microblogging useful + we
> > > fund our community without realising it. Three bigs things, and all it
> > > takes is a bit of API hackery as some Jelly-a-thon.
> >
> > > Thoughts?
> >
> > > [1]http://twitter.com/liako/statuses/887005932
> > > [2]
> > >http://blog.twitter.com/2008/08/changes-for-some-sms-usersgood-and-ba.
> ..
> > > [3]http://www.me2mobile.com
> >
>
------=_Part_16045_32983473.1218969713230
Content-Type: text/html; charset=ISO-8859-1
<div dir="ltr">Interesting stuff here on SMS.<br>As a newbie here, I am looking forward to seeing this SMS idea mature into a realtime projection.<br><br>Davis<br><br><br><br><div class="gmail_quote">On Fri, Aug 15, 2008 at 8:59 PM, Bart Jellema <span dir="ltr"><<a href="mailto:bart.jell...@tjoos.com">bart.jell...@tjoos.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Just got home from official friday and read (parts of) this thread...<br>
Decided to give it a whirl and got it working just fine...<br>
<br>
<a href="http://www.tjoos.com/Img/Tweet2Sms.png" target="_blank">http://www.tjoos.com/Img/Tweet2Sms.png</a><br>
<br>
Twitter sends notifications to my email. I poll my email every 30 secs<br>
and if a new twitter direct mail arrives I'm sending out an SMS using<br>
my Huawei E220 USB HSDPA Modem. I can put any SIM in this device, so<br>
could load a prepaid vodafone one with $49 maxicap = $310 = 1240 smses<br>
= 4 cents per sms. Obviously you'd set limits on both total number per<br>
day/week and total number from 1 person per day/week to prevent<br>
someone creating a crazy bill.<br>
<br>
So..... who would pay something like 10 cents per received sms? Should<br>
I build this prototype into a real solution? Does anyone really care?<br>
<br>
Time for bed.<br>
<div class="Ih2E3d"><br>
On Aug 15, 10:09 am, Elias Bizannes <<a href="mailto:elias.bizan...@gmail.com">elias.bizan...@gmail.com</a>> wrote:<br>
> -------------------------------------------------------------------------------------------<br>
> Adding Ivo's message which for some reason didn't post - Elias<br>
> -------------------------------------------------------------------------------------------<br>
><br>
> Hi Elias and Geoff,<br>
><br>
> I tried posting to the group but got an error message - maybe I'm not<br>
> allowed post. I've joined the group on google. Does someone need to<br>
> set me up to post?<br>
><br>
> Anyways heres my email.<br>
> Ivo<br>
><br>
> ---------- Forwarded message ----------<br>
</div><div><div></div><div class="Wj3C7c">> From: Ivo Brett <<a href="mailto:ivo.br...@gmail.com">ivo.br...@gmail.com</a>><br>
> Date: Thu, 14 Aug 2008 19:38:12 +0100<br>
> Subject: Re: [SiliconBeach] New project idea: Bringing back Twitter<br>
><br>
> SMS<br>
> To: "<a href="mailto:silicon-beach-australia@googlegroups.com">silicon-beach-australia@googlegroups.com</a>"<br>
> <<a href="mailto:silicon-beach-australia@googlegroups.com">silicon-beach-australia@googlegroups.com</a>><br>
><br>
> Hi there,<br>
><br>
> Thanks for including me on this email and thanks to Elias for<br>
> introducing <a href="http://me2mobile.com" target="_blank">me2mobile.com</a>. Premium SMS and bulk SMS is an area I know<br>
> quite a bit about after having struggled with many different business<br>
> models in this area. Its interesting that you've mentioned this as I<br>
> have spent the last couple of weeks looking into the area of SMS<br>
> enabling 'life streaming' services.<br>
><br>
> A few things I've learnt about running a premium SMS business that you<br>
> might not already know. Firstly, the costs for a shortcode with a<br>
> carrier is expensive to setup and maintain. The revenue share is<br>
> stacked in favour of the operators and they take a large share for no<br>
> risk. Secondly, you need to be doing a large volume of SMS for any<br>
> business case to pay off. This means that the only people who make<br>
> money out of premium SMS are the companies that can afford massive<br>
> marketing (e.g. late night text for a babe type services). This has<br>
> resulted in premium SMS being considered a slightly "grubby" service.<br>
> For all these reasons me2mobile has moved away from premium SMS as our<br>
> core offering. We now make most of our money out of selling<br>
> interactive SMS services to businesses (i.e. SMS campaigns using bulk<br>
> SMS) rather than premium SMS.<br>
><br>
> That being said, I think that your idea has a lot of merit. Twitter<br>
> have done the hard work of creating a market for this idea (they've<br>
> just withdrawn their own heavily used sms service). There is also a<br>
> sizable and well connected twitter user base so it would be relatively<br>
> easy to get this service 'out there'.<br>
><br>
> Geoff and some of the other posters correctly pointed out some of the<br>
> necessary mechanics of how premium SMS works so I wont go over them.<br>
> But you thing that wasnt mentioned was the ability to send a low<br>
> charged premium SMS (MT) to each follower. This could be as low as 25<br>
> cents. I do, however, accept the point from Silky that its a pain to<br>
> have to pay for incoming tweets especially since you dont know how<br>
> many there'll be but as Elias says you can give people the option to<br>
> opt out (or set a daily limit on how many they'll receive).<br>
><br>
> Not too make it sound too trivial as I know there'll be some gotchas<br>
> but I reckon I've implemented about 75% of what needs to be done for<br>
> this project. I also have an agreement with one of the top premium SMS<br>
> and bulk SMS aggregators. I selected them after indepth selection<br>
> process and I reckon I have the best rates and revenue share that one<br>
> can get. The best thing about this aggregator is that they have<br>
> premium SMS connectivity in 28 countries so if this offering proven<br>
> successful in Australia it would be very simple to roll out<br>
> internationally.<br>
><br>
> I have a good premium SMS shortcode already set up (19961996) with<br>
> this aggregator (its 55 cents MO). Note: If you were to set up a<br>
> shortcode yourself it normally takes 6 to 8 weeks to get a shortcode<br>
> set up and sometimes operators knock back the applications.<br>
><br>
> To be perfectly honest - the most expensive part of my agreement is<br>
> maintaining the premium shortcode and I have been considering closing<br>
> this part down altogether. There is one customer using it extensively<br>
> but I dont push our premium sms offering anymore. Therefore, ne<br>
> possibility is that I share my current agreement with others that want<br>
> to take advantage of this shortcode. I'll be a transparent as possible<br>
> and even share the contract details I have with the aggregator just to<br>
> show that I wont be creaming any margin off the top. All I'd ask is to<br>
> be involved in the service and any revenues generated by it.<br>
><br>
> I'd like to be involved in this project as I think its got a lot of<br>
> legs. I'm back in Ireland at the moment but I can have a call with<br>
> others if that helps speed things up.<br>
><br>
> Ivo<br>
><br>
</div></div><div><div></div><div class="Wj3C7c">> On 8/14/08, Geoff McQueen <<a href="mailto:geoff.mcqu...@internetrix.com.au">geoff.mcqu...@internetrix.com.au</a>> wrote:<br>
><br>
> - Show quoted text -<br>
> > Elias,<br>
><br>
> > Sounds interesting. As someone who's messed around with premium SMS before,<br>
> > could I confirm the idea is:<br>
><br>
> > 1. A "short code" or 19 number be registered in AU<br>
> > 2. People who send to this number pay a premium to send their SMS<br>
> > 3. Some of this premium is revenue that goes to the "owner" of the 19 number<br>
> > 4. This revenue be re-invested in the community, in whatever form that is?<br>
><br>
> > If that is the plan, this would require:<br>
> > 1. Account setup with a carrier, which I take it you're suggesting mobileme<br>
> > (although [3] wasn't referenced in your post)<br>
> > 2. Some glue to tie submission posts to the short code as submitting to the<br>
> > Twitter API<br>
> > 3. Resolving who's going to pay for broadcast/outgoing messages from Twitter<br>
> > (unless people agree to cop a fee per message they get delivered a la late<br>
> > nite adult tv commercials)<br>
><br>
> > I see aspect 3 of the requirements above as the hard bit financially; this<br>
> > is why Twitter is removing support for international 'sending', and unless<br>
> > I'm missing something, the premium SMS creature is more to collecting a form<br>
> > of premium revenue on the user sending you a message, not the other way<br>
> > around.<br>
><br>
> > Of course, this AU gateway could truncate the messages and fund the outbound<br>
> > transmissions via advertising, but that might be a bit hard to swallow.<br>
><br>
> > Or, am I missing something really important here?<br>
><br>
> > Geoff<br>
><br>
> > -----Original Message-----<br>
> > From: <a href="mailto:silicon-beach-australia@googlegroups.com">silicon-beach-australia@googlegroups.com</a><br>
> > [mailto:<a href="mailto:silicon-beach-australia@googlegroups.com">silicon-beach-australia@googlegroups.com</a>] On Behalf Of Elias<br>
> > Bizannes<br>
> > Sent: Thursday, 14 August 2008 9:46 PM<br>
> > To: Silicon Beach Australia<br>
</div></div><div><div></div><div class="Wj3C7c">> > Cc: <a href="mailto:ivo.br...@gmail.com">ivo.br...@gmail.com</a><br>
> > Subject: [SiliconBeach] New project idea: Bringing back Twitter SMS<br>
><br>
> > Boys and girls,<br>
><br>
> > <rant><br>
> > Since our discussions, things have predictably settled. It was never<br>
> > the intention that this mailing list becomes a 'chat' forum - there<br>
> > are plenty of other places for that. Instead, it's a way for us to<br>
> > have a central node as a community to collaborate on. I'm quite proud<br>
> > of what's become of it.<br>
><br>
> > One new initiate has been born - the distributed database - which<br>
> > several silicon beacher's having picked this up and are experimenting<br>
> > with now. It's going to be interesting to see what we can cook up for<br>
> > release later this year.<br>
> > </rant><br>
><br>
> > But I've now got a new proposal. Building on some thoughts I tweeted<br>
> > before[1], I have a solution that will do three separate things that<br>
> > will help our industry.<br>
><br>
> > Background<br>
> > Twitter has become the most important social networking site for the<br>
> > Australia tech community. It facilitates meet ups, keeps people up to<br>
> > date, breaks news, and generally builds community.<br>
><br>
> > Today - news was announced that twitter would be shutting off its SMS<br>
> > service for international numbers because they now long can<br>
> > sustain[2] . This leaves Australian users completely out in the cold<br>
> > on one of the most valuable features of the technology. Separately,<br>
> > the micro-blogging revolution that Twitter has created is going to<br>
> > create transformative impacts on the industry. The embrace of Plurk<br>
> > and Identi.ca by Australia's twitter community to name but two<br>
> > examples, of how things are happening. However what these open source<br>
> > solutions lack is an SMS solution.<br>
><br>
> > The idea<br>
> > What I propose, is that as a community, we create a SMS solution that<br>
> > brings back Twitter to the phone for us as well as supporting other<br>
> > twitter clones.<br>
><br>
> > SMS gateways, including an Australian startup in Sydney, allow you to<br>
> > set up premium SMS plans. So for example, if people subscribe to your<br>
> > plan - it will cost you 55 cents. However, as the organiser of that<br>
> > plan, you get 18 cents for every message you get. It's an innovative<br>
> > revenue model, which I have explored in the past as part of my<br>
> > research into the mobile web opportunity.<br>
><br>
> > If we can hack together something that links the twitter API and a SMS<br>
> > gateway API like that of Ivo Brett's startup[2], we can restore SMS<br>
> > functionality. Oh, and make a bit of money.<br>
><br>
> > Sure, this is a market opportunity for a entrepreneur. I reckon you<br>
> > could make a quick buck, until a phone company or Twitter wakes up.<br>
> > But personally, I think it's too small scale an idea to launch a<br>
> > business, but too big an opportunity to pass up.<br>
><br>
> > So by building this service, as Silicon Beach - we've now got a<br>
> > revenue stream...for the comunity. The revenue raised, will be 100%<br>
> > reinvested into the community. Sponsoring conferences, meetups - heck<br>
> > wherever there is value to support effort in the community.<br>
><br>
> > Twitter becomes useful + we make opensource microblogging useful + we<br>
> > fund our community without realising it. Three bigs things, and all it<br>
> > takes is a bit of API hackery as some Jelly-a-thon.<br>
><br>
> > Thoughts?<br>
><br>
> > [1]<a href="http://twitter.com/liako/statuses/887005932" target="_blank">http://twitter.com/liako/statuses/887005932</a><br>
> > [2]<br>
</div></div>> ><a href="http://blog.twitter.com/2008/08/changes-for-some-sms-usersgood-and-ba." target="_blank">http://blog.twitter.com/2008/08/changes-for-some-sms-usersgood-and-ba.</a>..<br>
<div><div></div><div class="Wj3C7c">> > [3]<a href="http://www.me2mobile.com" target="_blank">http://www.me2mobile.com</a><br>
<br>
</div></div></blockquote></div><br></div>
------=_Part_16045_32983473.1218969713230--
|
