• @smoysauce
    link
    English
    4
    edit-2
    1 year ago

    Thanks for this! Just gave this a try, downloaded from .world just fine, but uploading to .ml gives this error: ERROR: Failed Login - HTTP status client error (403 Forbidden) for url (https://lemmy.ml/api/v3/user/login)

    • @CMahaff
      link
      English
      41 year ago

      That usually means wrong username/password! But if you’re sure, I can make an account on lemmy.ml and give it a shot.

      • @smoysauce
        link
        English
        3
        edit-2
        1 year ago

        Thanks for the feedback. The username and password are indeed correct. I copied and pasted from Bitwarden and used the exact same ones to login to the lemmy.ml site. I do wonder if there is some sort of anti-bot measures that Colonel Sanders mentioned below.

        Also: I tried just my username vs email but neither worked and I also don’t have MFA enabled yet. Super weird.

        EDIT: opened an issue on Github: https://github.com/CMahaff/lasim/issues/4

        • @CMahaff
          link
          English
          41 year ago

          I have a fix! Merging the branch and dropping a new release shortly. Thanks for reporting this!

          • @smoysauce
            link
            English
            31 year ago

            Working great. Thanks for the quick fix!

      • Colonel Sanders
        link
        English
        21 year ago

        I’m not very tech savvy when it comes to this, but would it have anything to do with the anti-bot stuff that lemmy.ml has implemented in the sign-up process? You now have to answer a few questions and basically write your reason for making an account before it lets you even submit the request for review.

        • @CMahaff
          link
          English
          4
          edit-2
          1 year ago

          To use the tool you need to make your new account first manually - then you can port over your settings with the tool - so it shouldn’t be affected by this.

          So no, lemmy.ml shouldn’t be blocking it, unless it’s got something enabled to disable all API logins - though I would think that would break everything (i.e. apps).