There is currently something going on over at Lemmy.world causing authentication issues. This isn’t a memmy specific issue but is also plaguing the PWA. https://lemmy.world/post/1364490
Until this is fixed, the best bet it to just keep “retrying”. This would explain some of the issues I thought were linked to issues inside the app but might be something else.
I have an update ready that will fix a bunch of these internal issues with the app, but unfortunately it’s going to break Lemmy.world terribly for anyone using it, so I’m going to hold off on releasing that until they figure out what is going on.
I keep getting signed out of Lemmy.world as soon as I log in. I’m not sure if this comment will even post by the time I’m done typing.
Confirming that I am able to browse using my lemmy.world account, but upvotes keep failing intermittently and posting says I’m logged out after I login. Wonder if the hackers changed something on their way out.
Seems to work if I clear cache before commenting.
If there is one thing that is going to shitcan Lemmy it’s when the most popular instances of communities are on a server that is as stable as a Qanon voter from Georgia.
That’s bound to happen though. Definitely not just a server problem. Lemmy.world is basically stress testing the Lemmy code. Having to scale from hundred of users to hundred thousands during the course of a month is obviously going to mean issues.
Some due to world, some due to bugs in Lemmy and some due to efficient ways to run an instance is still being found out. Sooner or later it had to happen.
I still think lemmy and it’s likes are still getting a lot of core issues worked out. This feels like beta software and with the major version being 0 it’s understandable for me. I think a disclaimer that the tech is new and may have issues would help with keeping people from writing it if entirely.
Same here on the Voyager web app. I just got the Memmy app and it seems to be slightly more stable for the past few minutes, FWIW. I just started this account today and thought it had to do with signup delays.
