It seems that any Lemmy.world and Lemmy.ml hosted communities aren't any longer federating properly via kbin as I started getting 404 errors on all of them. Examples:
https://lemmy.world/c/personalfinance: ok
https://kbin.social/m/personalfinance@lemmy.world: 404
https://lemmy.ml/c/fire: ok
https://kbin.social/m/finance@lemmy.ml: 404
https://beehaw.org/c/finance: ok
https://kbin.social/m/finance@beehaw.org: ok
16 Comments
Alexmitter@kbin.social · 6 pts · 3y
Yea they are all on 0.18 which breaks federation with kbin. https://github.com/LemmyNet/lemmy/issues/3354
frasassi@kbin.social · 3 pts · 3y
@Alexmitter Thanks for linking the relevant repo issue, that explains it.
Mystify0771@kbin.social · 1 pts · 3y
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
Mr_Figtree@kbin.social · 0 pts · 3y
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 (personalfinance@lemmy.world), 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.
frasassi@kbin.social · 1 pts · 3y
@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/community@instance.tld. So https://lemmy.world/c/bogleheads should work via https://kbin.social/m/bogleheads@lemmy.world 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?
Mr_Figtree@kbin.social · 1 pts · 3y
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/personalfinance@lemmy.world .
frasassi@kbin.social · 1 pts · 3y
@Mr_Figtree It's broken because of the 0.18 update as linked by Alexmitter above...
Mr_Figtree@kbin.social · 1 pts · 3y
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.
Alexmitter@kbin.social · 1 pts · 3y
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.
Mr_Figtree@kbin.social · 1 pts · 3y
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).
frasassi@kbin.social · 1 pts · 3y
@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/personalfinance@lemmy.world 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.