mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-25 19:15:48 +03:00
[GH-ISSUE #294] EteSync support #288
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#288
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tasn on GitHub (Nov 2, 2020).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/294
Hey,
EteSync is a fully open source, and end-to-end encrypted sync for your contacts, calendars, and tasks. It's available on all platforms, and is supported by both GNOME and KDE (starting from the next release), and soon Thunderbird. It's an open protocol, and you can think of it as an end-to-end encrypted DAV.
More than a few of our users use your great project with EteSync using our DAV adapter layer, and I thought it would be great if there could be built-in support. There is a cross-platform C library and documentation is available at https://docs.etebase.com
It's very similar to DAV in many ways, and should be very easy to integrate if your codebase supports a different backend.
Would love to hear your thoughts!
Thanks again for this project!
--
Tom (lead dev of EteSync)
@aluxnimm commented on GitHub (Nov 5, 2020):
Interesting project, thanks for the info.
What would be the benefit of an integration instead of using the layer described in https://github.com/etesync/etesync-dav/blob/master/win10-instructions.md
And we would need a C# library to natively support it.
@tasn commented on GitHub (Nov 5, 2020):
Thanks for getting back to me. The layer described there is run locally by every user, so using it means every user needs to install both Outlook CalDav Synchronizer and the etesync-dav daemon, which is cumbersome.
C# library: I'm new to the C# world, but wouldn't a C library (DLL + header) suffice using FFI? We can take a look into creating an C# API, though we lack your expertise when it comes to C#, so what we end up creating may be awkward to use.
@tasn commented on GitHub (Jan 1, 2021):
@aluxnimm, the first version of the Etebase C# bindings (around the Etebase C library) is now out: https://github.com/etesync/etebase-csharp/releases/tag/v0.1.0