[Osmf-talk] Losing faith

Mikel Maron mikel_maron at yahoo.com
Tue Jan 15 15:29:35 UTC 2013


Let's find a pragmatic solution. Sending an email request to send a tweet ... that will kill the impulse. How about http://grouptweet.com/?

 
* Mikel Maron * +14152835207 @mikel s:mikelmaron


>________________________________
> From: Steve Coast <steve at asklater.com>
>To: Richard Fairhurst <richard at systemeD.net> 
>Cc: osmf-talk at openstreetmap.org 
>Sent: Tuesday, January 15, 2013 10:23 AM
>Subject: Re: [Osmf-talk] Losing faith
> 
>
>On Jan 15, 2013, at 7:04 AM, Richard Fairhurst <richard at systemeD.net> wrote:
>> 
>> The tweet in question, which Iván referred to earlier, made us (CWG) aware that we didn't know who had access to the Twitter account, nor any control over what they were posting. Consequently we changed the legacy password and decided to review how we managed it.
>
>In the three months since you took control what have you done to gain on any metric of engagement?
>
>The numbers for the other two crowd sourced maps of the world:
>
>@waze 79,583 followers, 246,238 tweets
>@googlemaps 327,722 followers, 1,806 tweets
>
>Are between seven and twenty times better than our numbers.
>
>@openstreetmap 13,108 followers, 980 tweets
>
>If we assume that somehow our quality is better than their quantity, how do you measure that and what is the plan for improving it?
>
>> Keeping access within CWG, but being open to suggestions is the simple, manageable solution we have arrived at for now. We did consider using a multi-contributor system like HootSuite but don't believe we currently have the resources to justify it.
>
>Another solution would be to let people who already had access tweet.
>
>Steve
>
>
>_______________________________________________
>osmf-talk mailing list
>osmf-talk at openstreetmap.org
>http://lists.openstreetmap.org/listinfo/osmf-talk
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmf-talk/attachments/20130115/5ac60852/attachment.html>


More information about the osmf-talk mailing list