I’m just getting a “problem fetching posts. Please try again” message. Been happening for an hour or so now
wefwef
wefwef is now Voyager! Subscribe to [email protected].
Same. Might be updating?
Hijacking top comment, update wefwef to fix this. Within wefwef go to settings -> check for update.
I read somewhere that the lemmy.world admin made a change to relieve the load on lemmy.world but that change is causing wefwef issues connecting to lemmy.world.
Lol, after 2 years of owning an iPhone I needed to learn how to force restart it (because it got frozen after launching wefwef). Now my wife is awake because I launched some SOS siren instead 😅
This is due to the update today. We are working with the wefwef dev on a resolution. Look for more info from Ruud on this as soon as we have a fix.
I'm having the same problem. Connect works fine... Not sure what's going on.
It's not wefwef, it's lemmy.world: https://lemmy.world/comment/695639
Edit: there's an update. Within wefwef go to settings -> check for updates.
That link won’t open.
Open it in safari.
Open https://wefwef.app, and inspect the network tab of inspector, I can see that there is a 400
status code response on trying to load https://lemmy.world/api/v3/post/list?limit=30&page=1&sort=Active&type_=All
. In the body of the response I see the message Origin is not allowed to make this request
.
I can get lemmy.ml to load, and it doesn't have this error.
Could this perhaps be related to lemmy.world not allowing requests from the wefwef.app host?
I have no idea what any of what you just said means.
I'm saying that wefwef app is giving us an error message saying that that lemmy.world web server is rejecting traffic from wefwef, so that's why the posts are loading.
Maybe related to user influx due to Reddit 3rd party apps shutting down today?
I think Lemmy.world is getting swamped with new sign ups and traffic. I’m using wefwef just fine.
Yep. I'm using Connect in the meantime
If guess the people telling me there was no difference between wefwef and a native app weren’t 100% correct.
It seems to be fine now using the .1 update 😁