Make workarounds for servers that does not support sync_token properly

[nevermind19]

Good evening,
I tried the library with nextcloud, all works good for create ,modify ,search data into nextcloud. I have some trouble with sync_token.. when i used the function objects_by_sync_token(sync_token, load_objects=True) after i did some change into nextcloud (for example move a meet and cancel another)
the server answer with error 418 i'm teapot ..i not understand if i wrong something ....

I also tried to do the same things but only with modify some meetings,without cancel and all was good and the function works ,and returns me all my changes correctly...
It seems likes the problem Is with delete records,Someone know why?

Thanks

[tobixen]

Known server-side issue. At least, it's an issue known by me ... I guess I never bothered to check up if it's known by the nextcloud developers.

[tobixen]

This issue should be addressed with Nextcloud, since this is a bug with Nextcloud.

That said, there are many servers having issues with sync tokens. I do have some plans to address this at the client side by downloading the full calendar for servers that does not support sync-tokens properly. Yes, it will be slow. And I will fix #157 first.