<oembed><type>rich</type><version>1.0</version><author_name>npub1t9txg5aevth45pu9hcz075tj3ch25fydn8c38wew90qjjdjv3rqq3r6cf0</author_name><author_url>https://nostr.ae/npub1t9txg5aevth45pu9hcz075tj3ch25fydn8c38wew90qjjdjv3rqq3r6cf0</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-04-04&#xA;📝 Original message:Matt Whitlock wrote:&#xA;&gt; The creation date in your BIP header has the wrong format. It should be 01-04-2014, per BIP 1.&#xA;&gt;&#xA;At first, I thought this was a second April Fool&#39;s joke, but then I &#xA;looked and saw that all of the BIPs really do use this format.  As far &#xA;as I can tell, we are using this insane format because RFC 822 predates &#xA;ISO 8601 by half a decade.&#xA;&#xA;Since we don&#39;t have half a gajillion mail servers to patch, we could, if &#xA;we desired, adopt a sensible date format here.  The cost to the &#xA;community would be minimal, with probably not more than a half dozen &#xA;people needing to update scripts.  It could even be as simple as one guy &#xA;running sed s/parseabomination/parsedate/g</html></oembed>