My wife and I picked out her ring together. She has to wear it all the time. I think she should have say in the matter. Ask your partner to help you pick one out.

Thanks so much! <3

Yeah, we also call them communities

It will work with Voyager. I also use that app and will make sure. All apps that work with Lemmy should work with Sublinks.

Lemmy.World isn’t developing it. Some of their team members are contributing but they didn’t start it. I did. I’m the admin of discuss.online

This is correct, thanks a lot!

It’s a reputable web development language and Spring Framework is very robust. I knew it would make development very quick and easy. Also, everyone learns Java just a little so I feel like it’s easy for the average person to contribute. Rust is certainly fun but Java is tried and true. The organization of the Lemmy project’s code vs Sublinks is night and day. It’s so easy to extend and grow Sublinks.

Great summary!

Easier but not what I thought was needed. We need more choice!

That’s not true, I wrote a blog post about it: https://jasongr.im/blog/why-i-started-sublinks/

I tried that the but API lacked a lot of features that they were too busy to add, like proper pagination to find the latest changes, etc. I started a project like that first called socialcare.cloud but have since shut it down in favor of Sublinks.

Java isn’t my preferred language. I did learn Rust to try to contribute but found the code base in less than ideal state and the process of contributing to risky. They don’t always accept all PRs. I also have low faith in the success of Lemmy due to it’s poor QA process and it’s major lack of features.

I believe Java is the best option for this type of application, I almost did it in PHP. My goal was to attract as many people as possible to want to contribute. It’s worked, I have a ton of people contributing in some way, Sublinks roadmap is clear and organized, and we have a super-motivated and driven team.

We won’t fail.

Yeah, that’s a good callout. Thanks, we’re working on redoing reporting and have a more traditional table/grid like layout for mulit-select.

cc: @kenvald@discuss.online

Not that I’m aware of. We will support all Lemmy apps when we launch though.

There is talk of having post types. This would allow for further fediverse integrations to function better.

To answer your questions:

1. Sublinks isn’t a copy of Lemmy. There used to be a greater focus on multiple post types, but now it’s not a main feature to work on. Sublinks is an alternative to Lemmy that adheres to the Lemmy API to capture the client base for that API. Sublinks has its API for its front-end and any apps being developed for Sublinks.

Being long-term compatible with Lemmy isn’t a priority either. We set our first milestone to be parity with the Lemmy API contracts to allow for apps to work from the start. As we grow our footprint Lemmy would have to display it the best they can. We don’t plan to add support for Sublinks into other applications.

2. Yes, we’re building our federation service to include as many services as possible.

I think there should be a separate community for it though.

I don’t have a problem with it.

What is an example of a good reason to start a new project?

That’s an over simplified version. For the record, I couldn’t downgrade without data loss.

Thanks a lot!