<oembed><type>rich</type><version>1.0</version><author_name>npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_name><author_url>https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-01-19&#xA;📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----&#xA;Hash: SHA256&#xA;&#xA;&#xA;&#xA;On 19 January 2015 12:09:13 GMT-07:00, Jeff Garzik &lt;jgarzik at bitpay.com&gt; wrote:&#xA;&gt;Text formats such as XML or JSON are far less deterministic, are more&#xA;&gt;loosely specified, have wide variance in parsing, are not very&#xA;&gt;hash-able,&#xA;&gt;the list goes on.&#xA;&#xA;Protocol buffers isn&#39;t any more hashable than XML or json - round trips aren&#39;t deterministic with standard protobuf libraries. To make it deterministic you end up creating a new standard.&#xA;&#xA;I have this problem for an asset representation standard for one of my clients, and I&#39;ve reluctantly had to roll my own format.&#xA;-----BEGIN PGP SIGNATURE-----&#xA;Version: APG v1.1.1&#xA;&#xA;iQFQBAEBCAA6BQJUvV+KMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8&#xA;cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhRwcCACNkpkkjIh8Zv5I8bOy&#xA;BpM2Tc5hVpg4KY6eKRXYLYgxoEnekDXN1/LJ5bfl+xzJTMTdt4f7YF0EjFJSIJ0C&#xA;UpR9KbEVShmt7UsoNwwAFxtMQmZe84vANGG11NI/cb95GO2TOlxYtPMFizQrp80s&#xA;ULAelID3Pd8yPeadU/yrF+daz9I8UHqOyioL0piWUT+kshuzqQNclHQaPKWoOPbW&#xA;XF4w1SAJjb1tHmkHqCY1HRvwlv8fqxXgjtEyjkz/HK70ZzOI+8aR49aigx2njwyL&#xA;F8EJ1gO3XkivRidTRKfbSloeq96TRneXXXfmyB6p8jI3O3BRkrk9x465EWMnzYu7&#xA;uJqo&#xA;=N1G+&#xA;-----END PGP SIGNATURE-----</html></oembed>