You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 5, 2026. It is now read-only.
We use github.com/henrybear327/go-proton-api in the Proton drive backend for rclone.
I've just discovered in rclone/rclone#7998 that the protondrive backend is adding over 3.5MiB to the rclone binary! That is nearly 5% of the binary size. Most backends weigh in at about 200k - it is only the ones with big external SDKs that exceed 1MB and the protondrive is the second biggest after storj.
I suspect that this package is pulling in more things than it needs to which are making its way into the rclone binary.
We use
github.com/henrybear327/go-proton-apiin the Proton drive backend for rclone.I've just discovered in rclone/rclone#7998 that the protondrive backend is adding over 3.5MiB to the rclone binary! That is nearly 5% of the binary size. Most backends weigh in at about 200k - it is only the ones with big external SDKs that exceed 1MB and the protondrive is the second biggest after storj.
I suspect that this package is pulling in more things than it needs to which are making its way into the rclone binary.
I used https://github.com/Zxilly/go-size-analyzer to examine the rclone binary and it wasn't obvious where the extra code size was coming from.
Any ideas?