Recently I was locked out of my own Ghost blog platform because they decided they were going to add Email 2FA. I also cannot add any other authors because that requires email verification.

Today I was looking at installing Bonfire and came across this:

Bonfire requires working email for user signups, password resets, and notifications. Most installations will need email configuration before the instance is usable.

Setting up email is a pain in the ass, costs money, is dependent on 3rd parties, violates privacy, and is just completely unnecessary. Why wouldn’t you give users the option to not use it? It’s infuriating!

  • stoy@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    8 days ago

    Most people have no idea they exist.

    That is my point.

    If you write software, and need a way for it communicate with the user outside of the app, implementing email is simple, just about everyone with internet access has an email address and it is free.

    XMPP/Matrix is a lot of added work that will only benefit those who:

    1. Knows what they are and
    2. Has or are willing to set up an account and
    3. Care enough about it to do that rather than just using email.

    I think you will find that the groups of persons who all three critera fits is vanishingly small.

    So, please tell me why a developer should focus their time doing that rather than building the core features of the app.

    EDIT:

    I write this as someone who has used Jabber/XMPP and Matrix in the past, they are great services and I wish they had a longer reach. This is not a hill for you to die on.

    • artyom@piefed.socialOP
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      8 days ago

      So, please tell me why a developer should focus their time doing that rather than building the core features of the app.

      It’s a whole lot less work than configuring email.

      How much work do you think it is to add a toggle that makes email optional?

      • IsoKiero@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 days ago

        It’s a whole lot less work than configuring email.

        It’s a crapload more work to support XMPP/Matrix/whatever messaging on any platform than just using a robust, reliable, resilient, widely supported good old SMTP. For you it might be easier to input your account (which at least on XMPP resemble quite a bit of email address) but for the developer it’s totally different thing. Also practically everyone accessing a website has an email address and if they’d decide to support some mesaging platform it’d make more sense to use whatsapp than XMPP since it’s vastly more popular.

        • artyom@piefed.socialOP
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          1
          ·
          8 days ago

          It’s a crapload more work to support XMPP/Matrix/whatever messaging on any platform than…SMTP

          It’s absolutely not.

          it’d make more sense to use whatsapp

          It’d make far less sense considering both the fact that it’s a Meta-owned proprietary data collection and advertising product, and also that they simply don’t support such a functionality.

          • IsoKiero@sopuli.xyz
            link
            fedilink
            English
            arrow-up
            1
            ·
            8 days ago

            It’s a crapload more work to support XMPP/Matrix/whatever messaging on any platform than…SMTP

            It’s absolutely not.

            And you know this since you’ve written code to manage both on different environments, right?

            Also, whatsapp supports all kinds of “bots” and it has absolutely massive userspace compared to pretty much any other instant message application. It doesn’t matter if you create the perfect protocol and platform for this kind of thing if there’s 7 people globally using it.