this post was submitted on 10 Jul 2023
29 points (100.0% liked)
Moving to: m/AskMbin!
235 readers
6 users here now
### We are moving! **Join us in our new journey as we take a new direction towards the future for this community at mbin, find our new community here and read this post to know more about why we are moving. Thank you and we hope to see you there!**
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Lemmy can see kbin magazines. I'm on a lemmy instance right now.
kbin.social itself has had some federation issues in the past month, but I think that's more growing pains of a new platform than anything inherent in the system itself.
Oh, maybe that's where I got the idea that Lemmy couldn't see them, I've only been on the fediverse for a couple weeks. People were saying Lemmy couldn't see kbin, but I didn't realize that was temporary.
There's some suspicion that the specific instance lemmy.ml is rejecting incoming requests from kbin via a configuration, but lemmy.world, lemmy.ca, beehaw, etc. seem to be federating well enough.
Not really suspicion at this point. They are proveably 403 rejecting requests from the KBin useragent. You have the letters "kbinbot" anywhere in your useragent (case insensitive) you ain't getting content.
As a bonus they're still sending out stuff to instances though. But since KBin can't then resolve it it amounts to a DoS attack as the messages just build up in KBin retry queues.
At what point do the other instances consider this federation in bad faith and defederate from .ml?
A number of kbin instances already have. But not .social - which is obviously the largest instance.
Aggravatingly .ml users can browse and interact with kbin magazines just fine as we let them in. It's very much a bad faith thing at this point.
G'day from a Kbinaut :)
Yeah this seems to be a temporary thing. I've been following the federation issues we've been having on kbin and I'm hoping they can resolved as everything stabilizes.
I'm unsure if the ingest from kbin > Lemmy was working because last I checked they were returning error responses on requests that had "kbinbot" in the name.
It's only lemmy.ml, not all of lemmy, that's returning a forbidden response on requests from kbin.
There definitely seems to be something going on but I haven't found solid problem replication steps.
For example it may be because the instance the thread was posted on is lemmy.ml but I expected the thread here: https://kbin.social/m/[email protected]/t/163712/former-current-Twitter-users-what-do-you-do-on-there would still sync up with where the version of the thread where the OP is located https://lemmy.nz/post/314511 even if it the instance where the thread was posted (maybe?) doesn't federate with kbin.social: https://lemmy.ml/post/1868037
It's possible my mental model of fediverse working is just still very basic and thread instance is the ultimate arbiter?
Yeah that doesn't look like it's federation correctly. I'll raise it again with some of the other devs, maybe one of them will know. Pretty annoying ;(
I hope kbin gets federated by lemmy.ml it seems they have been rather trigger happy with blocking. It seems we will have to wait and see which instance is the most free.
A lot of the original Lemmy instances are quite trigger happy. It's one really nice thing about the new instances with new admins who block but still prefer not to unless it's really necessary.
i kind of knew what i was signing up for with this lemmy ecosystem, so at worst people will just switch instances and the most free gain the most leverage, it beats this hopping from one centralized service to another by far.
I've been all-in on the fediverse since early 2021, including the threadiverse. It may not be the future for the masses, but I think it might be the future for people who value freedom and autonomy.
there are like 10 times or 20 times more users online than back when reddit even started, i think we will be fine even if it wont be for "the masses". I respect that you got in early, a true pioneer.