Re: Microblogging Workflow

[Anthony Papillion <anthony papillion me>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 5/29/2012 4:19 PM, Allan Day wrote:
> Tobias Mueller <muelli cryptobitch de> wrote:
>>> The only thing I've found which is able to do what we need is 
>>> Tweetdeck.
>> I haven't seen why using "at" doesn't do what we want. Have I
>> missed that?
> ...
> 
> If you schedule posts, other contributors need to be able to see
> what has been scheduled. Otherwise you could easily end up with
> conflicts.
> 
> And I don't want to have to leave a machine running to know that a 
> post will be made. We might want to schedule posts weeks in
> advance.

Tweetdeck is great except it's not really for group microblogging. I'm
part of a crisis mappers group and we use a service called "Timely" to
coordinate tweeting as a team. It's great and it lets people
collaborate on the tweets sent out, track metrics, reach, etc.

I believe the site is www.time.ly but if that's not it let me know and
I'll dig it up.

HTH,
Anthony
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)

iQIcBAEBCAAGBQJPxUI8AAoJEE8yDBL3zdVph7AP/3Z9qGJPDx58BRjk+VamE1fI
OYsTOAWq2hZBQbci6Xe1xO5VOMqvgQYji/rSl/D6WUV3ZPdyaXvP3Jks2Y0QyYOV
g5zI1GIcNOAHQO9Tqx53QrX6MVe8kc7HkebLGzjg+982D//kA60y0dT7elZi7+0B
uwH0NRHdLQYVin8J00kfyLhOZpT1nCu8bxtOxO6SmYZ8EQaVWxsVKPEhAK5s3UJf
zl+YWAKHkXOaUP3/nDNxJBrtMZtFYJWoX8ZPWCFpZWpqdBjXOnlqsBZVF4acHsbH
ohfYl7MA8Ii1L2SsdA8ivRJRfTRWFMH20Y+GcOxACkKp+DOcIK28Rt35gW9F4L5e
pDb3xFHkFDyByKUGKui+V+ruhPC2CbBIQItPwIvkre4j0ze1uZQUQR9zxLfzYHnT
D6DAsG9LpHuOK8j/7neWCLVdCH6O7iCuqrycRShB0+lyq/RODw2OuEz9BgvRgCmj
kjbuXiHpxjG4tliVXFGJ9DVfETRBGvPH0TFnjJnWoROp7CQeEHJ1W0TsKmAt17rB
JPNSnNpyrUCEdHBZ8QsryYJHRvpbUzV1YZhoOEpttYFijOpFCq5r7yRS/luxkxxl
ajzFjMKlcEvaniXixck0pmMVfaZYCId8eO2KPQbaW7JtRw8nIQSzSIEF0n/F5X/4
b4/AkcFQIJAcUmChzWUk
=QUAa
-----END PGP SIGNATURE-----