@sorenpeter (#qvykv7a) What did you change it to? You **must** use RFC 3339

@sorenpeter @prologic (#qvykv7a) changed the suffix from +00:00 to Z

@sorenpeter @darch (#qvykv7a) Is that still RFC 3339 compliant? I’m not at my computer to check 🤔

@prologic (#qvykv7a) it seem to work just fine for the most part. for refernce

(#qvykv7a) @prologic @sorenpeter Z is for zero, so it just another way of saying +00:00. i makes thes txtxt.txt more readable in the raw

(#qvykv7a) 👍

@darch (#qvykv7a) The “Z” is fine, but date and time really have to be separated by a “T”, IIUC. 🙂 That one twt on is broken, IMO.

(#qvykv7a) @vain I read somewhere that you could use a space instead of the "T" as still comply with RFC 3339. But I put the "T" back after testing it and found that it did not work with twtxt.net ;)

@sorenpeter @prologic @darch @vain (#qvykv7a) The "Z" is even required over "+00:00" according to our Twt Hash Extension Specification. The ABNF for RFC 3339 states, that "T" has to be used. But the second note below can be interpreted such that RFC 3339 also permits a space. Up until now I always read this as they refer to ISO 8601 with the space rather than RFC 3339.

@sorenpeter @prologic @darch @vain (#qvykv7a) Well, "Z" vs. "+00:00" only matters for the twt hash, not the timestamp of the twt.