Skip to content

Comment on Why SpiderOak doesn't de-duplicate data across usersparent

Comments

My point is specifically that many of them are doing so in this ridiculous way. You can try for yourself: upload a bunch of pirated mp3s and see if the transfer is suspiciously fast.

But saying that other companies are doing things wrong, doesn't mean you have to throw the baby out with the bathwater - you can still do de-duping, you just won't do it in a way that exposes vulnerabilities/etc.

The article makes it sound like it cannot be done.

To my knowledge, it cannot be done in a way that addresses the privacy concern: that a court could require the storage operators to answer such questions about their customers as described in the article.

If there's a way around that, I am your eager student.

By the way, some people have suggested using reference counts as a solution. You then know, for example two or more users share duplicate data, but not which two users. My feeling is that, at some time, you did know which users those were (when the counts were incremented.) I like to stay within the realm of "we are not capable of knowing" instead of simply, "as it happens, we don't know anymore."

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.