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!

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

    your only options are to code it, or ask someone else to

    I wasn’t asking for options, I was asking for an explanation.

    • porcoesphino@mander.xyz
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 hours ago

      In your OP, sure.

      But this comment reads as a desired state, and in some situations thats a feature request (in this case it seems like there are architecture / system workarounds):

      I don’t want email to be accessible to those services. I don’t want those services to use email at all.

      Did you get an explanation you’re happy with?