It's been a long journey since we announced this back in December 2021. Welcome to the new Hexbear!

If When you encounter a bug, please report it here. Please give us as much detail as you can (how to reproduce the bug, the platform/browser you're using) so it's easier for us to fix!

Known Issues
:

A list of issues, not exhaustive or in priority order. We're looking into all of these and will be deploying a variety of hotfixes over the next few days/weeks with fixes.

🚨 A lot of these are bugs that exist in upstream Lemmy 🚨

  • On some errors, infinite rotating spinner with no error message
  • Includes resetting password via password reset link
  • Can't navigate away when text is entered
  • Issue logging out if initial pageload was not on homepage
  • Reporting posts does not work in portrait mode on mobile. Temporary workaround: rotate to landscape mode
  • Jerboa broken due to api changes
  • Inline gifs/images are able to render way too big
  • portrait mode for tablet width/aspect ratios probably should not show sidebar, too much wasted space.
  • disabling "Show Read Posts" in user Profile hides featured/pinned posts from the homepage
  • Highlighting then clicking reply to automatically quote includes "undefined" before the quote.
  • Sitewide Featured Post titles turn blue when moused-over, becoming illegible on the blue background
  • comment permalink is too easy to misclick when aiming for upbear or username.
  • Post shown occasionally changes out from under you while browsing, comments remain the same

If you are open to volunteering, we are looking for frontend developers who can help figure out and fix some of these UX issues. If you think you can help, please send Layla a message on Element (@layla:chapo.chat). 

None of this is possible without your continued support. If you enjoy the site, please consider donating via our Liberapay or Patreon :hexbear-retro:

Edit: sorry for the second spurt of downtime folks, we are trying to solve the performance issues

    • WhyEssEff [she/her]
      ·
      edit-2
      2 years ago

      the original dprk-soldier jpeg, as it shouldn't, does not upload

      mao-clap

          • PorkrollPosadist [he/him, they/them]
            ·
            2 years ago

            I'm pretty sure the actual file they tried to upload was absolutely massive. There was a bug in pict-rs which allowed malformed jpegs to consume enourmous amounts of disk space leading to DOS attacks. We were the first time it happened. It has since been fixed.

            • WhyEssEff [she/her]
              ·
              edit-2
              2 years ago

              It’s the original jpeg, I got it directly and rendered it on my last computer to reproduce the image. The bug was that pict-rs would get stuck on attempting to render it (because it could be rendered, technically, with a lot of time) and it would cause a memory leak.

    • solaranus
      ·
      edit-2
      1 year ago

      deleted by creator