Existing options are built for the mass-market, but I wanted to be able to control where I stored my data, and I wanted to ensure that I was using client-side encryption.

So I built one, would love some feedback. If you're interested in trying it out (free for my first users if you don't mind giving me some feedback), hit me up.

First round of features are:

  - Configure your own storage backend that _you_ control (S3, GDrive, iCloud)
  - Client-side encryption (AES-256-GCM with PBKDF2)
  - Pin, auto-locking, metadata stripping, blur-when-in-background, delete-on-import
  - Zero telemetry, zero tracking, zero outbound connectivity except to talk to your configured storage system 

Comments URL: https://news.ycombinator.com/item?id=47651536

Points: 2

# Comments: 0

For hobby sites, you could argue (I think the argument is still weak), about the MITM threat being low enough to not be worth doing something, but this is a security blog.

Security blogs matter, because people follow their guidance. This makes them a potentially attractive target for some groups of people.

Not everything needs to, or should have the same quality standards applied to them. For the purposes of the Cursor post, it doesn't bother me that most of the commits produced failed builds. I assume, from their post, that at some points, it was capable of building, and rendering the pages shown in the video on the post. That alone, is the thing that I think is interesting.

Would I use this browser? Absolutely not. Do I trust the code? Not a chance in hell. Is that the point? No.

I did read your post, and agree with what you're saying. It would be great if they pushed the agents to favour reliability or reproducibility, instead of just marching forwards.

People were making all sorts of statements like: - “I cloned it and there were loads of compiler warnings” - “the commit build success rate was a joke” - “it used 3rd party libs” - “it is AI slop”

What they all seem to be just glossing over is how the project unfolded: without human intervention, using computers, in an exceptionally accelerated time frame, working 24hr/day.

If you are hung up on commit build quality, or code quality, you are completely missing the point, and I fear for your job prospects. These things will get better; they will get safer as the workflows get tuned; they will scale well beyond any of us.

Don’t look at where the tech is. Look where it’s going.

In the example of a data centre, there would be considerably more heat generation than 3 astronauts, but, I would like to understand more. 38F is cold, so heat is clearly lost not as slowly as we might think.