On 02/02/2015 03:47 PM, vv01f 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.
Pavol's suggestion saves 2 chars only because its just a date. I think the creation date should be at least precise to the hour, if not to the minute. But anyhow, if everyone prefers a human readble date format I will bow to the majority. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
