I mean, you could stop saying it right now, since it is not. There is no single coordinator run by a company or nothing like that, and it's also a protocol ya know, sandwich made a client, now cloud is making his own, all of them interoperable, no obligatory coordinator anywhere. But yea, hardening and federation are important points and they are already in the works. And yea, concord so far inverts the nip-17 expectations, specifically this point

GitHub

nips/17.md at master · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

. If you guys change that part of the spec I will shut up, but so far I think you still using the pubkey of the channel as author. So relays need to choose, be compliant with nip-17 or concord. I buy that is not at hard measure and any plain relay will work, thats why I said 'work as expected' in my comment, not just that doesn't work in regular relays.