See title. Then I try to go back but the back button does not exist? I am using Safari on mobile.

  • Awa@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I get them a lot too. I am on the chrome PSA on android tablet. I end up just refreshing the page that turned into the sport post and it goes back to the post I originally clicked on.

  • 00Lemming@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 year ago

    Just so you know this has been reported and is a known issue (happens to me on the browser as well). Presumably, it is due to Lemmy’s use of websockets for API requests, which has its issues for this particular application.

    This has been addressed in version 0.18.0 as, among quite a few other changes, an HTTP API is now in place for API requests which will (should) resolve this issue.

    Lemmy.world is currently on back end version 0.17.4 which still uses websockets. You can see this at the bottom of every page. The reason for this is that version 18 removed the ability to use Captcha for account registration. Given the size of the instance and its rapidly growing user base, and the fact that we are still accepting registrations, we simply must have the ability to leverage Captchas to mitigate the bot spam signups, which has been an issue.

    We have tested the 0.18.1rc build (non-official release) in order to try and get this new functionality as soon as possible, but as you can see in the post 18.1 needs some time to bake still - at least for large instances.

    This is definitely being discussed among the admin/mod team and we will be upgrading as soon as we realistically can while providing a stable - usable - experience.

    • marsara9@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      I’m not 100% confident but I’m assuming it has to do with the fact that lemmy.world is still using websockets instead of the new http pattern from 0.18. If true, once lemmy.world can upgrade to 0.18.+ it should fix itself?