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.

Yes, almost all team members are contributing code, designs, feature requests, etc. I called out @Rooki@lemmy.world specifically because he's been a major contributor. One of the admins is actively recruiting people to help contribute to Sublinks, this is how we got so much support so quickly. It's a very close collaboration. I owe a lot of thanks to the Lemmy.World team.

A new front-end is coming too. We need a new front-end to support all the new features we’re adding.

Yes, there is going to be a tool that exports from Lemmy via a direct database connection and adds to Sublinks via the API. Sublinks is heavily event driven by design. We'll want some events to trigger during import.

It's basically a fork of Lemmy. But rather than forking, we're rewriting the entire tech stack to something easier to support and enhance. You can see the full roadmap here: https://github.com/orgs/sublinks/projects/1

1. I referenced the Rust code to determine what was sent and received. We're implementing better code logic; we're not just copying their API. We want to be compatible to attract users and support all the hard work used to create Lemmy phone apps.
2. Java is for the core Sublinks API/core. Golang is being used for the federation service that operates independently. Once it's done, it will be platform agnostic if someone else wants to use the federation service for their fediverse project. They communicate through a message bus.
3. Yes, we plan to do the new API correctly. We will support Lemmy's API for as long as it is relevant, primarily for mobile apps.

Multiple domains aren't possible yet, but that doesn't mean we cannot add it later.

I'm unhappy with the Lemmy roadmap, development speed, and quality. I wanted to contribute but found it difficult to. I did the next best thing and created a somewhat drop-in replacement with a much larger community of developers who are willing to support it.

You can see the complete Sublinks roadmap here: https://github.com/orgs/sublinks/projects/1. The first release of parity (v0.10) will use the existing Lemmy front-end. All releases after that will no longer support the Lemmy UI because that's when the enhanced features start to roll in. We don't want to support or fork the current Lemmy UI.

That’s the goal, yes.

The LW admins have helped contribute to Sublinks. They've given me full support and access to all resources to help grow it. They've been extremely helpful.

We are creating a Sublinks specific API that is much more optimized than the Lemmy one. Our front-end will be using that. Also, we'll have tons more features that the Lemmy core doesn't support.

The front-end is coming later. It’s fully compatible with Lemmy’s API so the demo site currently uses the Lemmy front-end.

Thanks a lot! There are currently 13 contributors; it's coming together very quickly. I'm super excited.

The front-end is coming later. It's fully compatible with Lemmy's API so the demo site currently uses the Lemmy front-end.