When I go into one of my tracks, I've tried disabling the "allow others to download" option, then republish, but the changes are not reflecting. Looks like users are still able to download, even though I've unchecked this option in the properties.
When I go into one of my tracks, I've tried disabling the "allow others to download" option, then republish, but the changes are not reflecting. Looks like users are still able to download, even though I've unchecked this option in the properties.
Comments (3)
Even if you were to disable downloads, people can still download your content using a clever backdoor that I mainly use to embed my Audiotool music into stuff. Also, when HTML was able to be inserted into the sidebar in Junon.io, I would use this clever backdoor to play random music in my free admin world in such a way everyone in that world can hear it. This clever backdoor is accessing the actual sound file itself. I know the general format of the URL for this specific resource in relation to the URL for the song's page. It's not hard.
That's concerning. I'd imagine none of the devs are aware of this then? Should be patched and artists work should be protected.
I don't think there's a way to do this. If someone can hear the track, the file for it is in their browser, so there's always a way to go find the file. The only way to protect artists' music is to slap policies and stuff on said music and sue anyone who dares use it without artists' permissions. Although for things like international offenses, like if someone in China steals a song that belongs to someone in the US, I have no idea if that'll even work. The CCP in China would probably defend its citizens from international lawsuits and stuff like that, making it even easier for people there to conduct industrial theft and sell back lower quality cheated products to the world.