All of these issues should be filed with one or both of the projects involved. If both close them as "not a bug" because they can't agree on a standard, then yes, making public that A doesn't play well with B might help to find better standards or discuss more publicly who's at fault. If 90% side with client B, maybe A reconsiders but that could happen on nostr social instead of a GitHub issue tracker.

Great idea. Clients should play nicely together so that we all have the best experience possible and can communicate as expected with one another across the ecosystem.

nostr:nevent1qqswrfczlaapj2knrnlh97x3lct0f35g63lsfahpfs7tq5hzvs7wktqpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqvhpsfmr23gwhv795lgjc8uw0v44z3pe4sg2vlh08k0an3wx3cj9qvzqqqqqqynjk7qh

Saving this for later! I'm considering building a simple Nostr client using Flutter and this might come in handy! 🙌