I can see your point with the breathing jukebox… But here’s my take on it: I currently use a single user version of the basic functionality for my internet broadcast (on Eve Radio). My listeners know I’ll entertain requests – doesn’t mean I’ll play ’em. Any thought on how to present it so it’s NOT like a JB?
I like knowing what people want to hear though and the historical record of requests helps determine the “weight” of a song week to week.
Shite requests? Really? It’ll be your collection of tunes, my friend. Each DJ has an “in rotation” list which folks can browse/search. When they find something they want to play they click a button. So the short version is that you’re only going to get requests for tunes that you’ve opted to make available TO be requested. Pretty slick, eh?
It’s kinda like the PHP request system that comes with SAMBC – but better ’cause anyone can use it – not just folks who use SAMBC.
R.
