hey folks
", "time": "2022-07-25T17:31:11Z"}, {"author": "Ujjwal Sharma", "text": "question: is the matrix bridge still operational for this meeting?
", "time": "2022-07-25T17:31:25Z"}, {"author": "Robert Stepanek", "text": "yes
", "time": "2022-07-25T17:31:41Z"}, {"author": "Carsten Bormann", "text": "Zulip is the flavor of the week
", "time": "2022-07-25T17:31:42Z"}, {"author": "Bron Gondwana", "text": "we're on zulip now
", "time": "2022-07-25T17:31:48Z"}, {"author": "Robert Stepanek", "text": "it is. can't see you own video, though (maybe that's just me)
", "time": "2022-07-25T17:32:16Z"}, {"author": "Robert Stepanek", "text": "s/own/on/
", "time": "2022-07-25T17:32:25Z"}, {"author": "Ujjwal Sharma", "text": "oh, I like matrix better :(
", "time": "2022-07-25T17:32:46Z"}, {"author": "Bron Gondwana", "text": "Robert: mostly you aren't streaming video unless you explicitly ask to
", "time": "2022-07-25T17:33:02Z"}, {"author": "Robert Stepanek", "text": "gotcha
", "time": "2022-07-25T17:33:11Z"}, {"author": "Ujjwal Sharma", "text": "wait, does that mean that XMPP isn't active either?
", "time": "2022-07-25T17:34:05Z"}, {"author": "Bron Gondwana", "text": "I think it's ALL bridged this time
", "time": "2022-07-25T17:34:19Z"}, {"author": "Jabber", "text": "cabo: It is
", "time": "2022-07-25T17:34:23Z"}, {"author": "Jabber", "text": "cabo: For the last time
", "time": "2022-07-25T17:34:27Z"}, {"author": "Jabber", "text": "ryzokuken: ah nice, hello from XMPP
", "time": "2022-07-25T17:35:14Z"}, {"author": "Ujjwal Sharma", "text": "Common Locale Data Repository
", "time": "2022-07-25T17:39:07Z"}, {"author": "Carsten Bormann", "text": "4.3. Unknown Local Offset Convention
\nIf the time in UTC is known, but the offset to local time is unknown,
\n this can be represented with an offset of \"-00:00\". This differs
\n semantically from an offset of \"Z\" or \"+00:00\", which imply that UTC
\n is the preferred reference point for the specified time. RFC2822
\n [IMAIL-UPDATE] describes a similar convention for email.
@Bron: as perhaps the most experienced implementer in the room, do you have any comments?
", "time": "2022-07-25T17:57:51Z"}, {"author": "Bron Gondwana", "text": "I want some examples
", "time": "2022-07-25T18:08:02Z"}, {"author": "Bron Gondwana", "text": "just to be 100% sure that I know what this means... certainly 'Z' means offsets may have been applied to make this time align to UTC
", "time": "2022-07-25T18:08:59Z"}, {"author": "Bron Gondwana", "text": "but it doesn't mean that \"I assert this time is associated with the GMT timezone\"
", "time": "2022-07-25T18:09:19Z"}, {"author": "Carsten Bormann", "text": "18:00Z[America/New York] is not a conflict, and is equivalent to 14:00-04:00[America/New York]
", "time": "2022-07-25T18:13:54Z"}, {"author": "Carsten Bormann", "text": "Z no longer does \"imply that UTC
\nis the preferred reference point for the specified time.\".
great, that's what I was checking that everyone agrees with!
", "time": "2022-07-25T18:17:15Z"}, {"author": "Bron Gondwana", "text": "you can always convert to UTC but still give the zone name
", "time": "2022-07-25T18:17:35Z"}, {"author": "Justin Grant", "text": "I agree with Bron's comment in chat and his later one live just now.
", "time": "2022-07-25T18:22:44Z"}, {"author": "Ujjwal Sharma", "text": "had been under the impression that this would be fixed once we get the liason relationship...
", "time": "2022-07-25T18:29:10Z"}, {"author": "Carsten Bormann", "text": "We have more fruitful relationships with IEEE
", "time": "2022-07-25T18:30:51Z"}, {"author": "Carsten Bormann", "text": "But ISO really is a hard nut
", "time": "2022-07-25T18:31:00Z"}, {"author": "Justin Grant", "text": "Thanks everyone!
", "time": "2022-07-25T18:31:24Z"}, {"author": "Ujjwal Sharma", "text": "Thanks!
", "time": "2022-07-25T18:31:26Z"}]