[Aperocky]

> Since FFmpeg is gpl2.1 I thought they had to make it easier to know they're using this

Precisely, I doubt youtube just brazenly ignored this, but their legal might have buried it under some obscure link. I wonder if there's a license that require it to be "highly visible" in some sort of way.

[rchard2scout]

Isn't it that they're not actually distributing FFmpeg, just using it themself, so they don't need to do anything?

[komali2]

Huh, I never really thought about it, but I guess that's one thing that GPL kinda fails at: if your server does all the work, you can leverage open source technology to do all sorts of stuff for your clients, so long as all the work the code you serve them does is collect and present data to the server.

Like, they get to see the code they run, but there's no insight to the code you run to deliver whatever service you're doing. Maybe this is obvious to other people lol, I just hadn't thought of it till now.

[mpol]

Yes, this is the reason AGPL was created. With AGPL software you have to open your changes, even if you don't distribute it and only use it serverside. There are still nuances, but this is the main gist.

[pjc50]

This is known as "Tivoisation" (after a dead set top box company), and is the driving motivation behind GPLv3 and some other licenses adding terms to cover this.

[everslick]

Not really. Tivoisation is the process of locking your device down with hardware (or other means), so it will only run software signed with your keys.

So the end user can have all the source code they want and still be helpless.

That issue with the GPLv2 was fixed with V3.