• liv@beehaw.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Yes, it’s a massive level of cringe.

        Gmail is convenient, but if it’s about to be filled with 😊 and 👍 then I’ve got to stop using it for any serious communication.

    • falsem@kbin.social
      link
      fedilink
      arrow-up
      15
      ·
      1 year ago

      I work at a large company so get a lot of emails. This could conceivably cutdown on the amount of “Nice job!” type emails that don’t really have much substance.

    • SteveTech@programming.dev
      link
      fedilink
      English
      arrow-up
      11
      ·
      1 year ago

      Outlook has had this for a while, and I use it a fair bit to acknowledge that I’ve read the email, but without actually replying.

  • emptyother@programming.dev
    link
    fedilink
    arrow-up
    23
    ·
    1 year ago

    Eh… They chose to use the email protocol to send each emoji?! So external users or third-party clients (or school and work accounts for some reason) will be spammed. Won’t a bunch of gmails get marked as spammers then?

    • There’s an RFC for this, similar to how there’s an RFC for responding to RSVPs. Some mail clients (Outlook) decide to hide them or show them with a bunch of details, others will give you the plaintext description of the RSVP response.

      In this case, if your email client doesn’t support the RFC, you’ll get a single email in the mail thread with an emoji (if viewing plaintext mode) or, more likely, a description like “Steve responded with 🔝” from the HTML MIME part.

      As this is legitimate mail (that notably is a reply to another email with a valid message ID for the recipient) I don’t think has any spam implications.

        • Skull giver@popplesburger.hilciferous.nl
          link
          fedilink
          arrow-up
          8
          ·
          edit-2
          1 year ago

          RFC9078, which is currently experimental but still standardised.

          There’s no need to change standard for email because of its extensibility through headers and MIME types, so I don’t think the RFC needs to be upgraded all the way to Internet Standard for it to be relevant in this case.

          I think this is an incredibly silly standard, though. I don’t see the need for emoji reactions under email and I doubt it’ll solve any real world problems, but the people who do see value in it may as well use it.

          RSVP stuff is done through RFC 5545 and its many updates, I believe, though there’s also an RFC for resource reservation which has RSVP in its title.

          • Chobbes@beehaw.org
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            Thanks :). I’ve actually been looking for the RSVP stuff and I wasn’t sure which RFC to look through (wasn’t sure if it was in the CalDAV one or the iCalendar one… and they’re weirdly huge). I appreciate you pointing me in the right direction!

            Also was curious how they were implementing reactions in e-mail. I actually think it’s a good feature, and it’s one that’s slowly been making it into XMPP and stuff. Emoji reactions and stuff sound kind of dumb and like a “whatever, who cares?” feature, but I find that on platforms like slack they’re actually a really good way to deal with quickly confirming something / finalizing decisions / quickly gauging the opinion of a group. I think a huge problem with e-mail and instant messaging is that they can be quite noisy, so having a “quiet” way to respond without having a thread explode is actually pretty welcome in my opinion.

  • SLaSZT@kbin.social
    link
    fedilink
    arrow-up
    12
    ·
    1 year ago

    I’m struggling to think of a use case for this. Why not just reply and put an emoji in there?