I don’t know if it’s a problem on my end but today I’ve got the following error several times while reloading pages:
404: FetchError: invalid json response body at http://lemmy:8536/api/v3/siteI have to quit the browser and wait a few minutes before I can connect again. Never happened before.
I’ve also been getting these.
I don’t know if it’s a problem on my end
These are internal failures with lemmy-ui talking to lemmy_server and not understanding it got an error message or timeout back. Not on your end. Every busy Lemmy instance I’ve been testing on has these problems right now.
another cause of the infinite spinner: you are trying to sign in, but you haven’t verified your email address yet. solution: check your email, click the verification link that was sent to you.
The content of one instance can be very out of sync with another.
Example, this thread in kbin is visible here in lemmy.world, and at the time of writing, not even a 3-day-old comment shows on lemmy.world.
I have been subscribed to this community from beehaw in lemmy.world for those 3 days, which as far as I’m aware is the only pre-requisite to sync. But if syncing takes longer than 3 days…
Thanks for all the work to keep the community running, Ruud!
Do you already know when Lemmy.world is gonna be running lemmy 0.18?
Seconded re. Lemmy 0.18, just because the latest Jerboa release won’t support Lemmy.World until it’s updated.
deleted by creator
Is outbound federation a known issue?
I’ve just tested inbound from sh.itjust.works and it was instantaneous. But my outbound posts that have worked take hours and none have succeeded for days.I’ve had problems with posts not showing up on sopuli.xyz, so I’m guessing outbound.
Here’s a similar report, this time with feedit: https://lemmy.world/post/440406
Top comment by @Wander@yiffit.net says the new version coming tomorrow fixed this issue. Guess we’ll see.
I dunno. Can’t see any of that in Lemmy. So I’ll have to test if it’s our outbound or sh.it’s inbound.
Understood. I’m not just trying to get content to sh.itjust.works, though. outbound from here to .ml, kbin, and fedia have all failed. I’ll test kbin inbound.
kbin is not instantaneous. It has not appeared and I assume, due to instability, is likely lost. If it comes through I will update with time.
The kbin test comment posted there 4 hours ago according to time stamps. So 5 hours from previous comment
If you write a post, preview it, and want to edit it some more before posting, you do so by clicking “preview” again. That is confusing and took some figuring out. The “preview” label on the button should change to “continue editing” or something like that, while in the preview state.
As of right now (post-18.1 upgrade), when I visit https://lemmy.world/post/848519 it says I have to log in to comment, and the upper right of the screen has a login link. But I’m already logged in, the screen indicates that when I click the login link, and other pages also show that I’m logged in. Quite a few page refreshes don’t change this. I’m about to clear cache and cookies and log in again, but this is weird.
Also still seeing lots of backend timeouts and slow responses, plus I somehow got logged out again (I logged back in after a few tries).
I begin to hate Lemmy’s web front end, because it uses so much asynchronous network stuff. The success path works somewhat ok when things are fast, but when things are slow (even if you don’t hit an error), you can never tell whether the screen state has caught up to the server state. We need an old fashioned synchronous front end, so if the browser says that a page has finished loading, you can know that what you see on the screen is the final state of the page.
Just wanted to say thanks Ruud for all the work and expense. Your diligence is obvious. Thank you.
