Live data from Hacker News

Replacing Dropbox in favor of DigitalOcean spaces

mitjafelicijan.com

51–60 of 201 posts

Re: Replacing Dropbox in favor of DigitalOcean spaces

#51
post #13

You wrote about deplatforming-- heads up that DigitalOcean does deplatform people. I have direct firsthand knowledge of DigitalOcean deplatforming a security disclosure professional reporting a root breach bug. For your secure backups, I can suggest Tarsnap by Colin Percival, who's a security expert and a frequent contributor on Hacker News. I don't get anything for recommending Tarsnap; I'm just a customer. https://…

> I don't get anything for recommending Tarsnap; I'm just a customer. https://www.tarsnap.com/

From their site:

"The Tarsnap service is built on top of the solid platform provided by Amazon Web Services."

Re: Replacing Dropbox in favor of DigitalOcean spaces

#53
When I read "Replacing Dropbox", reading about a 1 way sync system for backing up a single system isn't what jumps to mind.

The magic of Dropbox is that it sync files across multiple computers and allows multiple people to share files. This doesn't do any of that.

You can use Dropbox for that, but there are definitely cheaper/ more robust solutions.

Re: Replacing Dropbox in favor of DigitalOcean spaces

#54

$5 for 250GB of storage and then $20 per TB ($0.02/GB) after that seems a bit steep. Plans and Pricing The base rate of a Spaces subscription is $5/month and gives you the ability to create multiple Spaces. The subscription includes 250 GiB of data storage (cumulative across all of your Spaces). Additional storage beyond this allotment is $0.02/GiB. If you cancel your subscription by destroying all your Spaces, your…

I think hetzner is about half an expensive (€8 tb/m) and I personally prefer ssh/rsync to http/S3.

I don't know what Hetzner is, but if rsync is available, it's a much better option, particularly if you can do incremental syncing you can get a fairly robust setup with very little code.

Re: Replacing Dropbox in favor of DigitalOcean spaces

#55
post #39

There is a lot of open source file sync software out there (ownCloud, NextCloud, Seafile, Syncthing, ...) that would be much better suited for a self-hosted Dropbox replacement than a single bash script. You are many orders of magnitude more likely to lose your data due to a code bug or unstable network than deplatforming. I looked into setting up something of the sort for myself a little while ago, but unfortunately…

[deleted]

Re: Replacing Dropbox in favor of DigitalOcean spaces

#56
post #39

There is a lot of open source file sync software out there (ownCloud, NextCloud, Seafile, Syncthing, ...) that would be much better suited for a self-hosted Dropbox replacement than a single bash script. You are many orders of magnitude more likely to lose your data due to a code bug or unstable network than deplatforming. I looked into setting up something of the sort for myself a little while ago, but unfortunately…

You can host Nextcloud at your home using something like NextcloudPi+DDNS (https://nextcloudpi.com) or HomeDrive (https://homedrive.io, which has ngrok-ish end-to-end tunnels integrated), and the monthly cost would be almost $0. :)

Re: Replacing Dropbox in favor of DigitalOcean spaces

#57

When I read "Replacing Dropbox", reading about a 1 way sync system for backing up a single system isn't what jumps to mind. The magic of Dropbox is that it sync files across multiple computers and allows multiple people to share files. This doesn't do any of that. You can use Dropbox for that, but there are definitely cheaper/ more robust solutions.

Well to be fair the remote backup is the part that's hardest to recreate with a self-hosted solution.

Re: Replacing Dropbox in favor of DigitalOcean spaces

#58
post #43

Earlier quoted context omitted.

I agree with you. I should add a disclaimer that this is still being worked on. I will add what you proposed. Thanks for your input.

Always start all your bash scripts with set -e You'll never regret it and might be very very very happy it was there. And if you start with that, then as you work on the shell script, you'll be more likely to make the script be idempotent (checking for files before copying, checking for lines in files before appending/sed'ing etc.) Idempotent >> non-idempotent for "alter the state on an end point" things.

Totally agreed. You can also temporarily turn it off and turn it back on again if you really need to by doing "set +e ... set -e". Sometimes it is more convenient to check errors explicitly, i.e. with test code where the test is expected to fail, but errors should fail fast by default.

Re: Replacing Dropbox in favor of DigitalOcean spaces

#59
post #43

Earlier quoted context omitted.

I agree with you. I should add a disclaimer that this is still being worked on. I will add what you proposed. Thanks for your input.

Always start all your bash scripts with set -e You'll never regret it and might be very very very happy it was there. And if you start with that, then as you work on the shell script, you'll be more likely to make the script be idempotent (checking for files before copying, checking for lines in files before appending/sed'ing etc.) Idempotent >> non-idempotent for "alter the state on an end point" things.

I don’t know about never regretting. “set -e” is the right choice the vast majority of the time, but definitely has some gotchas to it. For instance, what does the following script print?

  #!/bin/bash

  set -e

  (
   echo "Start of Subshell"
   (exit 1)
   echo "This shouldn’t run, right?"
  ) || echo "Subshell failed"

Re: Replacing Dropbox in favor of DigitalOcean spaces

#60
post #13

You wrote about deplatforming-- heads up that DigitalOcean does deplatform people. I have direct firsthand knowledge of DigitalOcean deplatforming a security disclosure professional reporting a root breach bug. For your secure backups, I can suggest Tarsnap by Colin Percival, who's a security expert and a frequent contributor on Hacker News. I don't get anything for recommending Tarsnap; I'm just a customer. https://…

I had a terrible, terrifying experience with DO where they hard locked my account for days (and it would have been weeks if I hadn't made a huge stink) because of a misunderstanding. They ban/lock first, ask questions later, and that's not cool and I can't have my (and my customer's) important infrastructure treated that way. I now use Linode for most of my stuff, and once they have cloud firewalls available in Dalla…

> They ban/lock first, ask questions later

Given the sheer volume of dodgy packets that originate from DO network space, I find this surprising.

Post reply on HN