this post was submitted on 16 Jul 2023
22 points (100.0% liked)
/kbin meta
5 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There were talks of lemmy.ml limiting kbin but I don't know if that was ever verified. There are other kbin instances you could try and see.
I use apps so lemmy experience is ahaping up to be pretty good for me.
It was verified and fixed, so users on kbin. social should at least be able to see their posts now https://kbin.social/m/kbinMeta/t/173366/lemmy-ml-is-no-longer-shadowbanning-kbin
We on kbin could always see lemmy.ml, it was their server which was accidentally misconfigured to reject information originating from kbin. As you say it has now been resolved.
.ml unblocked the kbinBot UA a couple days ago so as new posts and comments are made it should be syncing up. there are still a few instances out there that seem to not federate as well (in particular beehaw doesn't seem to be federating beyond community discovery) but i believe that's just some reverse proxy misconfiguration (the lemmy-ansible nginx config had some federation related fixes with the release of 0.18.1 they may not have applied) rather than anything intentional