[SpaceNugget]

The part I was indicating was incorrect was your usage of "could" It's not something they "could" do, it's something they MUST do.

Like saying I choose to not be the richest person in the world. Sure it could be technically true, but the statement is incorrectly implying that it's up to me, or within my power to make the alternative choice.

It's very strange that you keep using these intentionally awkwardly phrased, misleading-adjacent statements.

The rest of your comment is attempting to refute something no one made a case for in the first place, which coupled with the rest of it makes it seem like you are just trying to argument-bait, so I'll tap out here.

[palata]

> It's not something they "could" do, it's something they MUST do.

Well, maybe I just can't English :-).

They must include the copyright notice and the permission notice. Now I can imagine different ways to achieve that. They could use one or the other, as long as what needs to be included is included.

Depending on how they do it (while staying in the realm of what they MUST do, i.e. include the copyright and permission notices), it gives more or less visibility do Spegel. My point was that linking to Spegel in the README arguably gives more visibility to Spegel than alternatives that they COULD choose. And to make it very very clear: what I consider alternatives that they COULD choose are those that honour the licence.