Zuckerberg 'personally authorized' Meta's copyright infringement, publishers say

Discussion (10 Comments)Read Original on HackerNews

modeless•12 minutes ago

Funny how people are suddenly on Elsevier's side. It's clear to me that AI training is transformative fair use under existing law. Maybe this will be the case to prove it.

zx8080•22 minutes ago

Can someone explain why are we reading this instead of "Meta was fined for copyright infrigement" news?

solid_fuel•18 minutes ago

In 2024, voters signaled that they don't care about corruption when they reelected the most corrupt administration in American history. Since then, there has been a widespread understanding that the rich will not face consequences in this country. For example, take a look at the Trump administration's suppression of the Epstein files. Or the Trump families cryptocurrency schemes. Or the ridiculous ballroom.

Anyway, the point is - there will be no justice until the citizens of the united states demand it.

nomel•38 minutes ago

Title was changed. Now it's:

> Mark Zuckerberg ‘personally authorized’ Meta’s copyright infringement, *publishers allege*

gnabgib•about 3 hours ago

Discussion (139 points, 85 comments) https://news.ycombinator.com/item?id=48026207

nomel•38 minutes ago

Can't access that one with an ad blocker.

bawolff•31 minutes ago

Does it matter? The company's liability would (i assume) not change if the ceo authorized it or some other high level figure authorized it.

The question to answer is, did it happen and if so is this copyright infringement (not covered by fair use), not which company official authorized it.

palata•14 minutes ago

Too rich to care.

Der_Einzige•about 1 hour ago

Good.

ghstinda•33 minutes ago

this dude got in over his head with the evil empire, it is interesting how he learned judo and tried to surf, that being said I despise social media and what it did to society

Zuckerberg 'personally authorized' Meta's copyright infringement, publishers say

⚡ Community Insights

Discussion (10 Comments)Read Original on HackerNews