Apple added the same thing for iMessage/SMS. It worked as expected if the group message was all Apple users. But if you were the unfortunate person outside the ecosystem, you would get spammed with ‘{person} liked “{message}”’. In some cases, people would react to the reaction leading to some ridiculous chains of text.
As an Android user, I often wonder if Apple users realize how stupid their replies look to non-Apple users. I wonder if I should tell them or just move on.
Stop Microsoft users sending 'reactions' to email by adding a postfix header
321–330 of 377 posts
Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header
#322Earlier quoted context omitted.
Would it be better to have an op-out database, where you have to log in with a Google account, and prove that you own the device somehow using geolocation? The system has to be resistant against bad actors taking someone else off the map who chooses to opt in. It would be better if the syntax were simpler, like changing myhouse to __myhouse (double underscore == private identifier). By setting SSID a certain way, you…
no it would be great if you had to prove you own the device to opt-in.
Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header
#323Earlier quoted context omitted.
I like how you word this in the past tense, it still happens to this day. I live outside the states but keep a google voice number and in my family's group chat I still get these all the time. I've mostly (miraculously) moved them to Signal, but they revert to their SMS ways occasionally.
RCS is finally coming to iOS though, so soon this should be resolved.
Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header
#324Earlier quoted context omitted.
I literally had to set up a “Congratulations / Congrats” filter to auto-delete those emails because they were so frequent and numerous when various accomplishments across the org were announced. The party popper emoji at least makes that far more tolerable.
I see a lot of those too, and I am confused at the purpose. Clearly congratulations are warranted, but it would be much less wasteful of everyone's time if those were sent directly to the person being congratulated, rather than to the entire org / company / world. Is this just the sender looking for visibility? Does the recipient appreciate that yet another middle manager CC'd the whole company on a single sentence c…
Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header
#325Earlier quoted context omitted.
I see a lot of those too, and I am confused at the purpose. Clearly congratulations are warranted, but it would be much less wasteful of everyone's time if those were sent directly to the person being congratulated, rather than to the entire org / company / world. Is this just the sender looking for visibility? Does the recipient appreciate that yet another middle manager CC'd the whole company on a single sentence c…
I've thought about this a lot in terms of meetings that don't have to be meetings at my org, and I think it's essentially an adherence to protocol that communicates a kind of mutual awareness and respect for the performative expectations everyone is operating under. Put differently, it's a kind of "parliamentary procedure": specific rules and expectations that everyone follows in the workplace to keep things "profess…
Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header
#326Earlier quoted context omitted.
I read that as “party pooper” - I want that as a reaction emoji.
Have a few too many drinks at the christmas party and go for it.
Party: pooped.
Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header
#327Earlier quoted context omitted.
Be sure to CC everybody. /s No. The technology isn't built for this.
I'm pretty sure a large number of e-mail conversations (i.e. not just announcements) end in one person saying, "OK", "Will do", "See you then", "I'm too busy, sorry" or some such response. It's very uncommon to send out an e-mail to someone and ask them to do something or consider something and then assume it has been received without acknowledgement.
I'm being surrounded right now by examples in multiple domains where it is clear that the moral of the story is that one person taking an action is different than a company packaging that action up and selling it as a solution to a general problem. This seems to be a lesson which needs to be generally remembered, explored, and learned. Again.
While one person responding "will do!" is appropriate 1:1, it is typically not appropriate to /reply all/ when doing it or to reply to a distribution list when doing it. I mean there are exceptions to everything: "Reply 'will do!' to this all-staff@ message or you're fired." But generally it's a meme, an anti-pattern (and there, I did it again).
Many people have built autoreply systems for email to respond with helpful advice to frequent topics. (Happy to help, I've done it before.) Similarly email clients (MUAs) which have macro / scripting capabilities for filtering or replying are not new.
What's new here? If it can be called new, it's that somebody provided that macro capability and linked it to an optional email header the sender can provide which enables / disables the ability to run macros in the client. In theory; or something. We (or at least I) don't know if it's possible to add your own macros.
I imagine this comes with tools in the client or in alias management to manage "reply all" / "me too": in other words it might be possible for someone to disable macros when responding to messages sent to all-staff@. I expect other extensions which reach across boundaries of control to follow if this one floats, and that's why I consider it a shitshow.
Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header
#328Earlier quoted context omitted.
I've thought about this a lot in terms of meetings that don't have to be meetings at my org, and I think it's essentially an adherence to protocol that communicates a kind of mutual awareness and respect for the performative expectations everyone is operating under. Put differently, it's a kind of "parliamentary procedure": specific rules and expectations that everyone follows in the workplace to keep things "profess…
Well shit, I haven't been going to the all-hands either!
Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header
#329Earlier quoted context omitted.
Not everyone embraced it. I still use a plain-text email client.
In case you haven't realized, you're the odd one out, today, in 2024. I don't mean this in a negative way - I just mean that you're out of what's usual.
I can't think of a single person I know that uses a text-only email client (and yes, I know more than one of them) who isn't what you'd call a "power user".
All of them know that most people don't use a plain-text email client, they just prefer to use one themselves.
Re: Stop Microsoft users sending 'reactions' to email by adding a postfix header
#330This is the "extend" part of "EEE", where companies try to make it a nuisance to not use their products based on a standard tech stack.