Update on this request: A developer approached me and is not only helping me with review and fix security issues. We found quite concerning security issues, so I think the decision to have another person look at this was right one.

We discussed and found that we need to do following work

1. Redo backend/api so it is more robust, while doing that it will also become Lemmy API compatible
2. Fix client so it adapt to any API changes
3. Move from cloudflare workers to docker, so it can be self hosted
4. Move from D1 to postgres (D1 has 10GB limit, ClubsAll db is already 5GB), so it is scalable
5. Move production to a VM or k8s cluster so we can host our own DB, backend and frontend instead of CF workers

We have some work to do but will have a good product at the end of it. We will update further once we get this work done. Thanks to everyone to your thoughts and offers to help.

Typescript, Next, Cloudflare

I think lemmy left a lot to be desired.

Agreed, closed source is not a guarantee, but it does help. We are not hacked so far, so that's good enough for me :-)

you can probably reach out to people here

I have asked in this and other thread. Should I make a new post?

Question for everyone here, how is everyone paying for hosting and development costs? While profit is not my motive, break even is needed for long term sustainability.

Do you have any idea of the timeframe when you’ll be able to open source the project?

I replied in the other thread, copy pasting here: Open sourcing is not time dependent. I just need

1. security review by someone experienced to make sure we do not instantly get hacked as soon as we open
2. and some commitment to fix critical bugs and hacks that will kill ClubsAll or steal resources

what are the languages used to develop ClubsAll Ah, good question. It is typescript, next, React, Cloudflare

Open sourcing is not time dependent. I just need

1. a security review by someone experienced to make sure we do not instantly get hacked as soon as we open
2. and some commitment to fix critical bugs and hacks that will kill ClubsAll or steal resources

why were you forced to release it when your developer left? I think I should have released much earlier and developed with input from community. So developer leaving was a trigger to do it. Also, sitting on it would just demotivate me, degrade the code and it would have possibly died a silent death before release.

If you assume that investment returns are only in dollars, then yes. Investments can be into non profits, communities etc. with non monetary returns like creating a community, gratification and so on. In this case, my long term goal (return?) is de-enshittification of reddit and hopefully more later on.

Hi everyone, I’m Vinay, the founder of ClubsAll. I’ve noticed some negative sentiment, and I can understand why. I’ll do my best to clarify all the questions raised here.

https://clubsall.com/c/fediverse gives a 404, hiding posts such as the one we’re in. Very early censorship? Their approach to combining similar communities into one club could be the cause, and maybe they just haven’t set up the c/fediverse club yet.

Lemmy is too big to show everything. To keep costs low and due to some technical constraints with hosting, we had to prioritize what would be most useful to the broader community. If we show everything, the database won't be able to handle it, and I won't be able to afford the hosting costs.

There is no mention that this is content from lemmy.world. This is intentional. For federated servers to really compete, complexity needs to be eliminated. One of the goals of ClubsAll is to simplify everything, so we hide servers, instances, multiple logins etc that can be confusing and overwhelming for a new user. We're innovating and trying something different to help the Fediverse succeed. However, if we’re violating any community guidelines or site policies, please let us know.

This looks like a clear monetization attempt. We just launched. Please give us time to survive and implement features before jumping to conclusions.

They’re not contributing, and we don’t need proprietary cancer in the Fediverse.

Sorry you feel that way. Keep in mind that we built everything from scratch. Federation is not currently implemented, and we’ll need time.

Personally, I hope they open source, because the interface is visually appealing and quite fast. What I expect is most instances defederating from them soon, killing the product in the process.

Thank you for the compliment! I do intend to open source ClubsAll once I get some help. I truly appreciate the feedback and hope we are not defederated.

Being a single site, it might draw the wrong crowd and end up having serious moderation problems.

This is insightful and another reason for us to prioritize federation.

Seems to bring us back to the current Reddit situation with extra steps.

That’s a valid concern. However, I’ll open source the project once I get some assistance, which should alleviate some of these fears.

If you query it like a federated platform would, it returns HTML rather than the required JSON.

Keep in mind, ClubsAll was built from scratch and is funded entirely out of pocket. We’ve done as much as we can with what’s currently online (and a couple of new features are coming soon that I’m testing).

It seems to be a project where missing features are likely due to it still being at an early stage.

That’s exactly right. This is the main reason. Unfortunately, our developer recently left, so we’re at a bit of a feature freeze for now, aside from a couple of things coming soon.

Lack of details on how they implement federation.

We built federation from scratch, so many features are still missing. Currently, we don't federate, so it’s not possible to follow from elsewhere at this time.

Hi everyone, I’m Vinay, the founder of ClubsAll. I’m happy to answer any questions and would like to address where I think ClubsAll might be misunderstood.

“I think it’s unfair for them to federate all our posts and comments, making their platform seem busy, while they don’t allow federation of their own content or self-hosting.”

I completely agree with this concern. However, it’s important to note that ClubsAll is still in its infancy. We currently have around 10 upvotes on Product Hunt, with a nearly non-existent active user base or content. So even if we implement federation, the activity level would be minimal for now.

“We could establish a federation policy across instances, ensuring no single-direction federation of content.”

This proposal seems fair. I’d like to suggest an additional condition: “No single-direction federation of content once an instance reaches a certain level of activity, say, X posts per day.”
The reasoning here is that new and small instances like ClubsAll need time to grow and develop their features before being subjected to such rules. This approach ensures that very young instances aren’t immediately blocked, especially when they might not have much content anyway.

There’s also been talk about defederation. I want to be transparent – ClubsAll is bootstrapped and we have invested a lot of money and sweat to help the community. Right now even my developer has moved on, so new development has halted. This is why I was forced to launch.

If the community chooses to turn against ClubsAll, it won’t survive. That said, I’ll leave the decision to you. Defederation would immediately kill it. If defederation is the path chosen, then so be it.