/kbin meta

16 readers

2 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago

What's up with "The magazine from the federated server may be incomplete. Browse more on the original instance."? Is this working as intended or is it a bug? (kbin.social)

submitted 1 year ago* (last edited 1 year ago) by Treedrake@kbin.social to c/kbinMeta@kbin.social

26 comments fedilink hide all child comments

I've been seeing this for quite a bit, and thought it'd resolve itself once CloudFlare was taken off, but I'm still seeing it on many external communities from e.g. Lemmy. Not all posts or comments are visible from Kbin. Any idea on what's going on?

Edit, clarification: when I visit e.g., https://kbin.social/m/technology@beehaw.org the above mentioned sentence shows up, and I'm not able to see threads created even 13 hrs ago, like this one on the original instance https://beehaw.org/post/927935?scrollToComments=true. New content doesn't seem to be pushed to this instance at kbin.social. This is the issue I'm referring to.

Edit 2: This is probably the answer: https://kbin.social/m/kbinMeta/t/131241/What-s-up-with-The-magazine-from-the-federated-server-may#entry-comment-517045

you are viewing a single comment's thread
view the rest of the comments

[–] Treedrake@kbin.social 7 points 1 year ago (1 children)

So it's basically working as intended? It does feel like an annoying "issue" though. Thanks for explaining anyhow!

[–] dannekrose@kilioa.org 6 points 1 year ago (1 children)

@Treedrake

You're welcome!

Yes, it is working as intended. The idea is that each instance is responsible for pushing content once, then it's the responsibility of the receiving instance to process and display the content to the relevant users/accounts.

As a side note, if everything was "re-pushed" out, the load becomes even more on the "source of truth" for larger communities with wide federation and a lot of new content generated locally and remotely. I could see this being leveraged to take down servers by simply spamming really large communities (with large federation) with small content forcing the "source of truth" to now "re-push" the content to every server that is knows about for every single new comment, or reply, or post.

[–] Treedrake@kbin.social 1 points 1 year ago (1 children)

Fair enough! I guess it's a downside that comes with the federation.

[–] Kichae@kbin.social 3 points 1 year ago

Eh, it's not much of a downside in an active community. The model is push once at time of publication, there are other systems in place that republish content and help it propagate through the network.

On kbin, there's a "boost"... well, it's not really stylized as a button, but there's a "boost" feature, which acts to republish posts or comments and allows them to reach newer subscribers. I'm not sure how it works on Lemmy, as there's no explicit boost, but there are mechanisms there to renew active back content.

It all just means we, as users and members of communities, need to take on a little bit of responsibility for ensuring that interesting or valuable content propagates.