> You're confusing Twitter with RSS.
>
> RSS is a way to "push" this type of information out to people.
>
> Twitter is the wrong tool.

Well, is it? Yes, you're right, I AM thinking of using this like RSS,
but is that necessarily wrong?

To put it in context, there are lots of people who read the day's
obituaries (or other family announcements) in their daily newspaper. I
could imagine these people being interested in receiving a list of new
notices daily.

My previous number of 3,500 was the number of new notices across a
whole site (which consists of many newspapers), but for individual
newspapers, we're talking about anything between 0 and 100 per day-
usually more like 20-30.  That is manageable.

>
> Now if you're working for a client who insists that they've heard
> about this Twitter "thing" and they want to get their stuff on
> Twitter, that's fine.

There's an element of that :)

>
> If you/they are determined to do this, then the best way to do it
> ("least-worst") solution is to make it so that you are sending the
> fewest number of status updates as possible which are as specific as
> possible.

Sure. In this context, that amounts to a tweet for each new notice
that is published - any less and we'd just be sending stats: "20 new
obituaries", which is meaningless to everybody.

> I'd go on, but "how to use Twitter" is really OT for the list.

:)  .oO( it's that obvious? )

I'd welcome other ideas for how to incorporate twitter into the site,
or pointers to useful implementations by other companies.

thanks

Clint

Reply via email to