Hi! I’m trying to add a Kbin community to my account here on Lemmy, and nothing seems to work. I’ve tried pasting in the https URL and the Kbin URL, but nothing comes up in Lemmy search.
I’m sure I’m missing something simple. For reference, this is the community: @[email protected]
Thanks!
You just put in the community after the url of your instance
say in your case.
https://lemm.ee/c/[email protected]
for your example. Then just hit the subscribe in the top right.
This does not work unless someone was able to query for the community before. You’ll just get
404: couldnt_find_community. I have yet to be able to get kbin magazines to work on my instance, along with some lemmy.ml communities (about 50/50 there).I pasted the url of the kbin magazine into the search bar and waited a few seconds
This wasn’t working for me a couple days ago, but this does appear to be working now. Before I’d search and wait for over a minute and nothing, I assumed all these issues are just due to the flood of new users/instances. Good to know it works now. We’ll see if the subscription goes through and content shows up though, that’s the issue I have with lemmy.ml at the moment.
You have to search for [email protected]
I haven’t successfully federated with kbin yet which is a shame.>
Yeah I can’t get it to pull in my instance either. I think it may be their cloudflare config.
I’m not sure. Would love to add kbin instances.
I take that back. I searched the actual url and it worked. You also have to leave the filter set to all
https://kbin.social/m/tech
Another post here suggested searching the URL. This worked correctly. Yay!
This is what I’m experiencing too. Spent the better part of yesterday (unsuccessfully) trying to figure out why it doesn’t work - or only works sporadically for .ml like you found.
Couldn’t find anything in the logs other than the fact that kbin&.ml manage to send a web request to my instance under the ^/.well_known subdir. After that…nothing - communities on my instance don’t show up on those sites after they sent the req. It’s like the communication is dying somewhere in the middle.
This worked for me! Thanks. Based on the other comments, I guess someone had searched for that before.
Looking forward to an easier method, but this is fine for now.