I'm trying to put a thing that happens on the last weekday on or before the 15th of each month. E.g., if the 15th is a Sunday, this thing falls on Friday the 13th.
This is surprisingly hard to model in my calendar app
=> More informations about this toot | More toots from zcutlip@hachyderm.io
@zcutlip Worst case scenario is that if it's Monday the 15th, then the day in question would be Friday the 12th, which implies setting a reminder on the 12th recurring will give you enough advance notice "hey do the thing"
Alternatively there are only 12 of these and manually making them for a year would take you 15-20 minutes tops and then you're good for a year
=> More informations about this toot | More toots from mikeymikey@hachyderm.io
@mikeymikey oh yeah for sure. I ended up just putting it on the 15th because it's not critical
Just thought it was interesting! Haven't encountered this edge case before
There is a “last weekday of the month" for the second of two semi-monthly occurrences. But no equivalent for the mid-month occurrence
=> More informations about this toot | More toots from zcutlip@hachyderm.io
@mikeymikey it also got me to thinking that this sort of schedule modeling must account for interoperability between apps
So even if BusyCal could represent some oddball schedule, that's not helpful if Calendar.app or some other app can't also represent it. So there must be some sort of protocol/specification for describing these repeating schedules?
=> More informations about this toot | More toots from zcutlip@hachyderm.io
@zcutlip I believe there's limitations in the ics / RFC2445 standard for representing repeating events that probably isn't flexible enough for those kind of relative dates - but even then it feels like you could fake it with a year+ worth of precalculated dates
=> More informations about this toot | More toots from mikeymikey@hachyderm.io This content has been proxied by September (ba2dc).Proxy Information
text/gemini