Replies: 1 comment
|
I think I have found a better way to support S3 or other backends with minimal maintenance overhead or plugin bloat. So this polling can be finished. Looking at the results, more than 1/3 of the people would like to see the S3 support. Although not the majority, if we consider the impact of sampling bias, the result might lean toward it. S3 syncing will come true at some point in a wiser way, the ones who don't need S3 won't receive any bloat in the new architecture. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I have a long-term plan to support S3 and S3-compatible storage, like what Remotely Save does. Currently, the plugin code is strongly reusable to adapt S3.
I need a polling to determine whether the plan is worthwhile. I recommend everyone who sees this participate in the 5-second anonymous polling to allow me to obtain a fair result, no matter you feel interested about S3 or not, thanks♥️ !
Pros of adapting S3:
Cons of adapting S3:
Note that apart from WebDAV and S3, all proprietary protocols and vendor-specific APIs (OneDrive, Google Drive, Dropbox) will not be planned in the near future. They add pure overhead to the plugin and only benefit a small portion of users.
44 votes ·
All reactions