#[aciccarello]aaronpk, Seeing as you're the person with the most examples, how would you differentiate a trip post from a travel post? The wiki talks about travel as only a future dated thing. The definition for trip is closer to what I would think of when I think "travel". Though I'm personally thinking about a collection of posts related to a trip.
#Loqi✈ travel is a post type about plans to change locations in the future, similar to an event post about a future event, and related to exercise posts that involve changing location https://indieweb.org/travel
#capjamesgaaronpk Recurring events on Meetable would be cool.
#aaronpkNope, recurring events are a failure mode for event websites
#aaronpkall but guaranteed to end up with lots of "phantom" events, after someone creates a recurring event and forgets to stop it after they give up on organizing it in the future
#aaronpkI'm happy to make it as easy as possible to duplicate events individually into the future tho
#GWGaaronpk: How about something for recurring events that still requires individually creating sessions? Something to tie together recurring instances of the same event?
#[contact898]at my job our recurring events stop every 3 to 6 months automatically unless they're manually prolonged, which avoids abuse of phantom events
k1 and jeremycherfas joined the channel
#aaronpk"better visualization" is a solution, what's the problem?
gRegor, benji, revi, hidjy[d], GWG, trwnh, erscheinung[d], IWDiscord, againstthefuture, Salt and lanodan joined the channel
#[KevinMarks]The interaction between recurring events and timezones is a good reason to make manually cloning them the correct interaction model
#[KevinMarks]There's a reasonably good chance that the event editor can validate their own timezone by eye, Meetable will translate to an absolute offset from UTC and everyone else will get a correct translation. Recurrent events in local timezones are hostages to fortune
#gRegorI've only used it a handful of times but the Clone Event in Meetable worked well for me
#[Joe_Crawford]Agree with not overautomating repetitive events. But a tool to "compare this with the last similar event, did I forget a field?" could be useful. Also: the extent to which computer professionals mistrust automation is the extent to which computers ought to be mistrusted.
jeremycherfas joined the channel
#aaronpk[Joe_Crawford]: doesn't the "clone event" feature solve that?
#[KevinMarks]One of my favourite date representation stories was when a friend of mine who was CIO at a big Co with multiple countries and systems led the project to deal with the US changing the DST transition date. She went through all their systems with all their teams, and was fairly comfortable it was all going to work, but just in case, she scheduled a meeting with eng leads that spanned the DST change in all US time zones so they could watch
#[KevinMarks]it roll through and know if further patches were needed
#[KevinMarks]Microsoft Outlook refused to schedule that event.
#[Joe_Crawford]I've not used it, I did not know it was there [aaronpk] (and I was not complaining for any sort of change; I'm glad to know it exists, thanks for that!)
#[Joe_Crawford]Having worked on night shifts for a number of years in hospitals I got paid a number of 13 hour nights (loved that hour of OT pay) and 11 hour nights because of DST transitions. Always fun to "fall back" on recorded mechanical ventilator data on paper and note that *this* block of times was before the time change, and this after, even though they are the same numeric time.
[campegg] and [benatwork] joined the channel
#aaronpksounds like the button isn't discoverable enough then, i will think about that
#gRegorCould maybe move the "Edit" button in the drop-down menu that's just an arrow currently, then label that menu "Event Settings"