I get time out on every single post I make and have to refresh the page, also every time I sign in.
You must log in or # to comment.
Give it some time. Devs have had to go from a nonexistent community to tens of thousands. It will take some time to iron out the kinks especially with distributed open source developers. As for ‘soon’ I’d say probably a week at the absolute minimum. Growing pains of a new technology
True fact bud
I guess you’re right. I’ll try switching instance and hopefully that will help.
Maybe try migrating to a smaller instance? Lemmy.world is massive so that may be a part of it.
Would that help? I tried signing up to Lemmy.ml since I want to post on beehaw too but it timed out and didn’t let me join.
lemmy.ml is also very large, so I would look for something smaller. you can try vlemmy.net It isn’t that small, but it seems to have 100% uptime from stats.
Okay then. I’ll try vlemmy. Thank you.
lemm.ee looks good too.
I’m on a smaller instance and it’s super snappy.
It did for me. Had constant timeouts on some other instances I tried. Then I switched to FMHY, and now everything works smoothly.
Kbin.social is currently federated to lemmy.world.and seems ok
Same here, although it’s only like 90% of my posts. I figured it must be on my end, but I guess not.
I know there’s been a spike in users but like cmon. Lemmy has been running for like 2 years. Hexbear has just migrated over and all of their users are already complaining that the site is terrible.
Sure it’s been around for a few years, but with a consistently small number of users. With the massive influx of people over the past few weeks, it’s going to take some time to scale up resources to match the new demand. Plus, the code base has never been tested under this kind of load, so I’m sure there’s room for improvement there as well.
Short term fix would be to join a less crowded instance, or start your own.
Heck, if people are willing to help fund it, I’d gladly create an instance.
First of all, it’s had a tiny userbase, which is why it’s been buggy.
Second, yes there are improvements planned. I believe the next major version is supposed to be pushed out next week and will fix quite a few issues.
Third, even after next week there will still be some issues. That’s the price of being an early adopter. If lemmy.ml is really unstable try an account on another instance. lemm.ee and lemmy.fmyh.ml has been really good so far.
Try other instances: https://github.com/maltfield/awesome-lemmy-instances
For finding communities I recommend lemmyverse.net over browse.feddit.de; the former is more consistent
Kbin is working better for me than lemmy atm so I browse from there a lot.
the major issues I have with the platform are very minor things but are more QoL issues:
- up/down voting on a post or comment doesnt always happen - however, if I open the post or the comment thread in a new tab, I can see that it did occur.
- delays in displaying that a comment was successful. sometimes the above method works, other times it doesnt. sometimes the comment will just not go through and I’ll give up.
- notifications for new messages do not disappear from the top bar when I have read them, I have to refresh the page.
other than that, lemmy seems to be a very stable platform. hopefully 0.18 fixes some of these issues.
What’s funny is I experienced all of these issues on the reddit app too
Regarding unread replies, this system is actually better. It does remove the notification if you reply back to that message, but leaves as unread if you don’t. On reddit I often got into a situation where I navigated away from my unread messages before I’ve read them all and lost that list as a result. That was super annoying.
This system requires you to manually mark messages as unread, if you have not replied to them.
Remember Reddit used to go down all the time too, but it will improve.
In theory it should improve, but Lemmy.world getting slammed with a ton of new users all of a sudden really made things bad. It’ll take some time to figure out a good solution (e.g. Implementing a way to migrate users to other instances).
Just gotta be a little patient 🙂
