this post was submitted on 20 Nov 2023
1380 points (99.9% liked)
196
17473 readers
670 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts are not allowed
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
meh, I prefer RFC 3339
In case people need a nudge to convert:
https://ijmacd.github.io/rfc3339-iso8601/
tbh they both have way too many options.
just give me 2023-11-21T21:45:53.02Z and call it a day
Damn, y'all are nerds.
what do you expect on lemmy
Is it just me or do neither ISO8601 nor RFC3339 contain any timestamp formats that are windows file system compliant? There doesn't seem to be a time format that doesn't contain a colon.
I think you're right, but also windows file system is a dumpster fire