Mastodawn

We have received a Copyright claim from Amazon for our @peertube instance videos.trom.tf/ . Hetzner, the hosting company where we have the dedicated server at, gave us 24h to resolve it.

The problem?

The video in question, a documentary about "aliens", a garbage piece of content, was NOT hosted on our instance, of course. But since Peertube is federated the idiots sent the claim to our hosting company. Even if UNDER the video you can see that video is "Posted By:" and the instance and username. It takes a few seconds to see where the video is hosted.

But who cares...maybe Amazon has "AI Agents" employed and they simply find a video of theirs on a URL and see the IP of that URL and submit a Copyright claim to the hosting where that domain is registered?!

Bunch of idiots.

But it is very concerning the fact that they can do these and we, the ones who host (and for free for that matter), need to quickly "fix" these things even if the claim has nothing to do with our server.

We eventually had to block that URL, thanks Peertube for allowing that, else these idiots cannot understand that it was not us who were hosting that video.

#peertube #fedi #fediverse

videos.trom.tf

A trade-free video hosting platform for science/technology/nature videos in the English language. You do not have to trade your currency, data, attention, freedom or anything else, in order to use it.

videos.trom.tf

Show thread

FinchHaven sfba May 11

@trom

"The video in question, a documentary about "aliens", a garbage piece of content, was NOT hosted on our instance, of course"

As other have said (and may yet say) IANAL

*That said* there is a vast difference between "hosted on" and "served from"

Your instance may *not* be the sole source for that content, but if a video consumer *gets* it though you, guess what?

It doesn't matter what "makes sense"

This is law, and lawyer-speak

Good luck with it

cc @[email protected]

Show thread

TROM May 11

@FinchHaven It is ridiculous to act as if the content is "on your server" and you have to deal with it. If it is federated, go after the source. Else you swift the responsibility on the TV if one watches "pirated" content on "it".

Show thread

FinchHaven sfba May 11

@trom

What you "like" or "think should happen" is utterly irrelevant

And you clearly don't understand the usage of the word "Federated"

Which is super common around here

Being federated makes *every* federated instance the [a] source

There is no one single point source -- the sources are all federated into multi-point "sources"

Show thread

Rokosun

@FinchHaven @trom

The way Peertube federates is different from how Mastodon does its federation. As long as the video in question is not stored on your server and is just streamed from a different instance then that instance should be contacted for the removal - that's what any competent lawyer would do. But now what they've achieved is merely made us put up a curtain to hide the video from their view, a video that still exists on the original instance and free for anyone to watch.