Hey everyone, thanks for the candid feedback.
@mecsbecs, I appreciate the clarity on the new funding guidelines.
To give some context, I proposed the S3/Rclone stack because the committee explicitly recommended starting there in my SiaTrans feedback… And the natural available pathway to that end was to use Renterd.
The ecosystem direction toward indexd + SDK is clear and great, and I’m more than happy to pivot. My original architectural preference was to build directly on indexd + SDK anyway.
@CtrlAltDefeat, you raise fair points about rclone having built-in workflows. It’s useful for power users, but it still requires installing rclone, running commands to start it, configuring remotes, and keeping things running in the background. For non-technical folks (content creators, small business owners, regular users), that remaining friction is exactly what stops them from trying Sia.
CloudBridge aims to be a zero-friction web UI for people who just want a familiar Google Drive style experience without touching a CLI.
I will revise the CloudBridge proposal to strip out the Renterd dependency and align it strictly with indexd + SDK, while keeping the scope small and focused as the committee initially requested.
I will update the thread once the new draft is ready.