Title. I’m wondering what’s everyone’s take on this. On the one hand it’d mean seeing multiples of one post if you’re subscribed to equivalent communities between communities. On the other hand, right now I think a big worry is this momentum we have dying out due to lack of content.

We can’t possibly predict which community will be the “big” community across the Fediverse, so maybe cross-posts are the way to go until things grow big enough.

Thoughts?

  • 𝕊𝕚𝕤𝕪𝕡𝕙𝕖𝕒𝕟@programming.dev
    3·
    1 year ago

    Well, there’s this place:

    My new community got quite a few subscribers from there. Just make sure to post relative links using both the Lemmy and kbin routes (/c/ and /m/).

    EDIT: oh, I almost forgot, there actually is a site for community discovery: Lemmy Browser. I don’t think it currently lists kbin communities but we could ask them to (or if it’s open source, someone could implement it).

    • Otome-chan@kbin.social
      3·
      1 year ago

      I’ll definitely post some communities there :) I think it’s easy enough to discover lemmy communities, I just feel that kbin magazines ain’t getting as much love haha.

    • tal@kbin.social
      3·
      1 year ago

      Realistically, I feel like having a common link syntax must either exist – I haven’t really familiarized myself with the syntax yet – or is gonna get sorted out soon.

      • 𝕊𝕚𝕤𝕪𝕡𝕙𝕖𝕒𝕟@programming.dev
        1·
        1 year ago

        It already exists but Lemmy converts it into a regular link (I don’t know what kbin does):

        Syntax: !community@instance.tld

What Lemmy does: [Community](https://instance.tld/c/community)

Correct Lemmy link: [Community](/c/community@instance.tld)

Correct kbin link: [Community](/m/community@instance.tld)

        The first problem is that it should be a relative URL so visitors from any instance are sent to the community on their own instance.

        The second one is that the conversion should be done at rendering time instead of in the editor, so the client (Lemmy or kbin) can format the link according to its own route pattern.