Answer:[/b][/color] Regarding the linked, no wallet can prevent users from consolidating coins if they want to. In Wasabi Wallet 1.0 users see a big warning when they try to spend private and non-private coins together. If they want to do it anyway, we should allow it. In 2.0 they see who knows about the transaction they are making but we should add more warnings. Creating a separate wallet for private coins doesn’t help as the user can still consolidate outside the wallet and it’s a very bad UX if sending all coins is urgent. Wasabi Wallet coinjoins are designed to be very large to make sure that even if many users consolidate, you’ll still have plenty of ambiguity from non-consolidated outputs. Deanonymization is a problem in smaller coinjoins with very few participants and low remix rate. Especially if users by default send the server their xpubs, like in Samourai Wallet.
What are these post-mixing tools exactly? Ricochet is very expensive and doesn’t provide you any privacy. 6 hops between cj and exchange is something you can do manually with 10x lower price if you think that helps. Or do you mean small coinjoins after the main coinjoin that is supposed to make sure even the people who leak xpubs can get a little bit privacy from the service provider? Otherwise it’s just a crappy coinjoin.
Wait, they think that "post-mix tools" is an invention of Samourai Wallet's devs? Or that, if the question like this is raised during discussions, it necessarily comes from Samourai's sockpuppet? Otherwise, why do they behave childishly attacking other developers instead of giving a clear answer to a justified question?
Yes, a privacy-oriented wallet with in-built CoinJoin functionality
must do everything it can to prevent users from consolidating mixed outputs with unmixed change. And yes, advanced users will always find a way to merge privacy coins with toxic change, but who cares if your target audience is newbies who aren't even allowed to coin-control the coins they control (what a wordplay, huh)? And if they are your main audience, then you must protect them first, not advanced users.