Post B5dRvirJAYuaxvYd9M by bob_zim@infosec.exchange
 (DIR) More posts by bob_zim@infosec.exchange
 (DIR) Post #B5dRviaeAVaI8FlKBE by kusuriya@masto.hackers.town
       0 likes, 0 repeats
       
       @nuintari @mwl there is only one true way YYYY-MM-DD... iso date format or bust
       
 (DIR) Post #B5dRvirJAYuaxvYd9M by bob_zim@infosec.exchange
       0 likes, 0 repeats
       
       @kusuriya @nuintari @mwl ISO 8601 costs money to read. RFC 3339 or bust!
       
 (DIR) Post #B5dRvj6YFt6ZjCgnuS by sirwumpus@tilde.zone
       0 likes, 0 repeats
       
       @bob_zim @kusuriya @nuintari @mwl There are ISO 8601 drafts or past versions easily found as PDFs.
       
 (DIR) Post #B5dRvjJfT7b4NspHM0 by bob_zim@infosec.exchange
       0 likes, 0 repeats
       
       @sirwumpus @kusuriya @nuintari @mwl Sure, but it’s free to read the current RFC 3339 directly from the authoritative source.
       
 (DIR) Post #B5dRvjSsuqyAqT8dii by sirwumpus@tilde.zone
       0 likes, 0 repeats
       
       @bob_zim @kusuriya @nuintari @mwl But the RFC is a subset as I recall .
       
 (DIR) Post #B5dRvjZyUUdnCSSIls by bob_zim@infosec.exchange
       0 likes, 1 repeats
       
       @sirwumpus @kusuriya @nuintari @mwl RFC 3339 covers the specific date and time format everybody means when they say “ISO 8601”: 2026-04-24 with optional time.ISO 8601 has that, but also formats used exclusively by the criminally insane, such as “R/2026-W17-5”.