• Ulu-Mulu-no-die@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    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/site
    

    I have to quit the browser and wait a few minutes before I can connect again. Never happened before.

  • MrNemobody@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    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?

  • solrize@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    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.

  • solrize@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    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.

  • notatoad@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    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.

  • CH3DD4R_G0B-L1N@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    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.

  • Phil@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Just wanted to say thanks Ruud for all the work and expense. Your diligence is obvious. Thank you.

  • sss@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    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…