Objectively speaking, if zkSNACKS' coordinator did not hire the services of a blockchain analysis company, would Wasabi be in that list?

Wasabi has been reusing addresses, a lot, which has resulted in a lot of post-mix coins being linked back to pre-mix coins and being de-anonymized. And then the devs have been on Twitter, both defending that it is "acceptable" and also lying about it entirely.

Here's an example thread: https://nitter.it/HillebrandMax/status/1586249382097088512#m
Gets shown address reuse, claims it isn't from 2.0 and that it has never happened in 2.0. Then gets shown address reuse from 2.0, and says they've already patched it. How could they have patched it while also claiming it has never happened? They are lying somewhere.

Here's another example: https://nitter.it/ErgoBTC/status/1585671294783311872#m
And dozens more: https://nitter.it/wasabistats

But the devs don't care, because apparently some address reuse is "acceptable": https://nitter.it/HillebrandMax/status/1586321068129939456#m

Wasabi coinjoins creating outputs which can be 100% linked to a specific input: https://mempool.space/tx/dae13b2d015587a3033d7ab7949a7efa6d6ed7aa782168b0651ab37a2d8390f8
Wasabi coinjoins reusing addresses, leading to users being doxxed: https://nitter.it/ErgoBTC/status/1585671294783311872
Wasabi coinjoins using the same address on both sides of a transaction: https://mempool.space/tx/af50a27691c0f0b7b626cddb74445a0e26bb6ed7b045861067326ea173bc17d0 (address bc1qft2uze947wtdvvhdqtx00c8el954y6ekxjk73h)

Because it would be unfair not to include Wasabi if they're app is technically doing what it's supposed to - and doing it well - to increase user-privacy and help preserve fungibility.