Not if we get Dimon at Treasury. That would be worse than Mnuchin, probably, and definitely worse than Yellen.
I mean I’d call Oblivious-(DNS-over-)HTTP a VPN/proxy? People can do that if they want.
I’m already worn out from Nashville and I haven’t even gone there yet.
Meanwhile tons of bitcoiners are still frothing at the mouth for him after the news that he’s considering someone who hates Bitcoin for the role which impacts Bitcoin the most 🤦♂️
Then bitcoiners need to fundamentally change what they work on. Mining centralization is a joke, mints creating more custodial operations 🤦♂️…. People keep saying this but bitcoiners are not building like it’s true.
Ha, if this is true another Trump administration will be worse for Bitcoin than the current Biden one 🤦♂️ 
Ah, I missed the header/author, sorry! I don’t disagree with his conclusions, but my point was rather different :)
You might be surprised :)
A lot of people talk about “attacks on bitcoin”, but they’re usually just people doing something you don’t like. In rare cases, though, these things can have severe consequences for the entire Bitcoin system.
This is what an attack on Bitcoin looks like https://github.com/rollkit/rollkit/issues/761#issuecomment-2195853303
Have you ever taken a serious look at TLS/X.509/Certificate Authorities/DNS Poisoning/BGP Hijacking……..? :)
They is a political standards organization that is the successor to the people who invented http :)
They’re moaning about people having to make sure their site works with TLS? Seems like a weird complaint. My issue is that TLS is an overcomplicated beast of a protocol (okay somewhat better with 1.3, but even still), which is the enemy of security, we have like 100 “roots of trust” in the form of CAs, most of which have a long history of being terrible, it relies on too many pieces of an increasingly huge stack, etc….
DNS is so much less complexity/attack surface than HTTPS. HTTPS/TLS are terrible protocols that should be constrained to web browsers. nostr:note1rqz20lqj03r54k880tg4tw5hg3peyr8wy6lw7zm5xfwp62yznx5q58kqc7
The one good thing GDPR did was make almost all domain whois private by law.
Seems like a matter of adding nostr specific txt record?
cc nostr:npub185h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qcswrdp
Yea super trivial…
Get any domain, enable DNSSEC, add a Bitcoin: URI to username.user._bitcoin-payment.yourdomain in a TXT record. Done.
You can also now use https://satsto.me which should give reasonable error messages (currently says “The server indicated the records we needed were not DNSSEC-authenticated” for the example name you gave).