/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

105

/kbin is feeling great right now (kbin.social)

submitted 8 months ago by [email protected] to c/[email protected]

26 comments fedilink hide all child comments

Thanks for putting in something awesome, @ernest! Not sure if you want feedback, but functionality is as full as I know it to be. Maybe better. It is really fast right now! Hope you are on the mend.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 9 points 8 months ago (7 children)

Hi @piotrsikora. Great to see that kbin is responsive again and returning to usability. If possible, could you please give an update on what is going on currently with federation? It looks like some things are getting through (e.g. I can see this thread on reddthat) but threads from most lemmy instances are not showing up in a timely way in /newest still and at a quick glance it looks like communities in my collections are maybe a half day behind -- with many threads from the past week or more missing entirely.

I'm assuming some of that may be on the lemmy side -- 0.19 has a major issue with sequential message distribution as seen with lemmy.world <-> reddthat.com federation (see this bug report and this comment if you're unfamiliar) -- but it'd be best to hear from someone who has access to the infrastructure about what's going on rather than guessing.

In particular, it'd be helpful to know:

What kind of delay should we expect for threads and comments we create here to show up on Lemmy communities?
What kind of delay should we expect for threads and comments other people create on Lemmy/mbin/etc. instances to show up here? (Obviously this may vary from instance to instance, but in general are things cleared up now on the kbin side for receiving new threads quickly?)
Are comment notifications still delayed from local kbin replies -- or has that been fixed with the infrastructure changes?
Are federated upvotes propagating quickly? (It is very discouraging if you post something and it gets no interaction at all -- knowing if there's federation delay in upvotes would help with distinguishing between "no one saw this", "no one liked this", and "people probably saw it and maybe liked it but the response hasn't made it to kbin yet")
Is federation still playing catch up and old missing threads/comments will be backfilled eventually, or have they been dropped to get things back in working order?
Have any major instances defederated with kbin.social during the recent problems?

Also, should we @ you in addition to @ernest if we encounter problems on kbin.social?

Thank you!

[–] [email protected] 6 points 8 months ago (6 children)

@e0qdk
I can only check federation with our mastodon server (pol.social), and now is very quickly (about seconds).
Queue on kbin.social is empty, so everything should work instant. Maybe lemmy.world add some limitation due to problem with kbin.social.

Feel free to add if you encounter some problems with infrastructure ;)

@ernest @rhythmisaprancer

[–] [email protected] 0 points 8 months ago (1 children)

There was a bug with KBin some days ago where it would send huge amounts of federation activities to Lemmy instances which would overload them. To mitigate this, lemmy.world and some other instances had to block kbin.social. I believe the .world admins tried to get in contact with @[email protected]. You can read some more details here.

I would also suggest that you and Ernest join the Lemmy Admin chat on Matrix where this problem was found and discussed.

[–] [email protected] 1 points 8 months ago

lemmy.world block federation for about 1 day.
now should works everything.

load more comments (4 replies)