17
Help! Instance syncronizing in a very weird way
(818.gallery)
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]
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?
To “fix” all, you can run a bot. Check !lsbsupport@lemmy.world
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.
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.