I still think label based communities are a better model than nip-72

#asknostr Hey @npub1vadc...nuu7 I figure you're the guy to ask here. If I'm building a coinjoin but want to *consolidate* two outputs from separate participants which are going to the same recipient, how can all participants validate that their coins are accounted for in the outputs *without* sharing their destinations and amounts with all other participants? I assume this is possible, but I'm struggling to construct it. ex A sending 1BTC to D B sending 1BTC to E C sending 2BTC to D Ideally, the outputs would be 3BTC to D 1BTC to E But how can participants differentiate that from 2BTC to D 1BTC to E 1BTC to F (without knowing the destinations of each participant's coins, ruining all unlinkability) I've had a few ideas, but I've run into a brick wall every time. Blinded addition seems not to be useful, since you need to first prove you have contributed enough in inputs which seems to necessitate linking your blinded value to the inputs, ahead of time, negating the value of blinded addition? I hope I'm missing something obvious (or even a paper doing exactly this?)

Refreshed coracle and it is just loading a blank page now on Chromium Desktop. ``` Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'attribution-reporting'. Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'run-ad-auction'. Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'join-ad-interest-group'. Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'browsing-topics'. ``` Followed by lots of errors related to bugsnag logged in the console, and an error posting to dufflepud.onrender.com

Wtf is kind 9802?!

I just misread "coracle" as "whoracle". I guess I know what I'm listening to this afternoon...

@npub1jlrs...ynqn What's going on when I upload media using coracle? I got a prompt from nos2x about signing a "POST" message. What nip is that? (Also kind of amusing that we're now re-implementing HTTP request/response methods inside websockets lol)