101–110 of 421 posts
Why does this app need to link my identifiers and contact info to my identity? I would feel a lot more comfortable with this if it didn't collect any data of mine, and you were just storing ciphertext. I don't want an account, and I don't want to give you my name or email.
Your homepage says "protect your photos/faces etc. from algorithms" The algorithms are what makes Google Photos; Google Photos. If I wanted to just store my photos I'd throw them in a S3 bucket or Dropbox or something. Google Photos lets me automatically categorise my photos by person, lets me search my library using text search for anything (e.g. I can search 'museum' and see pictures I've taken in museums). That is…
Now that you've mentioned it, yes, I'd like to try that. But as a counterpoint to your argument, I've never needed it, and I suspect that a lot of people may not actually be getting the same value propositions that you're getting.
On the other hand, Google Photos is Google Photos. But it's often a mistake to compete directly with an established product. New ideas tend to win by transcending the competition.
I propose that if this Show HN turns into a product, it will be because it does something people didn't realize they wanted. Maybe that's privacy. I don't know.
This is looks super cool, however not something I'd be interested in using myself if I can't selfhost it (at least it looks like thats not possible from the website).
Self-hosting a zero knowledge service is probably unnecessary. If you're hosting the service, there's no need for data to be encrypted client-side. Unless, of course, you were intending on running the service on a public cloud which you didn't control, but that's something I don't think many privacy conscious folk would do. There's plenty of open source, self-hosted alternatives to Google Photos.
Clickable links! [1]: https://ente.io [2]: https://ente.io/apk [3]: https://play.google.com/store /apps/details?id=io.ente.photos [4]: https://apps.apple.com/in/app/ente-photos/id1542026904 [5]: https://web.ente.io [6]: https://github.com/ente-io/bhari-frame/releases/latest [7]: https://libsodium.gitbook.io [8]: https://ente.io/architecture [9]: https://github.com/ente-io [10]: https://www.reddit.com/r/degoogle/comme…
Earlier quoted context omitted.
I fully agree. It's a hard sell getting people to switch from an evil but known cloud provider to an unknown cloud provider that claims to not be evil. What we do not need is more cloud offerings that can change, vanish or lock us out at the blink of an algorithm's eye. What we need, rather, are reliable and easy-to-use solutions that allow us to retain full control of our data (i.e. self-hosted and offline) while ha…
Hey, so the project had initially started off as a self-hostable software (with an option to buy a pre-configured device). We realized soon that it's hard to monetize such a product in the consumer space to the point where it can become self-sustaining. We don't have a problem with offering a self-hosted variant. But given our limited engineering bandwidth we had to take a call on who our target market should be, and…
I suspect the way it usually happens is that somebody your parents trust (like you) tells them to sign up for a privacy-preserving backup service.
But who's going to tell them to do that? Do you have the money to pay for advertising?
Normally, I'd suspect it's the tech-savvy younger folks who'd tell them to buy something like this but with your pricing and lack of self-hosted options, I suspect you've alienated a large portion of the tech-savvy audience you need to advocate for your product.
Earlier quoted context omitted.
> So you're going to implement algorithms then? Yes, we will implement the algorithms, purely on the client side, such that we don't hold indexes to your personal data. But I understand how that piece of text could have thrown you off, I'll think of ways to rephrase it. Thanks for pointing it out.
Actually I'm really curious how you do this. If the photos aren't stored client side, then how do you search? Do you have a thumbnail of every photo client side? Is that enough? I mean ImageNet scores are still pretty low for small/fast neural nets. And ImageNet isn't even representative of real world photos. So obviously to be successful you're going to have to continue training. So how do you do this in a privacy p…
In the happy path the files/thumbnails are indexed before they are uploaded. But we are designing a framework that will pull files/thumbnails for indexing if they are unindexed or indexed by older models.
> how do you do this in a privacy preserving way
Our accuracy will not match that offered by services who index your data on their servers. But there's a trade off between user experience and privacy here, and we are hopeful that ente will be a viable option for an audience who is willing to sacrifice a bit of one for a lot of the other.
Very reasonable pricing, though you could advertise the free 'trial' tier a bit more prominently. I thought the service was paid only until I re-checked the pricing page and read the tiny gray on black text before writing this comment. You also didn't set a single tracking cookie. Nice.
Your homepage says "protect your photos/faces etc. from algorithms" The algorithms are what makes Google Photos; Google Photos. If I wanted to just store my photos I'd throw them in a S3 bucket or Dropbox or something. Google Photos lets me automatically categorise my photos by person, lets me search my library using text search for anything (e.g. I can search 'museum' and see pictures I've taken in museums). That is…
We need to make this stuff local again, that will be the real competitor to big corp Foo... no servers, no end-to-end, no service cost, no ads, no privacy issues, no random revokation of accounts without recourse, just one end - the users. We can have face detection etc locally if people want it... cycles, it's going to happen eventually.