Hacker News Reader

This feature isn't about security. Email is already pretty secure with TLS and DKIM. This is basically the equivalent of the "DO NO FORWARD" header people use for internal-only information but with a little more UX polish.

View on HN

I think what the parent is saying is that they feel this DO NOT FORWARD header feature is being presented as a security feature. I probably agree

This is an algorithmically enforced one, though.

But anyone can screenshot the message or take a photo of it. The point is that it's not actually enforced.

Anyone can screenshot or take a photo of any decrypted message. The question is when the email leaves Google's servers and whether you can trust Google with that same document.

Personally, if I had a message where I would consider a tool like this, I would just encrypt it on the client with PGP or something.

> Anyone can screenshot or take a photo of any decrypted message.

Yes, but ordinary decrypted messages don't claim to have superpowers like self-destructing.

The person I replied to wrote that this was "algorithmically enforced". I'm just pointing out that this is incorrect.

As long as it doesn't leave Gmail.

I believe Gmail already has that feature for corporate gsuite- greying out the forward button or something like that. Could be wrong. I know for sure Outlook has it.

Reply on news.ycombinator.com