📅 Original date posted:2015-02-02
📝 Original message:On 02.02.2015 15:17, Andreas Schildbach wrote:
>> Uff, I would expect YYYYMMDD there so it's human readable as well.
>
> Those strings are not meant to be read by humans. YYYYMMDD is more
> complicated than necessary, given that Bitcoin deals with seconds since
> epoch everywhere.
First that is a pitty .. as its simply a waste of storage.
but back to Pavol's point: IMHO no harm to anything, as Bitcoin never
has any valid timestamp below ~1230768000 (jan2009) and thus will always
have 10 digits.. you can easily identify 8 char long timestamp as the
proposed format.
And there never is anything wrong with having a transparent, human
readable option - especially when it saves 2 bytes in e.g. qr-codes.
vv01f [ARCHIVE] /
npub16w…ws45h
2023-06-07 15:29:25
in reply to nevent1q…l7ka
Author Public Key
npub16wxlvxa5c25gcawkfcf7v6w8ray5scwm8t8y0qkxpfr3h5c5j0aqhws45hPublished at
2023-06-07 15:29:25Event JSON
{
"id": "988554775dd2011c5d3f3431dce10c91a7308060da73fa43c804434abbdd94dd",
"pubkey": "d38df61bb4c2a88c75d64e13e669c71f494861db3ace4782c60a471bd31493fa",
"created_at": 1686151765,
"kind": 1,
"tags": [
[
"e",
"da5dfa7015ad7eb23fb699400b79b743db94aa85c8d6df42489b5ad471f64cea",
"",
"root"
],
[
"e",
"27b68ba8b66be2895bfdd32094919a67b57e7a5c44858892ba684dc71f1014be",
"",
"reply"
],
[
"p",
"3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc"
]
],
"content": "📅 Original date posted:2015-02-02\n📝 Original message:On 02.02.2015 15:17, Andreas Schildbach wrote:\n\u003e\u003e Uff, I would expect YYYYMMDD there so it's human readable as well.\n\u003e \n\u003e Those strings are not meant to be read by humans. YYYYMMDD is more\n\u003e complicated than necessary, given that Bitcoin deals with seconds since\n\u003e epoch everywhere.\n\nFirst that is a pitty .. as its simply a waste of storage.\n\nbut back to Pavol's point: IMHO no harm to anything, as Bitcoin never\nhas any valid timestamp below ~1230768000 (jan2009) and thus will always\nhave 10 digits.. you can easily identify 8 char long timestamp as the\nproposed format.\nAnd there never is anything wrong with having a transparent, human\nreadable option - especially when it saves 2 bytes in e.g. qr-codes.",
"sig": "af33acb7d6537871b97773af7bc20f39fd085166bc362ddc6e63f1689eca8e0aa77407e2828f49d47e4e9ba0deb0ba8e70985a6559de8255698572dbad01c56f"
}