[–] 5 points 2 months ago (1 child)

The post link works for me in Firefox, Vanadium (degoogled Chrome), and WikiReader. The link in the post body gives the error described.

It looks like the post formatting is reading the URL as an unescaped string and escapes the percentage marks that already did that in the string.

The post link is: https://en.wikipedia.org/wiki/Ramanujan%E2%80%93Sato_series

But the version in the body is this: https://en.wikipedia.org/wiki/Ramanujan%25E2%2580%2593Sato_series

So yeah, it looks like it got double-escaped somehow.

https://en.wikipedia.org/wiki/Percent-encoding

  • source
  • [–] 5 points 3 months ago (1 child)

    Not sure about the issue in Thunder, but loading slrpnk.net in my browser is extremely slow on establishing TLS connections even before the anubis check comes up. If I had to guess, Thunder is either timing out connecting, or however anubis is configured on this instance, it's blocking access from Thunder.

  • source
  • [–] 3 points 3 months ago

    Interesting that slrpnk.net comes up as one of the autofill options in the textbox when you start typing. But, as you say, Thunder still indicates that it "does not appear to be a valid instance" for some reason.

    I assume that means that this Lemmy instance is hardcoded into Thunder as part of an a array of popular/common instances, but that something is "wrong" on the server side and slrpnk is not announcing itself in a way that Thunder is expecting.

  • source
  • [–] [S] 2 points 4 months ago

    One of the big problems for me while experiencing that issue was that it was not actually throwing an error. It just... wouldn't log in, and would instead just go back to the previous account that I was logged in as. It was not providing any sort of error message, and it was not crashing so I could not see a crash log or something.

  • source
  • parent
  • context
  • [–] 2 points 4 months ago (1 child)

    Hey there, sorry for the late response and I'm glad you were able to sort it out!

    Thunder does expect instances to report back version numbers using semver otherwise it could throw an error. I'll look into relaxing that constraint in future versions to prevent this from happening!

  • source
  • [–] 2 points 4 months ago (1 child)

    I appreciate you labeling it screenshot lmao

    Its funny looking but it genuinely is super disorienting scrolling past a screenshot of a lemmy app within a lemmy app 😅

  • source
  • [–] 4 points 5 months ago* (1 child)

    I've noticed this only happens after opening and zooming a picture in a post. Only way to fix it is to close the app. After opening the app again everything is back to normal until you zoom a picture again.

    I think the app is going full-screen when you zoom in on a picture and not returning the navigation bar like it should when you close the picture again.

  • source
  • [–] 1 point 5 months ago (1 child)

    Hey there, could you provide some more details on the issue? For example, the instance you're connected to, where you're experiencing long loading times, the Thunder version you're currently on, etc.

  • source
  • view more: next ›