this post was submitted on 29 May 2024
19 points (95.2% liked)
Sublinks
266 readers
1 users here now
Donations
About
Sublinks, crafted using Java Spring Boot, stands as a state-of-the-art link aggregation and microblogging platform, reminiscent yet advanced compared to Lemmy & Kbin.
It features a Lemmy compatible API, allowing for seamless integration and migration for existing Lemmy users.
Unique to Sublinks are its enhanced moderation tools, tailored to provide a safe and manageable online community space.
Embracing the fediverse, it supports the ActivityPub protocol, enabling interoperability with a wide range of social platforms.
Sublinks is not just a platform; it’s a community-centric ecosystem, prioritizing user experience, content authenticity, and networked social interaction.
See:
Rules
- Follow rules of discuss.online
- Keep topics related to Sublinks
- For support use !sublinks_support@discuss.online
founded 5 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Sure, why not? I have a couple of questions following a list of observations.
The About page says it's a Java Spring Boot application, though... so the Go component is limited to a federation service?
The docs are all stub pages, so it's a hard to figure out what it's all about, and the Demo link leads to a standard Lemmy instance, complete with "Support Lemmy" hamburger menu entry. What's differentiating this project, and what's the motivation?
So of the projects under the github umbrella is the federation service (which you clearly state is the problem domain of this component). There's quite a bit of scaffolding in that project; is the issues list of (8 currently) enhancements the sort of thing you're looking for help with?
Yes, the about site needs a lot of work. The demo site is using the Lemmy frontend but Java Springboot backend. The whole intent of the first milestone release is to be a drop-in replacement for Lemmy. It's after that where we will differentiate with things like better moderation/admin support, etc... The federation service will be built in Golang. And yeah, we need to do a lot more work on outlining what work needs to be completed in the form of issues. Those 8 for sure are things that need to be done though.
I just need motivation. If you'd write up a why (like, expand on your response in the wiki), what the differences will be, the benefits, and so on, that's really the minimum needed to get people onboard and chipping in.
Oh, and probably a clarification of the governance and license; nobody wants to contribute a bunch of work to a project just so someone can go monetize it.