this post was submitted on 08 Jul 2023
8 points (90.0% liked)
/kbin meta
639 readers
1 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
@blazera lemmy.ml is blocking incoming traffic from the kbin.social server.
https://kbin.social/m/kbinMeta/t/145248/Is-Kbin-defederated-from-Lemmy-ml#entry-comment-568968
@rodhlann
As far as I know, lemmy.ml itself is not blocking kbin requests, at least not on purpose.
But I will try to get some official information from one of the lemmy.ml admins.
There were some issues with the federation of non-Lemmy instances in general.
Multiple issues caused these and affected incoming and outgoing communication.
https://github.com/LemmyNet/lemmy-ansible/issues/106
https://github.com/LemmyNet/lemmy/issues/3354
The latest Lemmy version 0.18.1, which was released yesterday should fix most of the issues, but some instances still need some fixing on the nginx side.
@stanford @ernest > As far as I know, lemmy.ml itself is not blocking kbin requests...
lemmy.ml is returning 403 forbidden responses at any of it's endpoints when the useragent string contains "kbinbot". We know this because we've tried all variations. Brave kbin instance admins willing to change their useragents are able to federate just fine with lemmy.ml.
This is not a Lemmy thing, its implemented at the server or firewall level. Lemmy.ml admins have not responded at all.
@stanford @ernest Annoyingly, they have not fully defederated. Due to the nature of ActivityPub lemmy.ml users can view and interact with kbin instance magazines and content just fine.