devycarol
commented
1 year ago I, too, would appreciate this. This is how this sort of data should be stored. Having a more conventional, standard save format option will greatly improve compatibility, removing the need to run a background CalDAV spoof or third-party plugin in order to share calendar data with a client that already supports ICS files/directories for calendar storage.
Having a human readable .ics and .vcf in addition to the existing files that decsync uses would be hugely helpful to users. Please consider an option to include a .ics and a .vcf file in addition to the existing files in the decsync folder.
My use case for this is : I wanted to do a little scripting with the data in my calendar events. Manually Exporting events to .ics file from my calendar app is not an option since the script is supposed to run daily, and I don't want to export manually daily. So because decsync data is not human readable what I ended up doing is syncing decsync folder to my Linux pc via syncthing then using evolution plugin to make evolution read that data and then using the .ics generated by evolution in its data directory for doing the scripting. (PS. If anyone thinks there is better way to do this, then please let me know!)