If this is an entirely corporate offering, with supporting EULA - you could accept it as simple monitoring requirements. But without that clear separation of corporate, and potential end user devices, this feels more to me perverse - like spying - than anything.
You are removing the right for someone to make a mistake.
That being said; the idea of a system to which a conversation is mutually engaged (“contract”), but to which a single party can immediately and entirely redact their contributions is flawed at best.
Feels like some kind of in-between is required - hopefully with clear end user understanding.
Being able to see the original message someone shot off in anger and then revised into something nice is really handy as a manager. Especially if the entire team is remote and you can't tell things by body language.
You aren't stopping them from making a mistake, and you aren't even stopping them from removing evidence from their PoV. You're merely retaining all communication on your side.
I understand OP's sentiment, and even share it to a degree.
It's 50% FOMO, and 50% a certain arrogance of "It made it to my client desktop, the bits are HERE, therefore they're mine now. How DARE you reach out remotely and remove them." Feels like a violation.
But these feelings are silly, and life is too short to worry about such things. There are better things to optimize for and spend time on.
This is a cool tech demo, but anyone who's thinking of using it PRACTICALLY should consider why they also don't root through their building's trash for nuggets others threw out.
We were both into computers so he acted like it was a funny/novel piece of tech but he used it in daily life. Felt like stalkerware. You don't stalk your friends, and you don't violate their consent in the same way that friends dont use a patched snapchat client that disables screenshot notifs/keeps photos. Thats creeper shit!!!
This is documented in this old FAQ https://github.com/Kjir/amsn/blob/master/amsn/FAQ
(Former aMSN developer)
I admit now this is creepy.
Early ICQ didn't even store the contact list on the server so you had different contacts on every PC.
i checked out that "open chat window once someone starts typing" once out of novelty value... but it felt to stalky to keep it active, and wasnt really handy at all. sometimes ppl misclick and open the wrong window and realize later, others are reading past discussions... really not that useful as a feature
(I will admit to an illicit thrill when I click no on the outlook pop-up that informs me someone wants to recall their message...)
A bit mean to systematically retain.
But if my password, or any other credentials, were leaked because someone in a trusted environment was scraping deleted messages, then storing it unsecurely, i wouldn't be impressed.
Worst ever is one of those apps where you do /funny cat and a meme pops up.
Did one once. And this crazy offensive thing popped up. Like sort that can get you fired. Learned that there was no way to delete it.
I hate when that happens.
It astounds me that people use notification sounds for messenger and e-mail clients. How do you get anything done when being repeatedly distracted all day?
I even find them sometimes helpful, they provide short breaks.
If I want to focus hard on something I can just ignore them to check later
First time on medication was surreal oh how I just worked on one thing at a time.
You're confusing productivity with reachability.
I currently have my Slack set to be pretty sensitive to topics that concern me, but that's voluntary. In a previous workplace, Slack was noisy af and I felt pressured to keep it at maximum sensitivity. Of course that just made me more anxious.
I think as a developer it would be very different.
When building a chat system with notifications, it's also important that you can recall notifications. Wouldn't want someone's accidentally pasted password to be retained in notifications.