Hacker News new | ask | show | jobs
by jooize 2023 days ago
I tried arguing for being able to delete messages from all parties of a conversation. [1] They were feature-averse back in 2014 for good reasons, but perhaps now they would consider implementing Delete Messages When Requested on a per-conversation basis.

[1] https://github.com/signalapp/Signal-Android/issues/1764 (2014)

1 comments

I've participated in some form conversations on the topic. At least people on the form are very against message deleting. Although Signal does have a bidirectional "delete for everyone" feature now. But you can only do it within 3 hours of sending the message.
Three hours is a very short duration, IMO. In my opinion, it should be at least a day (24 hours) or cover more than one’s average sleep duration so that any messages sent in haste can be removed once better senses prevail. Considering time zone variances across the people involved in chats, I think something more than 12 hours would be good.

We all have a need to amend our messages after ruminating on them for sometime. The three hour limit doesn’t gel well with how humans work (on this matter, even the HN edit limit duration is very short).

Yeah so I'd encourage you to write that on the signal forums. The discussions are very one sided. The arguments against deleting are "it's my device, so my data." The people there are very unhappy with the fact that you can even delete now (feature is like 2 months old).
That argument alone should suffice. Down that path lies trying to lock down other people's devices, people complaining that they deleted a message but others have screenshots, etc.

Once you've sent a message, the message is sent. Once it's on my device, it's mine. If you don't want someone to have a message, don't send it.

I consider that argument unpragmatic. Any recipient can still be made in control of keeping messages they have received. Sender must assume that the message is unretractable, because recipient can record it with a capturing device. If there is zero trust, you must operate by that assumption. If there is non-zero trust there are practical benefits to enabling any party to request the deletion of messages. Whether each party will accept that request is a matter to consider by the sender. Deletion can be per-conversation or per-contact preference controlled to automate, disable entirely, or prompt.

The program can not guarantee deletion, but in practice that is not necessary for it to be useful.

I'm not arguing that it is impossible to provide a best-effort mechanism. I'm arguing that it's a bad idea for a messaging program to even consider accepting deletion requests by default, because it sets unreasonable expectations.
This sounds like a classical slippery slope argument.

I think many people believe that if you create data it is your data. GDPR suggests that legally we lean towards this position as well.

The existence of GDPR suggests that people supporting GDPR lean towards that position regarding data held by companies. Leaving aside that not everyone supports (or is subject to) GDPR, that doesn't justify controlling individuals.

There are arguments for addressing the power asymmetry in mass data collection. Those arguments do not extend to individuals communicating with each other, and they certainly do not extend to forcing those individuals to use technological measures that reduce the amount of control those individuals have over their own devices.