On the other hand if you say that at the 100 view mark, if a link has a ratio above 7 clicks to every 10 views (for example) then it gets added to the top of the rss feed of top headlines, this will be much more accurate at spotting good links instead of just links that a lot of people have seen. If you're only posting links that a lot of people have seen then nobody will bother clicking on them in Twitter, because they will have already seen it somewhere else.
"Views" meaning what, Gerry? The number of people who visited DR and who subscribe to a certain site's feed while that link was available? I.E., the number of individuals who had that link appear among their subscribed feeds?
I admit my way is crude, at least without a time element (and I've figured out how to add that in--but it has other effects too, so I might not... more later after I think it through).
But I think the only practical way to work it is to work from the list of clicked headlines. It's already there, and we have a good idea of interest from its numbers. It's much more indicative than views, which only go to a specific site's popularity, and only vaguely to the subject matter of the headline.
As for "easiest to code," well, maybe, but I have to work within my own limitations.
I've worked out a way the Uptrending headlines can be displayed without the problem indicated in my last post. First, they'll always be on the default page and the page of those who subscribe to that feature. But for those who don't subscribe, but are configured users, I'll use an env factor -- referrer. If referred by twitter, the uptrend headlines will show on their DR config. (I think--have to look closer at twitter referrals)