Yea they are all on 0.18 which breaks federation with kbin. https://github.com/LemmyNet/lemmy/issues/3354
this post was submitted on 02 Jul 2023
3 points (100.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
Not sure if it's the same issue, I can see new posts from lemmy but not all the comments get synced. For example I can see all the comments for the post but most of replies to those comments are missing. Also, comments made on kbin are not visible on lemmy
Were these communities federating before, or is this the first time you've tried them? I got a 404 on the first one, searched for the qualified name ([email protected]), now I'm not getting a 404 anymore. Instances don't learn about communities on other instances by themselves, you need to search for them and interact with those communities for your instance to start pulling in content.
@Mr_Figtree I am not 100% sure what you mean by "you need to search for them and interact with those communities for your instance to start pulling in content". The URL syntax for federated communities outside of kbin is fixed to https://kbin.social/m/[email protected]. So https://lemmy.world/c/bogleheads should work via https://kbin.social/m/[email protected] when federating properly. However it isn't even coming up in search at the moment: https://kbin.social/magazines?q=bogleheads
Perhaps something to do with the very recent lemmy.world update to 0.18.1-rc?
Oops, didn't mean to delete my comment. You get a 404 for communities that no one on your instance has interacted with yet. After you search for them using the general search (not the magazine search), e.g. https://kbin.social/search?q=personalfinance%40lemmy.world , they show up on your instance, e.g. https://kbin.social/m/[email protected] .
@Mr_Figtree It's broken because of the 0.18 update as linked by Alexmitter above...
Yeah, that is a separate issue that I don't think is affecting lemmy.world right now because I am seeing content from there show up on the front page.
@Mr_Figtree I'm pretty sure this is the issue as lemmy.world just updated to 0.18. They are being "re-linked" to kbin as we speak, https://kbin.social/m/[email protected] just popped up and timestamped as created 52 minutes ago. Perhaps something with caching? No idea, it goes beyond my area of knowledge but definitely something broke just a few hrs ago.
You still see content, just not any new content from that instance from the moment it updated to 0.18, except content made by users who are on other instances that not yet have updated.
I'm browsing /newest and seeing posts from lemmy.world. The time that OP says the magazine was created on this instance matches when I did my search. I really don't think the 0.18 thing is what OP is running into (lemmy.world is running 0.18.1-rc.7).
view more: next ›