Hacker News Reader

Comment by 2474 | Hacker News Reader

Yeah, I would have chosen a better way to imply that.

Hmm. Do you mean it sounds like we'll get hacked any day now? Do you have a suggestion for better wording?

Thankfully, I don’t think this is a super strong selling position. Google has an incredible reputation for keeping its users safe and their information private. What you don’t know is whether google in fact stores your documents in an encrypted format at rest. If they do, then what exactly are you offering?

Google can and does read your documents (in an automated fashion). That's how they can flag documents for abuse/TOS violation, as they are currently having issues with today. The whole argument here is that Airborn OS can't read your documents, presumably at all.

A bit off-topic, but since Google's goal seems to be know everything possible about you, so they can sell better, more expensive ads and make more money, they presumably do more than just look for TOS/copyright violations. Otherwise I agree with what you said.

Just say "So Secure that no one read it even if they wanted to"

Yeah, exactly. I agree with the "so secure" suggestion by the other commenter. You can tweak it to your liking but you don't want to give the impression you're anything less than complete with your approach to security.

You should speak to me, as a customer, about my benefit in using your product.

Currently you're telling me what won't happen in a very unfortunate event. I think this is wrong in 2 ways.

1. You're telling me a message "the other way around". Even if you just say "Keep your documents secure" is better than "Nobody will access your documents".

2. You're comparing w/ Google docs so, following the logic of your message, what's the probability that Google will get hacked? Tiny, right? So... you're not telling me anything useful.

You can check lastpass or 1password as examples. They implement more or less the same thing, but as you can see they don't talk about how it works, but about the benefit for me, as a customer.

Thanks for the suggestions. The reason I mentioned getting hacked in the copy, is because I think that for the average customer, it's now starting to seem like every web service is getting hacked. I wanted to highlight that we're trying to solve that in a better way than "well, this time we really won't get hacked!" But yeah, I'll try to bring out that message in a more positive way.

> for the average customer, it's now starting to seem like every web service is getting hacked.

It did have a positive influence on me right away. It also established this sense of trust. Enough that I began to crawl through the other pages for more info.

I also appreciated how you managed to convey, in a single image, exactly what was encrypted (ie, both document content and filename).

The first question I had was how Google Docs handled this. Do they also encrypt? If so, do they encrypt both filename and content? Considering Google's business model, I always assumed that they did less in this regard - relying instead on other mechanisms to protect user data.

I would keep the encryption message and double-down... comparing how other services handle privacy, tracking, data-mining, encryption. It's your strongest selling point.

Thanks! Google Docs can read your content on the server, as proven by https://motherboard.vice.com/en_us/article/zmz3yw/why-is-my-....

You mean as proven by being able to share docs publicly? There isn't some grand conspiracy here, Google never claimed they couldn't read your content. That's literally the point of most of Google Docs is that Google _can_ read the content.

I like the copy. "Even if we get hacked, they can't read your ..." is a real claim. It means something concrete, and is an interesting hook for someone who's technically literate. Something more generic like "We keep your documents secure" means almost nothing nowadays -- literally every online document storage system will tell you that regardless of how seriously they take security. I'm sure Equifax will be happy to tell you how secure your data is with them.

You have good points and in you might be right for the common user.

But as a technical user I despise that and I liked the honest way this was presented. Because this is something everyone should be thinking before signing up (granted most don't, so, yeah).

Your current copy tells something very real and concrete to the user, gives him valid information. It is useful.

All suggestions in this thread ("it is secure!") are just marketing gibberish, slogans without any meaning. If you intend to appeal to a large, stupid audience, maybe they're good, but it is a little dishonest.

While you are right, it wouldn't be that great of an idea for Honda to market their new airbags by saying "Next time you get into that accident, at least your face won't be smashed into a million pieces by your wind shield!".

While what he has is fine, you can convey the same sentiment without saying "Even if we get hacked..."

Ok, but you don't have to say evasive things like "Honda airbags adds the safeness of air to your driving".

No, I don't necessarily think it implies you'll be hacked immediately, or anytime for that matter.

I definitely get what you are trying to do though. It's so secure it doesn't matter if someone has the data.

Perhaps some clever illustration depicting the odds of cracking AES-256 (e.g. a man fishing in the ocean but there's only one fish to be caught). Visuals can be a great way to convey complex concepts.

I don't think what you have is a huge red flag but someone might read it and say "Whoa, ok, it sounds secure but what about other systems they have in place? Are they insecure, are people trying to get at my data 24/7 on their servers, etc.

Reply on news.ycombinator.com