Uncle Jim sovereign selfhoster Privacy/Physics/C++/#Bitcoin 8BETLojm7zCfGV8DKKiRWLAXrFGbkZxDAgzpGmkrDvafTB18QFUg9cQ1KKDtcECrekV14yZDdGEEQbGy8ShXq1pDBVAh2Hw
sommerfeld @sommerfeld - 5h
It's obviously a bug, but let's not overblow it. It has limited impact and can easily be mitigated by setting a loopback or null DNS server in the "blocking" state. I also don't trust devices and apps to use my preferred DNS servers. This is why I route all traffic to port 53 (plain DNS), 853 (DoT) to my own DNS server. The only thing that escapes the net is DoH which would require manually blocking a list of common DoH IPs, which I never bothered to do... nostr:nevent1qvzqqqqqqypzp50ncutrnt3mhgtll3kgm6clmva9v5rtxjfzz0grx55vc2g4ydcyqy2hwumn8ghj7mn0wd68ytn00p68ytnyv4mz7qpqa5q7rpqxa5ydfmy9y08jyuh9tlf5l8krnm8wvc48vu0fnncemamspr2gk7
sommerfeld @sommerfeld - 7h
This level of cope is just sad. I'm paid to code in #cpp and even I admit it's not even a fair fight. Cpp will keep being used... to maintain existing complex software. nostr:nevent1qqswn3rq52s0ktmcuuje0qglq0r0cvywdj2d02en269gzke6n8xechgpgdmhxw309amkjmn9ve5kcar9wfkksutf0pu85mtw0fuxsundv96kvurwvecnxunddf3kcdn9dy6r26tex3skjerjdenhqumed9jzummwd9hkuq3qs9c53smfq925qx6fgkqgw8as2e99l2hmj32gz0hjjhe8q67fxdvsxpqqqqqqzmxq6yh
sommerfeld @sommerfeld - 8h
> Enjoy your day. but which one? 🤔😂
I'm sure my 15 real human followers there will miss me
sommerfeld @sommerfeld - 11h
What are some prominent and interesting bluesky accounts to follow?
Open platforms is how we win, regardless of what shape and form they take.
You're barking the wrong tree here. If you ask on twitter, you'll get bombarded by the ossify and filteroors crowd.
This is great news
I run a SMP relay, haven't updated it in some months. Should I?
sommerfeld @sommerfeld - 12h
Hi FBI
sommerfeld @sommerfeld - 22h
I saw it from rabble. I tried it, it's still very minimal and unpolished but I definitely see the use case.
sommerfeld @sommerfeld - 23h
Communication layer is not exactly the issue thus far. Real problems are architectural
Bullish on geese
> That can be correlated to say that 5 UTXOs lack common ownership with each other. That's still not very useful information to have. It's not exactly a secret that it's a zerolink coinjoin. I dont think chain analysis knowing that they might have common ownership would make it that much better.
You're right, that's definitely a possible attack vector (besides a malicious coordinator, who can just do that by only paying miner fees). I never thought of that. But still don't understand how allowing more than 1 utxo being remixed per client would sove it... Sounds like it would just make it easier to attack
sommerfeld @sommerfeld - 24h
I don't understand how that can be correlated. Also, if you were able to have more than 1 input in a mix, you might be ably to sybil it an unmix it.
Would be cool to see but my point would remain valid 😉
It might resurect, some people have the code saved up and are looking at the best way to redeploy without getting arrested. We'll see
Wait for something better to come along and if you need to spend privately, use monero.
Do you really think a privacy upgrade is coming to bitcoin-core when most (or all?🤔) core devs use their real names? We need a culture shift
