Live data from Hacker News

Stop Microsoft users sending 'reactions' to email by adding a postfix header

neilzone.co.uk

41–50 of 377 posts

Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header

#41

Earlier quoted context omitted.

With a thumbs-up I know they've read it, and that's worth quiet a bit in this asynchronous communication world of ours.

We used to (and I believe still) have Read Receipts for this.

Yes! +1 And it's possible to disable Read Receipts and a lot of people do. A lot of people mangle beacon pixels too.

Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header

#42
post #4

Oh, this is good to know! I haven't encountered this issue personally yet, but maybe once I've updated my mailserver, I won't encounter it in the future. Now to figure out how to stop the same thing happening in SMS.

You'll be glad to hear that SMS already doesn't have reactions

If you're texting with an iOS user and they use a reaction, Apple "helpfully" forwards the reaction as text. Which is OK. What I don't like is that it also quotes the complete text that the person reacted to.

Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header

#43
post #22

Earlier quoted context omitted.

This is cute, but not how email communication works. There's no need for explicit answer to any email, otherwise people would never stop responding.

> not how email communication works. There's no need for explicit answer to any email Obviously context dependent. For time-sensitive emails, it’s common to follow up with a call if receipt isn’t acknowledged.

Be sure to CC everybody. /s No. The technology isn't built for this.

Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header

#44

I kind of get why we don’t like this in email, but for SMS and Slack I’ve thoroughly enjoyed reactions. They’re a way to say “I received this and have a positive reaction to it, with no further communication necessary”. Replaces a lot of useless typing I had to do to sound polite when saying “fine, no further comment”. And then getting a notification from the other party acknowledging my acknowledgment… yuck.

It should be entirely socially acceptable to respond to any trivial message with "ACKNOWLEDGED" á la Picard

I agree. Also, if the message proposes any action, it should be appropriate to reply with "Make it so.".

Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header

#46

Earlier quoted context omitted.

With a thumbs-up I know they've read it, and that's worth quiet a bit in this asynchronous communication world of ours.

We used to (and I believe still) have Read Receipts for this.

Oh yeah, the thing I always turn off or filter out because the last thing I need is another way spies and hackers and ad men can track every waking moment of my life.

Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header

#47

Can an anti-reaction person explain what they find so distasteful about them? Is it that the other person wasn't willing to make the effort to type is seen as disrespectful? struggling to see what the problem is

In email, it would just be an annoyance that bulks out the inbox. Not a huge deal, but filtering them out would improve the experience.

Reactions make more sense to me in a kind of communication where you're doing real-time conversational stuff and brevity is important, such as instant messaging. In email, it doesn't really add anything.

Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header

#48
post #39

Earlier quoted context omitted.

SMS is being replaced with RCS, which does have reactions…even Apple is adding RCS… Welcome to the future.

RCS is already here on Android, but I keep it disabled in order to avoid read receipts and typing indicators.

You can disable read receipts and typing indicators without disabling RCS

Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header

#49

Earlier quoted context omitted.

Genuine question: why?

This question is how we get opinionated software that slowly-but-surely stops serving the user. "I don't like it" should be a perfectly valid reason for turning off a feature.

Except, by turning them off, you are therefore forcing people who want to communicate with you to adapt to your communication preferences because you have, by fiat, decided that you simply don't want to perceive the communication method they prefer. Coming to an agreement with others about how you want to communicate with them as fine, but communication is a two-way street, and so it has to be bilaterally negotiated by both parties, in which case it is very fair for someone to question your decision to unilaterally force everyone around you to change how they communicate by simply deciding to stick your head in the sand regarding one channel of communication. I find emoji reactions to be a much more efficient, direct and low boilerplate way of communicating, sometimes quite relevant and important information, and I would be extremely frustrated to the point of disgust if someone decided to simply turn them off and not perceive my reactions, thus forcing me to come up with polite non-phrases lile "looks good to me" to express the same reaction.

Also, I think this philosophy that all software must be infinitely configurable, so that it can serve every whim of every possible user, and that if it has a clear idea of what it wants to do and how it wants to achieve that, and sometimes that way it is designed to be used, it's somehow unethical or abusive of the user or something, is the fundamental sickness at the heart of open-source software design. It turns programs into unclear bloated piles of buttons and switches that are overcomplicated to use and impossible to properly quality assure and impossible to design in a coherent way. For powerful professional creation tools (CAD software, publishing, programming, etc) that will be the primary software used for decades by experienced and educated professionals who will want to optimize their workflow and who have the time to invest in deeply learning that one specific tool, then I think that philosophy is fine, but for random chat apps and stuff, it's just frustrating.

Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header

#50
post #15

Earlier quoted context omitted.

The UX problem is you send an e-mail, and someone "thumbs up" a response, and then you block the response and assume that they didn't care to respond, while they think they have responded.

No. When you block an email the sender will get a notification email from their mail server that their message was blocked. They will not assume anything for very long.

That's email server dependent. When my mailserver blocks emails, it just drops them onto the floor. The sender doesn't get any sort of notification.
Post reply on HN