We're not breaking ground on AI innovation (in fact, we're using an old, "deprecated" file format from a whole six months ago)
The ggml format isn't "deprecated" it's completely dead. In those 6 months we've also seen 2-4x speedups on some systems, not to mention improved accuracy via kquants. I don't know why they would build out a new extension with such an ancient dependency.
This has been known for a long time. The main point of contention now will be who is liable for infringing outputs. The convenient answer would be to put the responsibility on the users, who would then have to avoid sharing/profiting from infringing images. In my opinion this solution can only apply in cases where the model is being run by the end user.
When a model is served online, locked behind a subscription or api fee, the service provider is potentially selling infringing works straight to the user. Section 230 will likely play a role, but even then there will be issues in the cases where a model outputs protected characters without an explicit request.