@1Fuji2Taka3Nasubi Hey, during the server migration, I had to unload the queue (the previous week). I added several addresses to the blocked instances that were either unresponsive or generating errors at that time. Lemmy.zip ended up on that list - probably by mistake. My bad. Now, after the initial verification, most of those instances are still dead, but I will verify it more thoroughly today. Now that I have sorted out the infrastructure issue, a series of federation fixes will follow - perhaps even this week.
this post was submitted on 10 Jul 2023
4 points (100.0% liked)
/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
Thank you for looking into it. I tried subscribing again and it went through, and several threads just got through to kbinMeta over there, so I'll cautiously say it seems to be fixed now.
Glad to hear federation is being worked on, it does feel it needs to be more robust to live up to the promise that one gets the same experience no matter which instance (local or remote) one view a magazine from. (I'm not being critical, interoperability is always a hard problem no matter which stage of development it is)
Again, thanks for the good work and for bringing kbin to us!
Actually, I have a plan to improve the federation, but at this scale, I need to be super cautious. Just one mistake is enough to harm other instances. That's why I want to prioritize setting up robust testing environments first, so that the every changes in this regard are thoroughly checked and validated.
Is the list of blocked instances available to view somewhere? It'd be nice to know which instances are currently blocked on Kbin.social
@ernest Is there just a constant cache of posts to be received that have to process before updating in a magazine here? I'm confused on why some magazines are only behind on syncing with lemmy communities by a few hours, but some are weeks behind on the same instance.
The latest Lemmy updates seem to have a lot of issues, including communication with non Lemmy instances.
That doesn't explain the difference in behavior between talking to fedia.io and kbin.social though.
I'm not sure but it feels like I see a lot more content from a larger number of communities when I browse from my Lenny.world account. When I browse from a kbin.social account I don't think I see as many different posts from different instances or communities.
I have a similar experience, this and the wefwef app have made me to primarily browse from lemmy.world for the past couple days
Yes I did that to try out the apps too. wefwef/Voyager is very nice and is being updated frequently and getting new features. Memmy is pretty good too. Lemmy.world was a bit sluggish before they fixed it that’s why I was trying out a less busy instance.
When Artemis for kbin comes out I’d like to check it out too.
That’s my impression as well.
The admins probably has a lot on their hands but I hope they get around to fixing federation.
Yes it does. My KBin node is not federating with KBin.social or only works intermittently.
Thanks for the verification. Is your node working well federating with Lemmy/kbin instances other than kbin.social?
Posting in here since my issue is related and I'm wondering if anyone can lend any insight.
Does anyone know why federated microblogs wouldn't show up in a given magazine? I've added tags for a magazine I moderate, but posts don't show up with any regularity. However, upon clicking the tag in the magazine description, all sorts of posts with the tag show up.
I haven’t looked at microblogs much, perhaps someone else can give you an answer here.
Isn't that how it is supposed to work? Microblogs shouldn't get mixed in with Threads right?
I'm not asking about threads, I'm asking about why the microblogs section of a magazine isn't being populated.
view more: next ›