If someone can listen to your audio, they can also record it using a program like Audacity. So there's really no way of preventing people from copying it.
you can create your own audio player. (minified and obfuscated js) that interacts with your web server in random ways.
eg: the js get each packet from your webserver, reverses the bits before letting the datapacket continue onward to being played by the browser.
better yet, reenginneer your own version of LAME or mp4 that only your player knows how to handle. dont tell anyone about said protocol and nobody can play your music but your player.
profit? actually not.
because still, you aren't relying on the cunningness of your algorithm for protection but rather on it being an annoyance for the penetrator to deobuscfate your js and reverseengineer your protocol.
everything can be broken, provided there is enough incentive to do so.
2 comments
[ 2.8 ms ] story [ 13.9 ms ] threadbetter yet, reenginneer your own version of LAME or mp4 that only your player knows how to handle. dont tell anyone about said protocol and nobody can play your music but your player.
profit? actually not.
because still, you aren't relying on the cunningness of your algorithm for protection but rather on it being an annoyance for the penetrator to deobuscfate your js and reverseengineer your protocol.
everything can be broken, provided there is enough incentive to do so.