Hacker News Reader

Do you know what would be nice ? A way to encrypt the data before viewing to the user and the js will decrypt the data by calling a websocket api to give the password. This way for each specific websocket session you encrypt and decrypt the data differently. Also you can hide recognizable information in the data so when copied you will search the history to find who did it.

View on HN

That would not work, would be a poor user experience, would be technically infeasible, and would be ineffective.

You can't publish content to the public and prevent copies being made. That's the lesson we need to take away from the DRM nonsense that we went through (and to some extent, are still going through).

Reply on news.ycombinator.com