I finally found a workaround for my issue with #NextCloud calendars. #VDirSyncer is the answer.
We share calendars with my fiancée to see each other's program but also invite each other to events that we want the other to attend.
NextCloud sadly has event ids unique across all calendars, thus this use case creates many id collisions between calendars.
When Vdirsyncer copies events from ics to caldav it does not use event ids, but creates own hash id from event content.
github.com/nextcloud/calendar/…
Same event in multiple calendars · Issue #5277 · nextcloud/calendar
Is your feature request related to a problem? Please describe. I recently migrated from Google calendar and I am used to this setup: I have imported my girlfirend's web calendar and then I have my ...GitHub
This entry was edited (10 months ago)
Štěpán Škorpil
in reply to Štěpán Škorpil • • •At the end the workaround didn't work well, because #Nextcloud was sending invitations from synchronized events and that is not wanted.
I ended up writing my own little #iCal #middleware that fetches the original #ics export and republishes it with all event UIDs postfixed by a constant string.
This ensures that fiancée's calendar event UIDs don't collide with received invitations to the same events and I can add them to my own calendar.
github.com/Stopka/icsmw
GitHub - Stopka/icsmw: ICal middleware
GitHub