• KairuByte@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    16 hours ago

    App or website? They’re talking about rolling their own code to interface with the public API of whatever service is being talked about. That’s a boatload of effort to fix something that shouldn’t be a problem to begin with.

    • explodicle
      link
      fedilink
      English
      arrow-up
      1
      ·
      15 hours ago

      I mentioned rolling my own code because we weren’t yet discussing the average user. Iff the time has come to make it easy for the average user, then I’d want to create an app or website instead.

      • KairuByte@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        12 hours ago

        Which would in turn require revenue for hosting and development. Meaning either ads, or monthly payments.

        I’d rather not pay you for a service which shouldn’t need to exist. And it could be done away with by requiring an easy “cancel subscription” button which requires no hoops to go through.

        • explodicle
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 hours ago

          You’re already paying for automated payment infrastructure; it’s just included in the price of subscription products.

          The cancel subscription requirement is also very reasonable IMHO. But that makes it difficult for average users to see how many subscriptions they’ve got active; who’s currently authorized to withdraw money from their account. The default remains keeping the subscription active.