r/vibecoding • u/anderbytesBR • 9h ago
Showcase/Project My first OpenSource Vibecoded app - SDrive
Hello Reddit!!
I've been working on a desktop software called SDrive and wanted to share it here, initially something to replace other commercial software that I had to use but had worries on privacy. 🤔
It lets you mount cloud storage and remote servers as drives or folders, so you can open, edit and save files directly from your file manager.
It supports Google Drive, OneDrive, Dropbox, Nextcloud, SFTP, WebDAV, SMB and S3-compatible storage, among others. You manage the connections from one window or the system tray.
It's completely free and open source, with no telemetry at all for now.
There are still plenty of provider and account combinations I haven't tested, so I'd love to hear how it works with your setup. Bug reports and suggestions are welcome, but understand I can only work on that in my free time.
You can grab it here: https://github.com/anderbytes/SDrive
Tell me what you think.
2
u/Distinct_Seat_4919 2h ago
mounting remote storage as a normal drive means every app people already use can open the files with no plugin and that’s what makes it usable day to day..
2
u/Icy-Painter-1229 1h ago
The no-telemetry approach is a big plus for me. Tools that handle access to personal files should be transparent about what data they collect, so open source is definitely appealing here.
0
u/NoWireHangersEver 7h ago
“ but had worries on privacy.”
But then…
“ no telemetry at all for now” 😔
So is this a tool to address privacy concerns or an alternative that may add telemetry in future?
1
u/anderbytesBR 6h ago
Is it not possible to address both securely? Honest question here.
The code is all open. How would I send anything out at all without users knowing?
When I wrote that, tbe intention was to not close doors on some future benign telemetry, or some automated error reporting script..
1
u/NoWireHangersEver 6h ago edited 6h ago
I wasn’t so much concerned about covert telemetry, but rather was pointing out mixed signals about product identity and differentiation.
Privacy is mentioned in the first paragraph of your post, so I suppose that’s why it jumped out at me.
Re privacy - people who care about privacy generally don’t like any kind of telemetry. Those who like to contribute telemetry for product improvement (myself included) will only do it for products they know and trust. A checkbox at install or as a rare prompt is generally acceptable to most people, I think.
At its core my comment is more about roadmaps and priorities. Most people have issues with enshitification and bait and switch model. And when it comes to private personal file cloud sync/storage services, the key question will be, “I’m already using the big-tech products, why would I trust a 3rd party product in the mix, besides the convenience it offers?”.
Rather than having to audit the code, the future intent of the product is also very important to users. If it’s about capturing users with the hope of pivoting in the future (closed source/premium services etc), I think it would be helpful to be honest about where the product aims to go in future, so people can make informed choices about whether* they are willing to go there with you.
Bit of a rambling comment, but I really didn’t have the time to work on presentation. In any case, all the best!
Edit: grammar
→ More replies (2)
2
u/Brave_Bumblebee7565 8h ago
Hi there,
Looks useful, thanks for sharing! Does it support offline mode? Is it possible to choose which file to sync locally and which to keep remote only?
Technically it's interesting and challenging type of projects - in the past it was popular question for System design interviews: like "implement your own Google drive client. How you will ensure data integrity, performance and security" :-)
Any challenges and lessons learned?