|
|
|
|
|
by _nalply
1729 days ago
|
|
Yeah. I remember reading somewhere text steganography being used not to encode a hidden message but to identify recipients who might leak the text. One way is to introduce small mistakes or differences like "were were" but differently for each recipient. One might get "were were" and someone else might get "the the", a third one might get a superfluous comma, etc., even harmless differences which are not mistakes are possible. One possible difference corresponds to a bit of information. If you have one hundred possible differences, you have one hundred bit of identificating information. But I am sure that it is possible to work around this. Just don't give the exact memo text to the public. Paraphrase the text. I am afraid copy-edit or some intentional changes won't be enough if you don't paraphrase the text. Dangerous and prone to mistakes but surely lucrative or satisfying for the leaker. |
|
Those people would probably do something like innocuously forward it to other departments. Reply to your version of the memo, but respond to the entire design and sales teams. Something like "What a great memo by Tim Cook!"