@lyse@lyse.isobeef.org it hasn’t happened yet. It is this coming Saturday.
@bender@twtxt.net Ohhh! Well, this Sunday is even more unlikely as I’m probably helping a mate in the woods. But maybe we’re quicker than I think.
@lyse@lyse.isobeef.org but it is Saturday… 🤣🤣🤣
@bender@twtxt.net There’s a reason it’s in UTC time 🤣
@bender@twtxt.net @prologic@twtxt.net I got confused again, but luckily, the 2nd November 2025 at noon UTC is right on a Sunday in my timezone. :-)
@lyse@lyse.isobeef.org then I blame @prologic@twtxt.net, and no one else. LOL. But yeah, it is Saturday around 08:00 my time (EDT).
@lyse@lyse.isobeef.org So you’ve RSVP’d then? 🤣
@bender@twtxt.net Hm, are we talking about different dates or are there different timezone offsets for this timezone abbreviation? With EDT being UTC-4, 2025-11-02T12:00:00Z is Sunday at 8:00 in the morning local time for you. Or were did I mess up here? :-?
@prologic@twtxt.net You want me to submit a reply with “I probably won’t show up”?
@lyse@lyse.isobeef.org maybe @prologic@twtxt.net managed to mess things up—we should be used to this already, right? LOL—as the meets are always on Saturdays, as early as 06:00 EDT, or whereabouts, never on a Sunday.
You want me to submit a reply with “I probably won’t show up”?
I LOLed IRL! 🤣
@lyse@lyse.isobeef.org back to this, I think @prologic@twtxt.net meant 1 November 12:00 UTC. I won’t hold it against him. 🤭
@bender@twtxt.net LOL 😂 Timezonea are hard 😆
@bender@twtxt.net @prologic@twtxt.net Let’s see on which day we’ll finally settle.
I reckon the white-space: nowrap is a bit evil on the gatherly notes, though.