• manucode@infosec.pubOPEnglish
    4·
    11 months ago

    Jerboa does also seem to have problems with this post. There it doesn’t even show up in the feed of the community to which it was posted.

  • manucode@infosec.pubOPEnglish
    3·
    11 months ago

    I tested a few more apps. Here’s my summary:

    Visit beehaw.org/c/gaming :

    • Eternity: post shows up
    • Sync: post shows up
    • Voyager: post shows up
    • Jerboa: post doesn’t show up
    • Boost: post shows up
    • Connect: post shows up

    Open post via beehaw.org/c/gaming :

    • Eternity: app crashes completely
    • Sync: displays post
    • Voyager: displays post
    • Jerboa: not applicable
    • Boost: displays post initially, then either crashes to previous post or completely
    • Connect: displays post

    Open post via link:

    • Eternity: crashes to previous post
    • Sync: displays post
    • Voyager: displays post
    • Jerboa: opens post externally in browser
    • Boost: displays post initially, then either crashes to previous post or completely
    • Connect: displays “Error: unknown” and “1471762@infosec.pub unknown” (instance name infosec.pub changes when opened via a different instance)
    • hulemy@ani.socialEnglish
      5·
      11 months ago

      OP of that post here. It breaks on Boost for Reddit too, I made the post using the web interface. This is the content of the post:

      ![](https://i.imgur.com/2ZosESG.jpeg)
![](https://i.imgur.com/y6VIk4W.jpeg)
![](https://i.imgur.com/X0C6Q97.jpeg)
![](https://i.imgur.com/HcGiViy.jpeg)

      I don’t know what causes it, although it shows some  symbols in Boost before crashing.

  • hulemy@ani.socialEnglish
    2·
    11 months ago

    I left this comment on the Boost thread too, but they’re 9-11 mb images with 9248 x 6936 resolution. I think that’s most likely the problem