this post was submitted on 27 Jun 2023
28 points (96.7% liked)

Fediverse

17735 readers
35 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
[email protected]
[email protected]
28
Is lemmy.ml partially blocking /kbin instances? (lemmy.ca)
submitted 1 year ago by [email protected] to c/[email protected]
15 comments fedilink hide all child comments
 

A post on kbinMeta states that "Lemmy.ml is blocking all inbound ActivityPub requests from /kbin instances." More details here, but the theory is that -- rather than defederating -- lemmy.ml returns a 403 'access denied' message in response to any inbound requests from a user agent with "kbinBot" in the string. Upvotes, comments, and boosts don't seem to be going through. However, it appears that lemmy.ml still federates information outbound to kbin instances.

I'm wondering if anyone here knows what is going on and why it might be happening? Federation between Lemmy instances and Kbin instances seems to be a selling point for both, so I'm sure others using both services are curious as to what's going on.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] CosmicSploogeDrizzle 6 points 1 year ago* (last edited 1 year ago) (1 children)

I'm not sure if this specifically applies, but there are federation issues happening across multiple instances.

Many issues have to do with a mismatch in Lemmy BE versions. Lemmy.ml is on 0.18, others are on 0.17.4 waiting for Capcha support to come in 0.18.1. BE 0.18 replaced websockets with http, so it's a substantial update. How this works with kbin specifically I do not know, but things are in flux.

Additionally there is this issue:

https://github.com/LemmyNet/lemmy/issues/3101

Which according to the devs is related to this other issue that has been fixed and will also likely come in 0.18.1

https://github.com/LemmyNet/activitypub-federation-rust/pull/52

So, I do not believe this is international. If lemmy.ml didn't want to federate with kbin they would just defederate. With kbin being its own distinct software that is different than Lemmy, these issues are likely due to the drastic change in the last Lemmy update. Things will have to be ironed out between kbin and Lemmy