<oembed><type>rich</type><version>1.0</version><title>mambru wrote</title><author_name>mambru (npub12m…h0ysr)</author_name><author_url>https://yabu.me/npub12mdvv7amnzl0mfl58umk0cm0c3l0tj2tl7f276fjy3s24tnnygdqeh0ysr</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-November/022152.html&#xA;Interesting comment by Peter Todd when discussing the possible use of nostr as a new protocol for the bitcoin-dev mailing list. His comments are not particular to that usage though:&#xA;&#xA;&#34;&#xA;Strong NACK on nostr. It&#39;s a badly designed, centralized, protocol that needs a&#xA;significant redesign to be usable. While off topic for this mailing list, some&#xA;of its many issues include:&#xA;&#xA;* Reliance on single-key, cryptography that often results in people having&#xA;  their keys compromised. This is a serious problem in the context of&#xA;  bitcoin-dev, where faked messages published could easily have market-moving&#xA;  results.&#xA;&#xA;* Inability to mirror relays: since nostr deliberately ignores the lessons of&#xA;  blockchains, there is no way to be sure that you have a complete set of&#xA;  messages from a given person, for a given topic, etc.&#xA;&#xA;* Highly centralized design: since mirroring relays isn&#39;t reliable, in reality&#xA;  nostr operates in a highly centralized fashion, dependent on a tiny number of&#xA;  relays that can&#39;t be easily replaced if taken down.&#xA;&#34;&#xA;He was replying to this proposal by nostr:npub19jescdjr3wk552j3q77f3awwhe4qy2ds24xce773exd28nr7emqsm2pt7r (I believe).&#xA;&#xA;&#xA;nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6  nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft  nostr:npub1qqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqt0n47m nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx </html></oembed>