Very true and exactly what we plan to do, although when summed up you find that a scoring system is best handled on a server and not a client, i.e. Twitter Search. In the mean time we've got enough things we can do real-time in javascript for our 'filtered' feed.
In our case we're dealing with events/trending topics which can have large amounts of data so run-time web app processing time becomes an issue. On May 19, 2:49 pm, Abraham Williams <4bra...@gmail.com> wrote: > On Tue, May 19, 2009 at 06:06, sillyt...@googlemail.com < > > I know these are just examples but both of those metrics are available to > you and nothing is stopping you from restricting data from accounts based on > those metrics. > > -- > Abraham Williams |http://the.hackerconundrum.com > Hacker |http://abrah.am|http://twitter.com/abraham > Web608 | Community Evangelist |http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. > Sent from Mountain View, CA, United States
