87
Wefwef feels the most polished of the apps so far, but only when it works. Almost every other time I try to use it posts won’t load.
(media.kbin.social)
Wefwef feels the most polished of the apps so far, but only when it works. Almost every other time I try to use it posts won’t load.
Closing and opening it, making sure it’s updated and even restarting my phone sometimes won’t fix it.
How’s reliability for others?
It’s more likely an instance issue rather than a wefwef one. Try signing up into another one. Also, it’s time to charge your phone
Definitely an instance issue. I have zero problems with mine (Lemmy.one)
Same, also from .one. Move to a less overgrown instance. Spread out a bit, people! 😁
The app is shitty dealing with the shitty server performance. Instead of working with timeouts and waiting for a 200 the app just dies. There are better ways to gracefully fail. Especially on these broken ass servers.
Somebody needs to start making people pay for servers but nobody here (not you) wants to havea real conversation about how to pay for costs.
Actually, I'm guessing wefwef is using the J's client, which usually returns a 503 or 500 when something goes to shit on the instance.
I'm also developing an app for Lemmy and the only solution I found was to just keep request the data until the instance finally gives in to the pressure and works.
So it's less about "server is taking too long to respond" and more like "server responds instantly with a 503" because it's overloaded and can't handle any incoming requests.
I'm also guessing a lot of traffic comes from comments since the way of loading those is kinda stupid. (You load only the top layer and then for each comment you request the children, which sums up to a huge number of requests).
Lemmy should add more convenient APIs to reduce the amount of requests being made, maybe I'll do that myself once I'm done with the app.
Sorry for the long ass text.