Turn midnight-to-midnight events into all-day events

· v2.12.0

Not every calendar publishes all-day events properly. A good number of subscription links — conference schedules, school calendars, sports fixtures — describe a day off as a timed event that starts at midnight and ends at midnight the next day. It is technically the same span of time and it reads completely differently: instead of a quiet banner across the top of the day, you get a solid twenty-four hour block that buries everything else.

Keeper.sh can now recognise that shape and copy it as a genuine all-day event. It is a per-calendar setting rather than something applied everywhere, because the interpretation is a guess — a real event that happens to run midnight to midnight is rare, but it is not impossible, and the right answer depends on the calendar you are reading.

Turn it on for the subscription that keeps swallowing your week, and leave it off for the calendars that publish all-day events correctly to begin with.

Read more about everything Keeper.sh does.

New

  • An assistant can set an event's timezone, such as America/New_York, when it creates one.

Improved

  • A calendar that keeps failing to fetch backs off and retries, while its events still go out.

Fixed

  • A repeating event in your Keeper.sh feed expands properly instead of showing once.

  • A skipped date no longer drops the whole repeating series from your feed.

  • Events in your Keeper.sh feed show at their local time in Outlook, not in UTC.

  • Events that failed to write on every single sync now go through.

  • Events written to iCloud, Fastmail and other CalDAV calendars keep their own timezone.

  • Calendars that returned an error and never fetched any events now sync.

  • When a calendar link cannot be loaded, the events already synced from it are kept.

  • Calendar links that write dates in an unusual form now import.

  • A calendar your provider reports as missing is retried instead of being switched off.

  • An edit to an event's title, description or location reaches your other calendars.

  • A slow provider no longer freezes a sync part-way through.

  • An account wrongly flagged as needing reconnection keeps syncing.

Can Keeper.sh use cookies for analytics?