first: in the browse by artist/song/genre listings, provide an alphabetical jump-list so people don't have to scroll through the entire catalog. right now it's not a problem to scroll through the entire database -- it's at a size where this can still be done. but once you hit critical mass, i'm imagining a scenario where someone wants to look at the content on a scope somewhere between a full-catalog browse and a specific search. accessing what's in the database might be an easier task if the information is available at several different granularities. second: (and this may be what user jbembe recently suggested; i'm not sure if i followed that thread correctly) provide a weighted song-recommendation function. pick a song, or a group of songs, from your playlist. other people's playlists are scanned, and playlists that contain your selection(s) are retrieved, providing a pool of songs that have been recommended by people who share some portion of your musical interests. these select playlists are then examined, and if a song exists on (just for instance here) 50% or more of these playlists then it's assumed that the song has some merit and isn't just one person's fancy. lastly, if the song doesn't already exist in your own playlist, it's recommended to you.