/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

Why are you not seeing as many posts from Lemmy communities on Kbin? (kbin.social)

submitted 1 year ago by lixus98@kbin.social to c/kbinMeta@kbin.social

8 comments fedilink hide all child comments

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!

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

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

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

[–] LoafyLemon@kbin.social 1 points 1 year ago* (last edited 1 year ago)

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?