I always find it funny when developers introduce these client functionality kneecaps. This particular one is like security through obscurity. If a message reach

I always find it funny when developers introduce these client functionality kneecaps. This particular one is like security through obscurity. If a message reaches a recipient, there's no reason to believe you can delete it on their end. "Oh, well most people won't go through the trouble" is a lesson we have learned from already. The other one that gives me a chuckle is read receipts and typing notifications. Chat apps put them in (I can't stand them so I turn them off, I don't want to see them or send them) and then they make both the setting to receive them and to send them tied together, like some sort of mommy telling you how to properly behave. "If you don't want to send them then you shouldn't be able to see them, its only fair." But it is handled in the client, a lot of the time a FOSS client, which can be patched. It's kind of ridiculous.