aeharding@vger.social to Ask Lemmy@lemmy.world · 4 months agoIf you could regulate something relatively inconsequential, what would it be?message-squaremessage-square140fedilinkarrow-up15arrow-down10file-text
arrow-up15arrow-down1message-squareIf you could regulate something relatively inconsequential, what would it be?aeharding@vger.social to Ask Lemmy@lemmy.world · 4 months agomessage-square140fedilinkfile-text
Fitted sheet must have label on bottom right seam Salted butter wrapping text must be red. Unsalted blue.
minus-squarejbk@discuss.tchncs.delinkfedilinkarrow-up3·4 months agoevery date MUST be in RFC 3339 format. e.g. 2024-09-08, with optionally the time: 21:41:24+02:00 and hell no not ISO 8601 cause then people would use stuff like 2024W154
minus-squarenabladabla@sopuli.xyzlinkfedilinkarrow-up1·4 months agoThank you! Also nobody wants to buy a copy of an ISO standard
minus-squareiknowitwheniseeit@lemmynsfw.comlinkfedilinkarrow-up2·4 months agoI think that ISO 8601 is available for free. But agreed that the RFC version is superior.
minus-squareEiri@lemmy.calinkfedilinkarrow-up1·4 months agoWould you allow long dates? For example, Jan. 11, 2022, or 7 September 2010.
minus-squarejbk@discuss.tchncs.delinkfedilinkarrow-up2·4 months agono, for cross-language interoperability. ok I just noticed that this breaks other calendar systems but well
every date MUST be in RFC 3339 format. e.g. 2024-09-08, with optionally the time: 21:41:24+02:00
and hell no not ISO 8601 cause then people would use stuff like 2024W154
Thank you! Also nobody wants to buy a copy of an ISO standard
I think that ISO 8601 is available for free. But agreed that the RFC version is superior.
Would you allow long dates?
For example, Jan. 11, 2022, or 7 September 2010.
no, for cross-language interoperability. ok I just noticed that this breaks other calendar systems but well