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.
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.
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:
This is normal, because normally only stuff gets synced over:
When you search for that explicit post/comment, etc.
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.
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)
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
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.
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
/inboxand status of 200 that looks like this: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.
This is normal, because normally only stuff gets synced over:
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.
Wait, this means All is based on the instance users subscriptions? Or I am misunderstanding?
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)
Asking the real questions.
To “fix” all, you can run a bot. Check !lsbsupport@lemmy.world
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.