
Meta? Privacy?
Please refrain from using those two words in the same paragraph, let alone in the same sentence - unless you precede the latter with "lack of" or "abuse of."
Meta's efforts to stop people repeatedly viewing WhatsApp’s so-called View Once messages – photos, videos, and voice recordings that disappear from chats after a recipient sees them – so far remain incomplete. An interim fix deployed to stop people keeping hold of View Once data has been defeated in less than a week by white- …
I know, I know. You would somehow ask for operating system providers to not allow users to use screenshots without first getting the approval of any application on screen, or maybe just any application at all. That's the only way they can try to do that and similar to anti-screenshot mechanisms they try to use on phones which only work because they can interfere with things they shouldn't be able to interfere with. Not that it would work either. It will always be relatively easy to copy something that appears in plain text on a screen, and they should give up on preventing that rather than try to make it impossible by imposing their control on everything else a computer can do.
That - this disclosure doesn't change the threat profile; even if whatsapp disable the phone's screenshot option while a view once message is on screen, you can still just photograph the screen. this feature by default has to assume someone can copy the message by hook or by crook.
It's useful for sending messages to someone you trust to not themselves disclose them; it makes sure that they don't remain on the recipient's device to be retrieved later by a third party. (Assuming that the messages to be disappeared were properly stored in the client, anyhow.)
Icon because it's the only way to be sure.
This sounds a lot like the way Exchange Calendar used to (still does?) implement private appointments; a flag on the appointment which the official client looked at. Use anything but the official client to access the Exchange server and it's trivial to see the details of private appointments. This is why I put private appointments in my public calendar described only as "Busy" and use a second calendar on my local disk to hold the actual details.
Yeah that one is great, I remember we had info screens with calendar information for meeting rooms and it would just blast out the private title of the meeting on the screen even though the user thought it was secret.
Hasty fixes implemented.
Also smells of "redactions" in PDFs where an extra layer of black is on top of the words, completely unaffecting the text entirely when highlighted. Classic.
> he was also disappointed that after all this Meta still hadn't got in touch with Zengo, despite its bug bounty terms of service promising frequent communication on submissions.
Maybe Meta doesn't want to deal with Israelis while they are committing genocide? Maybe Meta doesn't want to pay war criminals during this time?
Or maybe that screenshot showing the time in Tel Aviv was just a bad mistake and we aren't talking about cryptobros from a country that is committing genocide at this moment?