For the record, any license that does not allow users to do that would NOT be a free software license.
For the record, any license that does not allow users to do that would NOT be a free software license.
The problem is that:
1. BSD-4-clause included an advertising clause and that was considered burdensome (similarly, GFDL-with-invariant-clauses is forbidden by e.g. Debian), so the attribution only has to remain somewhere.
2. Embedded-in-an-archive links probably don't count much for SEO. Some aspects of GPL and/or AGPL can help in some circumstances ("appropriate legal notices"), but automated AGPL requirement satisfaction in the presence of forks can actually be pretty tricky to implement even among good actors.
3. even though it's illegal, stripping of license headers remains very common
“Open source” means something too. The control people have is in using shared definitions.
Language is malleable, so if enough people use a word incorrectly it changes the definition. But those people get to be called wrong for years until enough people misuse it to make it right.
IMO, MIT & BSD give downstream developers more rights and are indifferent to end-users. GPL gives users more rights, and indifferent to downstream developers.
Is MIT not free because it requires attribution? Is no code free because it cannot be used in ways that break the law?
Just because there are some restrictions does not make it completely unfree, and its fair for people to want to use what is the most natural word to refer to thing that are free enough for them. "OSI-approved" works if you want to be precise but one org does not have the right to dictate the use of a word as common as "open".
I don’t think there’s a true, single definition, but I think maybe the closest to that would be https://en.wikipedia.org/wiki/The_Free_Software_Definition