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 heard a few more people who had that. I’ll investigate
Thank you!
I’ve also been getting these.
Just wanted to say thanks Ruud for all the work and expense. Your diligence is obvious. Thank you.
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.
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…
Hmm, the original thread/community seems to be at beehaw.org, right? Since both of the threads you linked to are referring to the community “Programming@beehaw.org”.
Beehaw is even down right now, so I am guessing that any syncing issues with other federated instances might be caused by a bottleneck at beehaw.org…?
I still don’t fully understand how Lemmy works though, so I am not sure.
Beehaw is defederated with lemmy.world, so those posts won’t be updated with the content from beehaw.
Yes, you are right. But it had 3 days to sync. The oldest comment is 3 days old. Here is the same thread visible from another instance, much more up to date. I hadn’t noticed that beehaw.org is down though. That could explain it. I still find it odd that this instance would not have a single comment on this thread over these 3 days but… yeah I’ll take that explanation for the time being, I’ll check again when I notice beehaw is back up.
Do you know how the fediverse works regarding this?:
- If I comment now on that thread on any instance, say, on lemmy.world or on the other I just linked, does it need to first sync to beehaw before it propagates to other instances or would other instances get load my comment even while beehaw is down?
If we take beehaw being currently down as a possible explanation for not seeing any of that thread here then I suppose first the comments need to reach beehaw.
I may as well ask another question, any idea how I would find that thread easily on lemmy.world? I tried pasting the full URL in lemmy.world’s search but didn’t find it, I had to manually go into that community in lemmy.world’s instance and dig through the history to find it. In this case I assumed I would be able to find it by searching the full URL since the thread already is visible in lemmy.world, even if with no comments.
beehaw.org is back up. So lets see how long until that thread updates on this instance.
edit: Ohh… but beehaw.org is blocking lemmy.world So what would that mean for lemmy.world? Would the normal behavior be that we can see the thread’s main post but not any comment?! I thought it was the other way around though, that they don’t get any content from lemmy.world but lemmy.world can still fetch theirs.
edit: Ohh… but beehaw.org is blocking lemmy.world So what would that mean for lemmy.world? Would the normal behavior be that we can see the thread’s main post but not any comment?! I thought it was the other way around though, that they don’t get any content from lemmy.world but lemmy.world can still fetch theirs.
No, the block goes both ways. Lemmy.world cannot see anything on beehaw.org, and beehaw.org cannot see anything on lemmy.world.
Think of it in terms of one user blocking another on a regular social network.
We’re all still learning, but check your facts before posting this type of info so you don’t add to confusion about defederation.
@sss had it right. We can still see posts from beehaw, just not comments. If we comment on the posts or make our own posts, they only show up on !gaming@beehaw.org and won’t go to beehaw. And syncing seems to be about 3 hours behind there, but that could just be the general sync issues right now, unclear.
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.Here’s a similar report, this time with feedit: https://lemmy.world/post/440406
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.
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.
deleted by creator
Lemmy appears to track on the server side what posts you have read, so it can show this in the UI. That is terrible for privacy since someone bad could seize the data. If reading history is tracked at all, it should be on the client only.
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.
Next to the sorting icon at the top of a community, there is a “?” badge that looks like it is supposed to explain the sorting options. It instead navigations to a 404 page on join-lemmy.org.
This will be fixed in the next version
