Hello! You may have noticed that the majority of posts and threads in your feed on Kbin are from within the platform itself. This is because the admin has activated Cloudflare DDoS protection which basically slows down requests to kbin, to prevent the website from experiencing downtime or becoming slow to respond.
Before implementing this measure, Kbin would often show 500 errors and be sluggish in its performance.
The admin (ernest), has been working on finding solutions.
So hopefully, everything should go back to how it was before, and you will see a lot more posts from the communities you have subscribed to with a bunch of comments from other places.
In my opinion, this also created an interesting situation where you can really see how active kbin is even when the discovery of posts from outside the platform is not functioning as intended.
Rest assured, this is only temporary, and in the meantime, take the opportunity to create and grow communities from within kbin itself!
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.”
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.
Hey, kbin is in Lemmy feeds again!
We recently refederated, we got a server update!
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?
