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.
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.
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 ( @argv_minus_one@beehaw.org ) English5•2 years 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.
Hey, at least we’re not rate limited.
Or having decisions forced upon us by megalomaniac billionaires.
Nice!
Y’all are doing your best and I appreciate it.
You sleep, we can handle some bugs!
Mastodon had some growing pains in November and December after waves of new users adopted the platform. I kind of expected it to happen here too. No big deal. We appreciate your efforts. :)
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.
I see this as well when I go into post details then back out. Looks like it loses its place when I come back to the main page.
Thanks for all of your work!!!
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.
I’m seeing that a lot lately. Worker Bees are busy with all the extra traffic I suppose.
We probably should accept it for the next couple of weeks.
I’ve noticed I’m spending at lot more time reading books (on Kindle) rather than aimlessly scrolling through page after page of guff on the R site. Success all round 😉
- argv_minus_one ( @argv_minus_one@beehaw.org ) English2•2 years ago
🥵👷♂️🐝💨
- argv_minus_one ( @argv_minus_one@beehaw.org ) English10•2 years ago
On a positive note, the “feed always defaults to local regardless of settings” bug seems fixed, and now that we’re not using WebSockets any more, the “new posts endlessly flooding into the page” bug is presumably also fixed.
Inbox items refuse to mark read. Neither reading them, nor marking read manually, clears the new flag.
flag? as in, the top icon? I think a refresh usually fixes that - obviously not ideal that said.
I meant clears the unread attribute.
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
Same, Firefox app (on Android) works but PWA insta-crashes. I tried removing it, clearing cookies and cache, and hard refreshing via desktop Firefox USB debugging. Got the website (in-app) to actually show a list of posts, but still no PWA.
Same but for Chrome PWA on Android.
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
your comment here seemed to work fine
I was using a different client and account 😊
And I can upvote you. Check your setting as in the PSA and live on the edge!
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.
Is that still true? The closest I have to test is GNOME Web which uses WebKit as well…
Still true, at least for me. Imgur since image uploads don’t seem to work:
All pages look like this in Safari: https://imgur.com/a/yDx9GOl This is the actual “Unexpected EOF” syntax error: https://imgur.com/1WC2yIO
Note I don’t have any issues with another instance that has upgraded, just Beehaw. It does work in Safari if I sign out though.
… and now the problem has fixed itself …
Well, that’s good news atleast 😅
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?
You should check if an issue has already been made but the best you can do is file an issue here : https://github.com/LemmyNet/lemmy-ui/issues
Thank you :)
I made a script that moves the delete button - but I’m not sure what jQuery hook I could use to re-run the script every time comments are loaded / reloaded - since in Lemmy new pages of comments are loaded into the current screen, not a page refresh
https://greasyfork.org/en/scripts/470304-beehaw-lemmy-separate-spacing-of-delete-and-edit-buttons
same issue for my adding the commenter’s instance name to their name script… works on page 1 but not on page 2 …
https://greasyfork.org/en/scripts/468708-beehaw-lemmy-add-home-instance-name-to-username
I can’t seem to get to my profile page at all, clicking on it does nothing. Also replicated this in a different browser that never even touched Beehaw.nevermind, suddenly works!I can’t seem to get to it from the homepage but I can access it from this thread.