Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@locus.apache.org Received: (qmail 52959 invoked from network); 2 Jan 2009 11:52:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jan 2009 11:52:00 -0000 Received: (qmail 77144 invoked by uid 500); 2 Jan 2009 11:52:00 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 77119 invoked by uid 500); 2 Jan 2009 11:51:59 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 77106 invoked by uid 99); 2 Jan 2009 11:51:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jan 2009 03:51:59 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [212.227.17.2] (HELO mout-bounce.kundenserver.de) (212.227.17.2) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jan 2009 11:51:49 +0000 Received: from [192.168.0.9] (cpc1-addl1-0-0-cust563.hers.cable.ntl.com [86.0.58.52]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis) id 0MKwh2-1LIiYH3xGp-00035N; Fri, 02 Jan 2009 12:50:54 +0100 Message-ID: <495DFF9D.3080503@fortybeans.com> Date: Fri, 02 Jan 2009 11:50:53 +0000 From: Darren Hague User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: esme-dev@incubator.apache.org CC: marcia@marciaconner.com, Bill Fernandez Subject: Re: AW: Thoughts on building a business around ESME References: <384A40FC-EF39-4C04-8024-0DBE7CECB369@gmail.com><3aade1dd0812281731k318ba452mffa24680b353232f@mail.gmail.com><30DB6ACF50A0A3439F39EFEB1C52E166078F2225@nets13ja.ww300.siemens.net><3aade1dd0901012342m5305471aj94ec93b75a9e4685@mail.gmail.com><30DB6ACF50A0A3439F39EFEB1C52E166078F2226@nets13ja.ww300.siemens.net> <3aade1dd0901020138u3cd2eef2g57bcfc1aec7b9acf@mail.gmail.com> <30DB6ACF50A0A3439F39EFEB1C52E166078F2227@nets13ja.ww300.siemens.net> In-Reply-To: <30DB6ACF50A0A3439F39EFEB1C52E166078F2227@nets13ja.ww300.siemens.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX18yf7rID6wAvOgl4K4ntb+japZcwwAT3rAGO6S 0l6DDi7PwxWXqHkeYf6MQgTirCkh9goGuBAf8DldXwBokFcPk5 GOYCT/8MT2scJoiUtenx2Pm4UtUXf8s/37B88WWTkk= X-Virus-Checked: Checked by ClamAV on apache.org I think that a useful lever for ESME adoption would be to make sure that Twitter (& Yammer?) integration is built-in - in other words, ESME should be usable as a Twitter client, so people can access their wider network. Once this is under way, integrating local users becomes easier. A useful default would be for users to specify their Twitter ID on registration/first login, and this would be their ESME ID too - @xyz would then work seamlessly. We would then need a convention for specifiying local-only users (i.e. those who do not have a Twitter account) - perhaps @_abcd or something similar. Along with this, of course, we need to implement the personal/group/local/global permissions model. - Darren