Thank you for mentioning this. Is this also the reason for the following message when subscribing to instances on other servers?
”The magazine from the federated server may be incomplete. Browse more on the original instance.”
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
Thank you for mentioning this. Is this also the reason for the following message when subscribing to instances on other servers?
”The magazine from the federated server may be incomplete. Browse more on the original instance.”
Would it be possible to have other kbin/Lemmy instances circumvent the cloudflare protection while still having it active for users? Like, maybe whitelisting the IPs of other instances? It should not be that much work since those IPs should be static, but completely losing federation everytime DDos protection is fired up seems bad
Yes it can be disabled for specific requests, referrers, or IPs, but there might be a better idea to differentiate, and hail instances. Maybe via a super cookie?
Hey, kbin is in Lemmy feeds again!
We recently refederated, we got a server update!
I just came over here and totally new to this. The transition is a bit confusing for me.. Can someone help explain why when I click on a community I subscribed to here that is on Lemmy it says:
The magazine from the federated server may be incomplete. Browse more on the original instance.
Is this normal behavior for things that aren't on kbin social?
Yes, it is normal. Basically, when you search for a community on Kbin for the first time (a community that was recently created, that no one else has searched for), it gets "saved" on kbin.
However, it won't show you any posts that were made before kbin discovered that community. It will only display posts from that moment and onwards.
The message is telling you that the community may not have all the previous posts, and if you want to see them, you need to visit the community's specific page or instance.