cross-posted from: https://discuss.online/post/4522403

We are thrilled to announce the upcoming release of Sublinks, a groundbreaking Link Aggregation Social Network, joining the Fediverse. This innovative platform is designed to revolutionize how we share and discover online. Our dedicated team of volunteer contributors has worked tirelessly, utilizing technologies like Java, Go, TypeScript, and HTML to bring this vision to life. Sublinks promises a user-friendly interface and robust features that cater to diverse online communities. Stay tuned for our launch date, and get ready to experience a new era of social link sharing!

Sublinks will have a fully compatible API with Lemmy so all current Lemmy apps will also work with Sublinks. In fact, discuss.online will switch to Sublinks to fully replace Lemmy once we reach our Parity Milestone.

For more information, visit GitHub - Sublinks and sublinks.org.

Stay tuned for more regular updates as we progress.

  • @[email protected]
    link
    fedilink
    English
    3910 months ago

    Please give me one example of how sublinks is better than lemmy currently for use.

    (I don’t understand why new software instead of improving lemmy.)

    • @[email protected]
      link
      fedilink
      English
      2910 months ago

      It’s always good to have alternatives. Healthy competition can make them grow better too.

          • @[email protected]
            link
            fedilink
            English
            010 months ago

            you are aware that what you linked is up to mastodon to implement? nothing to do with Lemmy.

            • @[email protected]
              link
              fedilink
              English
              1010 months ago

              Not really, Kbin (which also similar to core function as Lemmy) has better interoperability with Mastodon.

              Nutomic, Lemmy dev, reject that idea. Quoted from himself: “Like you said, Kbin already supports this. No need to reimplement it in Lemmy, definitely wouldnt be worth all the effort.”

            • @[email protected]
              link
              fedilink
              English
              310 months ago

              Which comment in the issue thread leads you to believe that?

              The developer’s closing comment is that it wouldn’t be worth it to implement that feature in Lemmy.

    • @[email protected]
      link
      fedilink
      English
      1810 months ago

      Java, Go, TypeScript, and HTML

      Different technologies. Rust is a more niche language, which is sometimes used to explain why there aren’t that many contributors to Lemmy

        • @[email protected]
          link
          fedilink
          English
          2610 months ago

          There is probably no reason now, but hopefully in the near future Sublinks will reach feature parity with Lemmy, and could even surpass it. Technological stack can have a huge impact on the development speed of a project.

          In other words, let’s wait and see

          • @[email protected]
            link
            fedilink
            English
            1310 months ago

            Thank you. That was very clear. I look forward to seeing the results of the developments.

      • jgrim of Sublinks
        link
        fedilink
        English
        1110 months ago

        Exactly, we already had 13 contributors working on it before it was announced.

      • @Molecular0079
        link
        English
        110 months ago

        Rust may be niche now, although it’s current momentum is huge, especially in the FOSS space.

      • @[email protected]
        link
        fedilink
        English
        -810 months ago

        That’s like saying “Watch my new TV show, it’s better than the other shows because our scripts are printed on an Epson printer!”

        • @replicat
          link
          English
          16
          edit-2
          10 months ago

          Not really because these are open source projects. The one that is easier to develop for will likely get more features which leads to more users.

          That being said, Java was a questionable choice IMO.

          • @[email protected]
            link
            fedilink
            English
            110 months ago

            The one that is easier to develop for will likely get more features which leads to more users.

            Not necessarily. It might get more developers at first when people think it’s going to be the Next Big Thing ™, but if nobody uses it, the devs might not feel their effort is worth it and might move on.

            Why wouldn’t people use it, despite it having “more features”? Because social media is mostly driven by network effects. People go where other people go. All the people there create content which gives people a reason to go there. In the distant past, Facebook only grew because it was so easy to move from MySpace. And, it was easy to move from Friendster to MySpace, and so-on back to the origins of social media. Since then, the walls of the walled gardens have become much higher. Every social media company actively makes it difficult to move to other platforms because they want to keep any users they have. You might hate Facebook, but you like Aunt Jane, and she’s only on Facebook, so you stay on Facebook.

    • db0
      link
      fedilink
      English
      1410 months ago

      Sometimes improving an existing software is not always possible. One example is when the lead devs do not accept the proposed features. Another scenario is when a dev team is too onerous to work with. I am not involved in this project so I do not know the background here myself so I can only make a few educated guesses.