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
jgrim
joined 2 years ago
MODERATOR OF
- 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.
- 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.
- 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.
Exactly, we already had 13 contributors working on it before it was announced.
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.
I only put it on when she goes into hibernation, so I take it off once a year. It's not a daily thing. Thanks for the tip!
You could always repaint it. It’ll last a lifetime or two. I have a 2020. They stopped the V8s by then :(
Basically, it's a replacement for Lemmy. Ground-up rewrite of the source using a language with a much larger community.