Hi, so I launched my very own instance. I’m posting from here, and hopefully this post makes it there. I subscribed to a few coms, but I’m getting outdated posts and the votes don’t line up, also the comments do not all load. So I’m able to federate, but for some reason only some of the data is coming over to my server… Has anyone here been experiencing the same thing?

UI is 0.18.2 and BE is 0.18.1

I just wanna be able to browse other coms without having to constantly switch domain names and log in with another account just to participate.

edit: Here’s pics for comparison for a post on selfhosted.

my instance [22 replies, 28/3 votes]

lemmy.world instance [20 replies, 61/3 votes]

  • MajinBlayze@lemmy.world
    1·
    1 year ago

    ActivityPub appears to be very “eventually consistent” by design. There’s no guarantee that any given post or comment gets federated to you within a particular period of time.

  • Max-P@lemmy.max-p.me
    3·
    1 year ago

    Regarding your edit, I see a pattern here: you’re only seeing content from lemmy.ml and lemmy.world. Checking your instance’s federation list, you’re using the allowlist of only those and kbin.social. That means your instance is likely to be dropping anything from other instances, and everyone in this thread is from other instances.

  • manitcor@lemmy.intai.techEnglish
    2·
    1 year ago

    first day my instance was all over the map syncing, there are a few general mismatch bugs, a couple are caching. The big one is posts on one instance not propagating to all other instances, in particularly the home instance where the thread started.

  • Max-P@lemmy.max-p.me
    41·
    1 year ago

    How long has it been? If you just spun it up, what you’ve seen is just the initial pull of the content. As you subscribe, all new content will get pushed to you, but the old content never backfills.

    Check your NGINX logs, you should see a bunch of POST requests to /inbox and status of 200 that looks like this:

    54.36.178.108 - - [13/Jul/2023:01:10:16 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:16 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:17 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:17 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:18 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:19 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:19 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"

    Included a bunch, as you can see they should be coming in quite frequently, basically everytime someone does something on the remote instance.

    Make sure you’re subscribed to the community as well

    Basic curl testing seems to rule out common routing problems, so check the lemmy logs as well just in case.

  • Jeena@jemmy.jeena.net
    5·
    1 year ago

    This is normal, because normally only stuff gets synced over:

    1. When you search for that explicit post/comment, etc.
    2. When you start subscribing everything after gets synchronized

    Anyway, like others said, most of this weirdness fixes itself after a bit of time, the next day you should be having a fairly normal experience with the exception of the “All” because if you’re the only one on the server your Subscribed and All are exactly the same.

    • XTornado@lemmy.ml
      7·
      1 year ago

      Wait, this means All is based on the instance users subscriptions? Or I am misunderstanding?

      • tal@kbin.social
        1·
        1 year ago

        I suspect that it works like the leafnode Usenet server did.

        A full Usenet feed is a lot of traffic.

        Leafnode would only download or update a newsgroup’s contents when first requested by a client. But once it did so, it would store that data and make it available to other clients. It kept bandwidth requirements reasonable for Usenet servers with a small number of users.

        The idea here is presumably aimed at scaling – to basically try to only download what your users want, but once it comes down for one, to let all the others use it. Optimizes for your instance’s bandwidth.

      • das@lemellem.dasonic.xyz
        3·
        1 year ago

        Yes, “All” shows all the communities users are subscribed to on your instance (since communities don’t federated with an instance until someone on that instance subscribes to it)