raspberryhead

Update, ran on a fresh calendar today after uninstalling for the rest of the day yesterday to hopefully skirt rate limitations. First run ran beautifully, finishes in 919 seconds. Second...

Weirdly enough, the link wont even run through the sanitizer. Here's the link we're using (generated by a software called MLSchedules) https://il27.mlschedules.com/iCalendar.ashx?subscriptionId=c4a00900-6a11-43a1-bfcc-6772fbbec1e7

I think that would work! How would I go about doing that? Would another solution be to ask them to use persistent event id's? I appreciate your replies.

This resolved our issues without even using `limitSyncRange`. We might turn that on just incase though. Thank you! However, i've been still using `onlyFutureEvents`. If that is set to false...

> The following event is causing the error > > ``` > BEGIN:VEVENT > DTSTART:20211210T192500Z > DTEND:20211210T090500Z > DTSTAMP:20211123T171700Z > SEQUENCE:0 > STATUS:CONFIRMED > SUMMARY:xxx > LOCATION:xxx > DESCRIPTION:xxx >...

confirmed on real m8 hardware as well