Hi Beeple, here’s a list of current bugs after our upgrade.

  • There are issues trying to login or log out. To fix this, please clear all your cookies and site data for Beehaw.
  • Image uploads don’t seem to work

Feel free to comment here if you have any new bugs.

It is currently late and so, we are trying to sleep. Thank you for your understanding.

  • hedge@beehaw.org
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    I’m having a problem where my upvotes won’t take, and also I keep getting shown that I have unread messages when I’ve read and marked them already.

    • Annies_Boobs@beehaw.org
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      I’m going to tell myself this is why I’m not getting upvotes and it’s not because I’m entirely uninteresting lol

    • wieders@beehaw.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      What I’ve seen is that the upvote will blink in then out. Awhile later (like 10 seconds later) it will show as having the upvote again. I’m just learning to trust that the button worked and move on now 🙂

  • b9chomps@beehaw.org
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    Not a bug, more of a PSA.

    When you setup 2FA, there is no mandatory verification step in Lemmy 0.18 for now. That means you can log out without setting up 2FA in your app or software correctly. Be careful or you might lock yourself out of your account permanently.

    • derelict@beehaw.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Having worked on programming auth stuff before, that is absolutely a bug. It may stem from a mistake in planning rather than one in implementation, but that is unambiguously the wrong behavior.

    • argv_minus_one@beehaw.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Stuff like that is why I avoid 2FA wherever possible. It doesn’t significantly improve my security because I always use unique random passwords, and it does create the risk I’ll be locked out of my account.

  • Witch@beehaw.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Wasn’t permanent but there was a brief few minutes where I didn’t have anything pop up in the subscribed communities, —refreshing it then gave me that “we’re working on the site” bug page. Back to normal now!

    Doesn’t seem to be a major issue, but figured I’d mention it in case that pops up for anyone else.

  • Sinfaen@beehaw.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Does this also apply to the Firefox PWA on Android? Whenever I hit the icon a window briefly appears but then it dies

    Regular Firefox works though

  • FlopsyM@beehaw.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I’ve been finding that occasionally the feed or comments will pop back to the top of the page, meaning I have to scroll back down to find where I left off reading. I’m using chrome on android, if it helps.

  • FelipeFelop@beehaw.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    I seem to be logged in but I can’t vote or comment and there doesn’t seem to be a way to search. I’m nervous to log out and in again because of the login bug.

    Edit: changing avatar gives a JSON error

  • Storksforlegs@beehaw.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    I realise this isn’t something that can be controlled by the beehaw crew, and it’s not exactly a bug…

    but has anyone else found it extremely easy to accidentally delete posts while going to select ‘edit’ on mobile devices? (since ‘edit’ is directly beside ‘delete’?) Maybe it’s just me but this keeps happening hehe

    Is there anywhere to post feedback to the folks in charge of Lemmy’s UI arrangement?

  • abhibeckert@beehaw.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    FYI Beehaw is currently broken entirely in Safari. The main API response to return the content for any page is failing with “Unexpected EOF” and inspecting the actual source code the response terminates with an invalid UTF-8 character in the middle of some Chinese characters.