2005-03-21, 09:40 PM
I think that services like TIVO use statistics gleaned from its users as the basis for what shows it recommends/suggests you might like.
For example, let's say that TIVO gathers data that shows that 58% of people who regularly record "The Simpsons" also record "Scrubs", but only 6% of "Simpsons" fans also record "Will & Grace". Â As a result, TIVO will suggest to you, if you schedule a season of the Simpsons, that you might also like "Scrubs".
Of course, in order for this to work on the GBPVR-level, GBPVR users will need to be willing to allow GBPVR or a stand-alone utility to share recording schedule data with a centralized database (anonymously, of course).
Then, GBPVR or the external utility can query the database for recommendations based on statistics collected in the master centralized database.
Programmatically, this probably is not that huge a task - far more challenging will be addressing controversial privacy issues, but those can be mitigated by allowing people to opt out of the service, something I don't think you can do with TIVO.
For example, let's say that TIVO gathers data that shows that 58% of people who regularly record "The Simpsons" also record "Scrubs", but only 6% of "Simpsons" fans also record "Will & Grace". Â As a result, TIVO will suggest to you, if you schedule a season of the Simpsons, that you might also like "Scrubs".
Of course, in order for this to work on the GBPVR-level, GBPVR users will need to be willing to allow GBPVR or a stand-alone utility to share recording schedule data with a centralized database (anonymously, of course).
Then, GBPVR or the external utility can query the database for recommendations based on statistics collected in the master centralized database.
Programmatically, this probably is not that huge a task - far more challenging will be addressing controversial privacy issues, but those can be mitigated by allowing people to opt out of the service, something I don't think you can do with TIVO.