Oddbean new post about | logout
 name a better one 
 In order from best to worst:

Joinstr

Joinmarket

Wabisabi

And there are other non-coinjoin solutions such as Lightning that offer great privacy. 
 I can see why you'd rank like that, however if the only criteria would be privacy and nothing else, then the rank order would be reversed, wouldn't it? 
 If we are talking about privacy in chain, wabisabi from my point of view is the one that gives the best privacy, besides solving the problem of toxic change.

It would be great if in the desktop client you could pay through coinjoin without having to depend on BTCPay Server. 
 MIX@meetups  
 It seems they just put that into the RPC yesterday. Although I don't personally think it's a good idea. I think payments in coinjoins will always have bad UX unless a proper P2EP is implemented, and everything that doesn't bring towards making the average Bitcoin user use Bitcoin privately by default is a distraction. But anyway, I'm not there anymore and even when I was I wasn't able to keep the project on track and kill all the advanced feature requests so all I can do now is to bitch about it on nostr😅 

https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.3.0.0 
 Thanks for the info, I saw that it was included in the new version. 
 Mofos never used the wallet and it shows.

Back when Whirlpool was still spinning, every time you'd submit a UTXO for a premix/remix, your android Samourai client would display a message that a new tor identity has been claimed when submitting that output. 

Stop this unproductive FUD shit show, go touch the grass and enjoy your day.

Support the FOSS devs via p2prights.org

#FREESAMOURAI https://image.nostr.build/227a0d7d82adcca0c889f8935698dd36b05a130e8d3694d86ce82824c78cb6c8.jpg

nostr:nevent1qqsvy6tf55qwz4nm9ds5g7qgqptx8acqu8uturnd6nqcl3zy9wzvdfqpz4mhxue69uhkummnw3ezummcw3ezuer9wchsyg8u7u9ytnagzl42syaeh29rwht385ckna9z0u7u4s75jyfd7e7n0cpsgqqqqqqsrxvn35
nostr:nevent1qqsvy6tf55qwz4nm9ds5g7qgqptx8acqu8uturnd6nqcl3zy9wzvdfqpz4mhxue69uhkummnw3ezummcw3ezuer9wchsyg8u7u9ytnagzl42syaeh29rwht385ckna9z0u7u4s75jyfd7e7n0cpsgqqqqqqsrxvn35
nostr:nevent1qqs20987kdaut5dyjr3sdhrpnw9cuzdty59zl0lgvfc5fzgvaa3p53gpzpmhxue69uhkummnw3ezumt0d5hsyg8u7u9ytnagzl42syaeh29rwht385ckna9z0u7u4s75jyfd7e7n0cpsgqqqqqqs06qf6j 
 I am being transparent in my analysis, and assuming my mistakes, you are not and inventing nonsense.

You are ignorant and a danger to privacy.

To outline:

- Samourai Android does not manage tor identities.

- Sparrow has faulty management, so ultimately it does not manage tor identities either.

- the whirpool client manages the identities but reuses in the remix the input identity, therefore the outputs can be linked.

I will never understand the cult when privacy is at stake.

Accept that you have a flawed solution, you respond the same way you did when it was shown that you exposed the public key in your Android Wallet.