Matt Wardman wrote:
>> Why, and in what way, is twitter the right channel for this? Twitter is
> designed, and best used, for immediate, transitory, concise and
> low-importance data that you're unlikely to detail for or to refer back
> to, or for keeping low-level "ambient" contact with particular individuals.
>
> Ouch :-)
>
> ISTM that Twitter - like Text Messages and Email - is a flexible
> service suitable for whatever people want to use it for.
>
> Unlike email, for example, every Tweet in the world can be referred
> back to since they all have their own permalink.
>
>> immediate, transitory, concise and low-importance data
>
> I'd say a planning "alert", as opposed to a planning "notice", meets
> all these criteria admirably
Fair enough, and all true, but personally I see it as a bit of a forced
combination; like receiving your shopping by catapult. I certainly
wouldn't oppose the project, but I'd be inclined to include an email option.
Yes, people are more than welcome to receive information by whatever
means they feel appropriate, but I've so many weird twitter mashups
recently I have to wonder if many things are being done because they're
possible rather than because it's the most useful approach!
The key problem of referring back to tweets is that 1) they're not the
canonical source of the data, and 2) we have no idea of just how long
old tweets will actually stick around. Certainly, most desktop clients
(AFAIK) don't use an "inbox" which then keeps input around indefinitely.
Richard
--
Blog: http://phase.org
Twitter: @parsingphase
_______________________________________________
Mailing list [email protected]
Archive, settings, or unsubscribe:
https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public
