I am wondering what is likely to happen if i made a blog where i would make songs available? Not in a "here are a thousand albums to download for free", but more discussing a single song in a blog post and embedding it in a playable state (and thus also downloadable) served directly from my server (and not some spotify / soundcloud / whatever link).

The blog would not be anonymous, it would be possible to trace the server and everything directly to me. Blog would likely be obscure and not grow much. There would be no ad revenues. I am based in norway (in europe, not in the eu but in the eea in case you are not aware).

Am i looking at a couple of dmca takedown requests, legally enforceable fines, lawsuits? I dont expect to get legal advise i can use as a basis for my defense in a potential legal case in the future, but just wanted to know if you had any insights in what could happen.

you are viewing a single comment's thread
view the rest of the comments

[–] cerebralhawks@lemmy.dbzer0.com 3 points 2 hours ago (1 children)

Either they tell you very sternly to stop, and you do. If not, they may take action, either against you or your host. They can’t do much from another country but they can negotiate with your country to bring you into their jurisdiction. Or they may take action with you not there (it’s early, I believe in absentia is how they say it) and if you come into their jurisdiction they can do something. If you continue to violate their copyrights, they may (attempt to) take more drastic actions.

You might be physically and even financially safe, but it’s still not a bear I’d recommend poking when you could just link to YouTube and have the same effect.

I mean, if you want to facilitate piracy, that’s one thing, but don’t consult social media about it — consult a lawyer instead.

[–] lunsjentilanette@sh.itjust.works 2 points 2 hours ago* (last edited 2 hours ago) (1 children)

Either they tell you very sternly to stop, and you do. If not, they may take action, either against you or your host.

This is mostly what i am hoping will happen - that the first step is always going to give me a chance to comply with a request to remove it.

I mean, if you want to facilitate piracy, that’s one thing, but don’t consult social media about it — consult a lawyer instead.

On the contrary, it is not to facilitate piracy (as in the goal is not to serve files for illegal download), it will include links to legal avenues of purchase and download. Its just that i am thinking about a particular style of embedding this within a blog post that would require me to host the file on my own server - and then that song would be downloadable for anyone who want to (even though i have no explicit "download button").

[–] cerebralhawks@lemmy.dbzer0.com 1 points 1 hour ago

Ah, got it. If there's no obvious way to download, that might count for something, and if the blog doesn't get huge, you might escape notice altogether.

If you aren't trying to facilitate piracy (as in, that's not the goal), maybe the YouTube link would be safer. Or, if you don't like YouTube (I mean, fuck Google), you could upload the songs yourself to the Fediverse alternative. It's still you, but it's another layer of bullshit they have to go through to do something about it.