Live data from Hacker News

Show HN: We built an end-to-end encrypted alternative to Google Photos

news.ycombinator.com

401–410 of 421 posts

Re: Show HN: We built an end-to-end encrypted alternative to Google Photos

#401

I think the idea is great, I'm looking for a E2EE photo service already for a long time. Although I'm not a security expert, I have some worries about your security concept. 1. When the user wants to change the password, all photos&videos have to be reencrypted and uploaded which is absurd for most people because ~100GB of photo-storage is not an exception these days anymore. 2. When your database is leaked, it is ve…

1. A user can change their password without re-encrypting any of the uploaded files. Changing the password only changes the encryptedMasterKey that is stored on the server. 2. Hashes of passwords are not stored at our server, and email addresses are stored encrypted. You can read more about our key-encryption flow here: https://ente.io/architecture#key-encryption

1. Oh sorry, thanks for the clarification

2. How is the email address encrypted? Why would an attacker need a stored hash? In a database leak situation it's possible to get to the data with only a valid email-password combination or am I missing something ? There is no information from a registered device necessary for the decryption right ?

Re: Show HN: We built an end-to-end encrypted alternative to Google Photos

#402

Earlier quoted context omitted.

I liked the clarity of response. Public models, not user data seems a clear answer to your question?

Not really. In fact it might suggest something I'm specifically more worried about. Datasets that we use in research aren't really appropriate in production. They have a lot of biases that we don't exactly care about in research but you do in production that can also get you into a lot of political and cultural trouble. So really if they are going to just use public datasets and not create their own then I expect a s…

Appreciate the detail here. Given your relevant experience sounds like something that the devs need to address.

Re: Show HN: We built an end-to-end encrypted alternative to Google Photos

#403

Earlier quoted context omitted.

Not really. In fact it might suggest something I'm specifically more worried about. Datasets that we use in research aren't really appropriate in production. They have a lot of biases that we don't exactly care about in research but you do in production that can also get you into a lot of political and cultural trouble. So really if they are going to just use public datasets and not create their own then I expect a s…

Appreciate the detail here. Given your relevant experience sounds like something that the devs need to address.

Being in the ML community I have a lot of criticisms of it. There are far too many people, especially in production, that think "just throw a deep neural net at it and it'll work." There is far more to it than that. We see a lot of it[0]

[0] https://news.ycombinator.com/item?id=28252634

Re: Show HN: We built an end-to-end encrypted alternative to Google Photos

#404

Earlier quoted context omitted.

Appreciate the detail here. Given your relevant experience sounds like something that the devs need to address.

Being in the ML community I have a lot of criticisms of it. There are far too many people, especially in production, that think "just throw a deep neural net at it and it'll work." There is far more to it than that. We see a lot of it[0] [0] https://news.ycombinator.com/item?id=28252634

Wow fascinating. What do you ideally want to see in terms of datasets enabled by user data?

Having vendors vacuum up my data is sub-optimal from a privacy/ownership standpoint. I'm curious how to enable models without giving away my data. Open source models owned by society? Numerai style training (that I don't understand) https://numer.ai/ ?

Re: Show HN: We built an end-to-end encrypted alternative to Google Photos

#406

Earlier quoted context omitted.

Being in the ML community I have a lot of criticisms of it. There are far too many people, especially in production, that think "just throw a deep neural net at it and it'll work." There is far more to it than that. We see a lot of it[0] [0] https://news.ycombinator.com/item?id=28252634

Wow fascinating. What do you ideally want to see in terms of datasets enabled by user data? Having vendors vacuum up my data is sub-optimal from a privacy/ownership standpoint. I'm curious how to enable models without giving away my data. Open source models owned by society? Numerai style training (that I don't understand) https://numer.ai/ ?

Datasets are actually pretty hard to create. You can see several papers specifically studying ImageNet[0] including some on fairness and how labels matter. There's also Google's famous private JFT-300M dataset[1]. JFT was specifically made with heavy tails in the distribution to better help study these areas, which is specifically the problem we're interested with here and one that is not solved in ML. Even with more uniform datasets like CIFAR there are still many features that are noisy in the latent space. This is often one of the issues with doing facial recognition and why there's issues with people with darker skin. Even if you have the same number of dark skinned people as light skinned you may be ignoring the fact that cameras often do not have high dynamic ranges and so albedo and that dynamic range play a bigger role that simply "1M white people and 1M black people". There's tons of effects like this that add up quickly (this is just an easy to understand example and one that's more near the public discourse). You can think back to how Google's image search at one point showed black people if you searched gorilla. On one hand you can think "oh got a dark color humanoid" or you can think "oh no... dear god...". That's not a mistake you want to make, even if we understand why the model made it. It is also hard to find these mistakes, especially because the specifics of them aren't shared universally across cultures because this mistake has to do with historical context.

This is still an unsolved problem in ML. Not only do we have dataset biases (as discussed above) but models can also exaggerate these biases. So even if you get a perfectly distributed dataset your model can still introduce problems.

But in either case, we don't have the same concerns in research as we have in production. While there are people researching these topics most of us are still trying to just get good at dealing with large data (and tails) in the first place. Right now the popular paradigm is "throw more data at the model." There are nuances and opinions to this why this may not be the best strategy and why we should be focusing on other aspects (opinions being key here).

Either way, "using publicly available datasets" is an answer that suggests 1) they might not understand these issues and 2) the model is going to have a ton of bias because they're just using off the shelf models. I want some confidence that these people actually understand ML instead of throwing a neural net at the problem and hitting go.

> I'm curious how to enable models without giving away my data.

Our best guess right now is homomorphic encryption. But right now this is really slow and not as accurate. There's federated learning but this has issues too. Remember, we can often reconstruct images from the dataset if we have the trained model[2]. You'll see in this reference that while the reconstructions aren't perfect, they are more than satisfactory. So right now we should probably rule out federated learning.

> Open source models owned by society?

Actually models aren't the big issue. Google and Facebook have no problem sharing their models because that isn't their secret sauce. The secret sauce is the data (like Google's proprietary JFT-300M) and the training methods (though most of the training methods are public as well as few are able to actually reproduce due to not having millions of dollars in compute).

I hope this accurately answers your questions and further expands on the reasoning behind my concerns (and specifically why I don't think the responses to me are sufficient).

[0] https://image-net.org/about.php

[1] https://arxiv.org/abs/1707.02968 (personally it bugs me that this dataset is proprietary and used in their research. Considering how datasets can allow for gaming the system I think this is harmful to the research space. We shouldn't have to just trust them. I don't think Google is being nefarious, but that's 300M images and mistakes are pretty easy to make).

[2] https://arxiv.org/abs/2003.14053

Re: Show HN: We built an end-to-end encrypted alternative to Google Photos

#407
post #85

Earlier quoted context omitted.

You can run algorithms locally and still violate privacy by uploading private facts derived from the data with algorithms. Saying you won’t hold “indexes” doesn’t begin to cover it.

Well, it does begin to cover it. Do you have to be so strident?

What do you think is meant by indexes?

Re: Show HN: We built an end-to-end encrypted alternative to Google Photos

#408
post #332

Earlier quoted context omitted.

Have you tried the Synology Photos app ( https://www.synology.com/en-global/DSM70/SynologyPhotos [1]) While it does have some kinks it's surprisingly good and has the features you are looking for in a locally hosted/publicly available option. You do have to buy one of their NAS's however. I have moved over to this partly for privacy and partly due to cost (I produce way too many photos per year to store them economic…

The biggest problem I've faced with their app suite is it seems to make my disks spin 24/7, constantly seeking even if there is zero external activity. It wouldn't be such a big problem if I didn't live in a small apartment and have to listen to them seek all night. Other people have reported the issue, but it doesn't seem like they plan on addressing it.

I'll be honest I keep my NAS in a purpose built server closet in my house which is shielded.

Maybe costs of SSDs are coming down enough you could use those instead?

Re: Show HN: We built an end-to-end encrypted alternative to Google Photos

#410

Earlier quoted context omitted.

Wow fascinating. What do you ideally want to see in terms of datasets enabled by user data? Having vendors vacuum up my data is sub-optimal from a privacy/ownership standpoint. I'm curious how to enable models without giving away my data. Open source models owned by society? Numerai style training (that I don't understand) https://numer.ai/ ?

Datasets are actually pretty hard to create. You can see several papers specifically studying ImageNet[0] including some on fairness and how labels matter. There's also Google's famous private JFT-300M dataset[1]. JFT was specifically made with heavy tails in the distribution to better help study these areas, which is specifically the problem we're interested with here and one that is not solved in ML. Even with more…

godelski, I really appreciate such a thoughtful response to my curiosity.

Looking at this while better understanding the problem, I wonder what features I really want for my own photo library. Thinking of iOS photos. Matching people together seems hard. But grouping photos by GPS location or date is trivial. So we have to get clear on what features are important for home photo libraries.

I can now see how the idea of "use public libraries = solution" falls short. It neither presents a viable solution or demonstrates rigorous understanding.

Post reply on HN