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.

  • chiisana@lemmy.chiisana.net
    1·
    11 months ago

    This is great, glad to see new project growing with community support.

    I’m curious as to if/how you plan to manage divergences from the current Lemmy features? Take for example the push notification issue mentioned in another reply (I can see it on your instance but because I wasn’t subscribed to the community before they were posted, it is not federated to my instance) for example. If you were to add that feature while adopting web standards, and Lemmy devs continue to stubbornly move forward with janky third party app solution, how would/could the divergence be managed? I don’t mean it in a negative way, just curious of the plans around things like this, as I have high hopes for this project to excel and end up better than the core Lemmy.

    • jgrim@discuss.onlineOPM
      61·
      11 months ago

      We’ll just become our own applications at some point. The reason I’m supporting the Lemmy API from the start is to allow users to have apps from the start. At some point there will be Sublinks phone apps and the need to support the Lemmy API will go away. Similar to how you can use a Mastodon App to interact with Pixelfed.

      Our plan is to implement everything right from the start. We have 4 core developers and 13 contributors helping at different capacities. Everyone is experienced and driven to do our best and make the fediverse more open to everyone.

      The reason Sublinks can replace Lemmy is that we’re building a migration to do so. It won’t be drop-in because we are building a whole new optimized database schema. We’re also keeping some of the same settings and capabilities for as long as we support their API. At some point the things we don’t like will go away and the things that are liked will stay.

      I run discuss.online and I wanted to contribute to Lemmy to improve moderation; however, I found it difficult to contribute in any meaningful way for a multitude of reasons. I created a service called socialcare.cloud to help with moderation but the Lemmy API is so limited I couldn’t fully do everything that needed to be done without copying the entire database from the instances it serviced.

      Mastodon seems so polished and easy to use. It’s getting wide adoption. I want to create that experience for link aggregation social networks too.