HELP NEEDED: Infomaniak kDrive backend

Good afternoon. For the last couple of days, I have been developing a Python-based backend for interfacing with the Infomaniak kDrive public API because I would like to include it into rclone. However, I am not a GO developer, and was wondering if anyone would be willing to port my Python implementation into GO so that we can include it as a new rclone backend (the Python backend is fully functional already).

If anyone is interested, please send me a DM.

Don't they support WebDAV already?

Yes, but WebDAV is not available in all plans. If you pay for myksuite+, you get access to a very good deal (1TB + unlimited mail storage for like 2€) but not to WebDAV, so no rclone (of course, no WebDAV in the Free tier either). To get access to WebDAV, you need to pay one of the pricier plans (kDrive Solo or kSuite Pro).

1 Like

I assume you mean my kSuite – The ethical solution to protect your personal data ?

Pricing looks attractive and they do publish an API unlike Proton but is it worth considering whether Infomaniak would be OK with this and how API credentials would be managed? The Proton API can be reverse engineered from their SDK but Proton have repeatedly said that they are hostile to an Rclone connector. If Infomaniak decide to add remote mounting to there own .appimage package (which I don't think it currently does but it does do sync.) then Rclone functionality might be harder to justify. They can say if you want S3 or WebDAV just use our object storage product in the same way iDrive (which no longer has a WebDAV interface but does have Linux sync client which does not mount remotes) and iDrive e2 does.

Just something to think about before you sink a lot of time in.

1 Like

In general, Infomaniak is very friendly to community/open source driven projects. They have a lot of documentation on how to use third party apps for their services (email, calendar, webdav, etc), so I don't think they would have a problem with it. Also, their API is publicly documented and VERY easy to use, so I do believe this would be a very interesting addition to RClone. My main drive towards implementing this is using crypt without the need for WebDAV. Besides, I have a fully working implementation of the API already; I just need to pprt it to GO :slight_smile: