Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
171–180 of 219 posts
Re: Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
#172Earlier quoted context omitted.
Vibe coded / sloppy projects
There are plenty of reasons to criticize OneDrive and I personally would not use it. But I think comparing it with a weekend vibe coded self hosted project is a bit of a stretch.
There is also sentiment / understanding that Microslop has been pushing their devs to do the ai thing and that it is resulting in more downtime and bugs. This is not limited to one company and more an artifact of the hype cycle. If anything, it's worse with the corporate product because there should be more checks and balances, but here we are.
Re: Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
#173Re: Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
#174S3 is costly and carries significant political baggage. For a better alternative, run MinIO on a cloud provider of your choice, or stick with a secure option like Proton Drive.
> S3 is costly > run MinIO When people say "s3", they mean "any s3 compatible storage" in my experience, not "amazon s3 specifically" or just "s3 as a protocol".
Re: Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
#175Earlier quoted context omitted.
Because you can self-host it all and validate the source yourself!
How can I practically verify 2TB of a life's worth of files while guaranteeing I won't have data loss due to some edge cases and race conditions that delete my data. Every time I've created my own backup script I realized knowing what to delete and when is not easy. IMO the practical solution to this is to just pay for more storage (within reason).
Re: Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
#176Re: Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
#177Earlier quoted context omitted.
How can I practically verify 2TB of a life's worth of files while guaranteeing I won't have data loss due to some edge cases and race conditions that delete my data. Every time I've created my own backup script I realized knowing what to delete and when is not easy. IMO the practical solution to this is to just pay for more storage (within reason).
How can you practically verify that OneDrive won't do this either?
Re: Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
#178But you have to pay for your own S3 bucket as well... and it's generally several times more expensive per terabyte, though this depends on different factors. (Not to mention you might still have to pay for Google if your e.g. Gmail doesn't fit into the free tier anymore.)
If this is supposed to be financially motivated, the creator seems to have it somewhat backwards.
Re: Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
#179Earlier quoted context omitted.
Because you can self-host it all and validate the source yourself!
How can I practically verify 2TB of a life's worth of files while guaranteeing I won't have data loss due to some edge cases and race conditions that delete my data. Every time I've created my own backup script I realized knowing what to delete and when is not easy. IMO the practical solution to this is to just pay for more storage (within reason).
Same with literally every other backup software. Have two, and test restorations regularly. It's not easy, but nothing worth it when you need it ever is.
Re: Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
#180Earlier quoted context omitted.
What experience?
A recent (last year?) Windows update moved a lot of people's Documents folder into OneDrive, without asking. In some cases people lost data, in others it was a nuisance as all sorts of embedded or saved paths broke.
Absolutely insane, glad I had Backblaze to restore from, but it even remapped his Documents and other home folders to a new place, so using restore didn't immediately make the files appear.