Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !newcommunities@lemmy.world

It’s available for me on kbin.social as of this writing, and I subscribed.

As far as I can tell, what one needs to do on kbin is search for communityname@instance. I don’t think that “!” goes in the search string.

But that’s already run by now.

For people on kbin.social, you should be able to see it at:

https://kbin.social/m/battlestations@lemmy.world

If you’re on another kbin instance, do the above search. I’m still a little fuzzy about the right syntax in a comment to produce a link to perform such an initial search in a cross-lemmy/kbin, cross-instance fashion. I think that it should be:

!@battlestations@lemmy.world

Giving the following:

That generated link does work for me on kbin.social, but I could be wrong about it working elsewhere.

I really wish that this particular issue would be made clear, as it’s important for community discoverability.

EDIT: Nope, generated link does not work on lemmy.world, so doesn’t work on lemmy, at least.

EDIT2: On fedia.io, another kbin instance, the link also doesn’t work, so someone on the instance may need to have already subscribed for the link to be auto-generated. The ability to have a link format that directs to one’s local instance in a way that works on all lemmy and kbin instances, regardless of whether anyone has subscribed, would be really nice.

EDIT3: Trying:

[battlestations@lemmy.world](/search?q=battlestations%40lemmy.world)

Yields

battlestations@lemmy.world

Which works to generate a search on kbin.social.

It also appears to work on fedia.io, so this is probably the right way to do a link, at least for kbin users.

EDIT4: It also appears to work for lemmy instances! This should probably be the new syntax used on newcommunities@lemmy.world to link to a community!

Not sure. I know that federation is still a bit iffy, generally. newcommunities@lemmy.world was erroring out for me for a long time from kbin.social, I just happened to check today when I saw something hit my feed.

Edit: I know on kbin, there’s a search function that might get you there, if it’s an issue with the links I’ve included here? Something like that on your platform, maybe?

If you could edit in an instance-agnostic link (!communityname@host-instance.com) for example: !newcommunities@lemmy.world would be this one.

Makes finding your community on other instances easier (and is technically required for our formatting rules)

That may be a good idea. The 3 communities I found relevant to crosspost this are:

• !fediverse@lemmy.world
• !fediverse@kbin.social: only 2 votes, no comments.
• !newcommunities@lemmy.world: this one

Curious if anyone else here is on kbin having issues accessing this. I tried altering the URL a few ways, can’t seem to get to it on kbin. And yet, I am on /m/newcommunities@lemmy.world just fine.

Lemmy community for kbin: /search?q=newcommunities@lemmy.world

Technically the actual link is /m/newcommunities@lemmy.world, but if your kbin instance has no subscribers to that community yet, you have to first find it with the first link and subscribe to it, otherwise you get a 404.

At least on kglitch.social, using !newcommunities@lemmy.world seems to work like a combination of both: Searching for it when kglitch.social doesn’t know about it yet, going to /m/community if kglitch.social does know about it.