▲ 659 ▼ The perfect date (lemmy.world) submitted 6 days ago by PopcornPrincess@lemmy.world to c/lemmyshitpost@lemmy.world 239 comments fedilink hide all child comments
[–] 7EP6vuI@feddit.org 200 points 6 days ago (7 children) ISO 8601 YYYY-MM-DD permalink fedilink source parent hideshow 14 child comments replies: [–] jlow@slrpnk.net 46 points 6 days ago 👆 permalink fedilink source parent [–] GreyEyedGhost@piefed.ca 16 points 5 days ago (2 children) RFC 3339 FTW! Open source, and no ambiguous options grandfathered in. permalink fedilink source parent hideshow 4 child comments replies: [–] bss03@infosec.pub 5 points 5 days ago Was looking for this. Yes. Whenever possible, dates should be specified in a format that is BOTH RFC 3339 and ISO 8601. I'd say both have their quirks, but the intersection of the grammars is machine-parseable and human-readable without (much) legacy baggage or (much) experimental / reserved-for-future-use noise. permalink fedilink source parent [–] The_Decryptor@aussie.zone 2 points 5 days ago Though the way it specifies raw UTC times is odd (8601 uses Z, 3339 uses -00:00), that got changed with RFC 9557 to align with 8601. It also supports "zoned date times", where instead of just using the UTC offset, you can also include a timezone identifier, e.g. 2020-01-01T00:00+01:00[Europe/Paris]. Useful if you're doing calculations on dates but can be ignored otherwise. permalink fedilink source parent [–] plasma8726@lemmy.today 13 points 6 days ago This is the only way to date. permalink fedilink source parent [–] Iusedtobeanalien@lemmy.world 3 points 5 days ago (1 child) No need for dashes permalink fedilink source parent hideshow 2 child comments replies: [–] sem@piefed.blahaj.zone 4 points 5 days ago Except for, yknow, human readability permalink fedilink source parent [–] CanadianCarl@sh.itjust.works 1 point 4 days ago ISO week date permalink fedilink source parent [–] bandwidthcrisis@lemmy.world 3 points 6 days ago I've recently noticed web forms and appointment emails start to use that format. Maybe web devs are sneaking it in bit by bit. permalink fedilink source parent [–] Nonononoki@lemmy.world 2 points 5 days ago Are a lots of things gonna break in about 8000 years? permalink fedilink source parent
[–] GreyEyedGhost@piefed.ca 16 points 5 days ago (2 children) RFC 3339 FTW! Open source, and no ambiguous options grandfathered in. permalink fedilink source parent hideshow 4 child comments replies: [–] bss03@infosec.pub 5 points 5 days ago Was looking for this. Yes. Whenever possible, dates should be specified in a format that is BOTH RFC 3339 and ISO 8601. I'd say both have their quirks, but the intersection of the grammars is machine-parseable and human-readable without (much) legacy baggage or (much) experimental / reserved-for-future-use noise. permalink fedilink source parent [–] The_Decryptor@aussie.zone 2 points 5 days ago Though the way it specifies raw UTC times is odd (8601 uses Z, 3339 uses -00:00), that got changed with RFC 9557 to align with 8601. It also supports "zoned date times", where instead of just using the UTC offset, you can also include a timezone identifier, e.g. 2020-01-01T00:00+01:00[Europe/Paris]. Useful if you're doing calculations on dates but can be ignored otherwise. permalink fedilink source parent
[–] bss03@infosec.pub 5 points 5 days ago Was looking for this. Yes. Whenever possible, dates should be specified in a format that is BOTH RFC 3339 and ISO 8601. I'd say both have their quirks, but the intersection of the grammars is machine-parseable and human-readable without (much) legacy baggage or (much) experimental / reserved-for-future-use noise. permalink fedilink source parent
[–] The_Decryptor@aussie.zone 2 points 5 days ago Though the way it specifies raw UTC times is odd (8601 uses Z, 3339 uses -00:00), that got changed with RFC 9557 to align with 8601. It also supports "zoned date times", where instead of just using the UTC offset, you can also include a timezone identifier, e.g. 2020-01-01T00:00+01:00[Europe/Paris]. Useful if you're doing calculations on dates but can be ignored otherwise. permalink fedilink source parent
[–] plasma8726@lemmy.today 13 points 6 days ago This is the only way to date. permalink fedilink source parent
[–] Iusedtobeanalien@lemmy.world 3 points 5 days ago (1 child) No need for dashes permalink fedilink source parent hideshow 2 child comments replies: [–] sem@piefed.blahaj.zone 4 points 5 days ago Except for, yknow, human readability permalink fedilink source parent
[–] sem@piefed.blahaj.zone 4 points 5 days ago Except for, yknow, human readability permalink fedilink source parent
[–] bandwidthcrisis@lemmy.world 3 points 6 days ago I've recently noticed web forms and appointment emails start to use that format. Maybe web devs are sneaking it in bit by bit. permalink fedilink source parent
[–] Nonononoki@lemmy.world 2 points 5 days ago Are a lots of things gonna break in about 8000 years? permalink fedilink source parent
