Hacker News new | past | comments | ask | show | jobs | submit | sdizdar's comments login

Leninism, Stalinism, etc. (countries you mentioned) are attempts to fix problems with capitalism identified by Marx and Engels.

Marxism is a method of socioeconomic analysis and it true that Marx and Engels writing offered scientific/philosophic background for revolutions (which ended up worse than capitalism). But their critique of capitalism is still very much valid.

If you want be successful capitalist you need read "Das Capital": many things will become clear. Or just watch it: http://davidharvey.org/reading-capital/


Bugs will always exist :( - and even if your data is in the cloud it is always good make one more copy. For example, you can use cloudHQ to backup to Dropbox: https://www.cloudHQ.net/backup_to/dropbox


As founder of cloudHQ, I have to jump into this. Software products will have bugs. And people will make mistakes. We are all human.

So even if you store data in Dropbox - it is smart to have one extra copy in some other cloud storage. Like Google Drive. Or Box. Or Egnyte. So if data is deleted in Dropbox (accidentally, maliciously, or due to a bug) you can restore it from other cloud.

Of course, cloudHQ is the system which can do that: http://chq.io/hnsc


Shameless Plug: you can continuously backup all your Google email to Dropbox, Google Drive, Box, SugarSync, or SkyDrive via cloudHQ (http://cloudHQ.net). We support txt, html, or eml export. You can also just backup certain types of attachments. And backup is continuous and in real time - as soon as a new email is added it will be transfered and backed up to your Dropbox/Box/Google Drive folder.

Here is a short video on how to setup this: http://vimeo.com/65168186


cloudHQ.net - San Francisco, CA - Marketing aka. Growth Hacker

We are bootstrapped and profitable cloud-to-cloud replication and synchronization service. We consider ourself the market leader in cloud-to-cloud synchronization and backup with more than 2 million copied every day.

You will be the first person solely responsible for marketing and hacking the growth. In other words, your goal is to increase awareness, virality, traction, adoption, and advocacy for our product in a scalable way.

Our email is: jobs@cloudHQ.net


Shit happens and things will go down (or accidentally/maliciously deleted) so dont put all your eggs in one basket. Back in 1970s and 80s companies were replicating data between different systems for redundancy. They do that even today.

So that is reason that if you depend on the cloud (and mobile) you should replicate all your data to some other cloud service. Just in case.

(And that is reason we built http://cloudHQ.net)


Or maybe we need "dropbox for email" YC S13 company.


Yes, sync != backup [1].

I do agree with you but, I can tell you that selling backup service is harder than you think. Also as pointed by paper [2], the human error accounts for ~50% of all system failures. And the worst thing is that majority of users who accidentally delete data, don't even notice data loss until lost data is needed and they don't recollect doing something wrong.

What I found out interesting that people (i.e., small business owners) will are scared of losing a credit card (even though you can call the bank and cancel your lost credit card and get a new one - inconvenience but not a big deal), but they will not backup critical company documents and data (even if they lose them the company will be pretty much closed - there is no "bank" to go to and get data back).

[1] http://blog.cloudhq.net/post/33844549768/the-difference-in-d... [2] http://roc.cs.berkeley.edu/talks/pdf/HP.pdf


Not sure it is harder than I think. Other than that, I haven't nothing else to disagree with. :)


Yes - sync is not a backup but services as Dropbox are designed to be backup too (with their revision feature).

So I think the underlaying problem here is that any backup/syncing system might have a bug (like this one) or there might be operator or user error (deleting your revision history is just a couple clicks away). Recovery oriented computing website has a lot good papers on this topic [1].

This is very similar to problems with outages on Amazon EC2 - yes Amazon cloud is great but in order to make your service highly available you do need to have standby system on some other cloud (for example, we run on Rackspace but our standbys are on Amazon).

One approach to protect yourself against problems like this is to replicate/sync all your files from one cloud storage (your primary one) to some other cloud service (GDrive, SugarSync, Box, etc.). So should Dropbox have a bug, then you still have everything in other cloud service: including all revisions.

Services like cloudHQ [2] (that is my baby) can replicate and sync all your files from Dropbox to, for example, GDrive. And of course cloudHQ has options like "two-way" sync, "don't replicate deletion", "backup" (weekly incremental are in folders - so your will be fine even if "revisions" feature fails), etc.

[1] http://roc.cs.berkeley.edu/

[2] http://cloudHQ.net


I don't think generating more complex passwords will completely solve the problem.

The problem is using only one cloud service for your data.

Basically, don't put all your eggs in one basket. I always recommend to replicate all your data and files to other cloud service which has different security characteristics. For example, if you use Google Docs and Evernote - replicate everything to a separate Dropbox or Google Drive account (using cloudHQ or some other system). Doing offline backup manually is also a solution but it is easier just to replicate everything to a separate Dropbox account and Dropbox will put everything to your PC - you can map that Dropbox account to an external drive.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: