vinay_clubsall

Our challenge has been that many people feel differently to what is fair. So I have been requesting if all admins can agree to a common set of rules so we can comply with it and be upstanding community members. Is that reasonable request?

Thank you. I request the defederation being traffic based rather than time based. Would that be fair?

Hi there, I am creator of clubsall.

Please see my updates. We are not intentionally blocking federation, we just do not have that capability (as we are not a lemmy instance). So I am requesting common fair set of rules, so I can save clubsall.

Hi there, I am creator of clubsall. There are a lot of adhoc discussions and rules. Some discussions such as this one does skip my notice too. So it has been very difficult to be fair and run a new instance. It seems anyone trying to build a lemmy competitor is being killed. If that is the rule, lets state that and I will kill clubsall myself.

If not, can I request a discussion or at least a set of rules that we should comply to so I can save clubsall?

@snowe@programming.dev @Ategon@programming.dev @mp3@lemmy.ca @ada@lemmy.blahaj.zone

@Nothing4You@programming.dev

The idea was to simplify federation for a non tech user. I believe that is literally why ActivityPub is not able to effectively compete.

We are trying to simplify by hiding all complexities. If we try nothing new, the results will not change. There have been many threads about ClubsAll and everyone disagrees what is fair and unfair, so it has been difficult for us to comply. Would it be fair to ask for a common set of rules to be fair to everyone and give me a chance to save clubsall?

Please include me

Hello @haverholm@kbin.earth and @jwr1@kbin.earth I am the creator of Clubsall. Please see my update above. Based on previous discussion, I was under the impression that until there is meaningful traffic, it is ok to give us time to implement federation. There were a set of rules proposed in another thread. However, seems like the rules were not finalized or not accepted or not distributed. If those rules are not acceptable, can we have a discussion first so we can agree what is fair and I have a chance to save clubsall?

Hello @Chozo@fedia.io and @jerry@fedia.io I am the creator of Clubsall. Can we have a discussion first so we can agree what is fair and I have a chance to save clubsall?

Hello Blaze,

One request, whenever you post about clubsall, can you please tag me so I can also participate? Thank you.

As for this discussion, when we had a discussion last time on reddit, I thought we agreed that as long as there is not meaningful traffic, it should be ok. I guess you were not fully onboard with this.

My request with all admins is - can we agree on some rules. If we block all new sites on hunch or rules as we make up, it will kill anyone trying to do something new.

There was another thread (that I cannot find now) where some rules were proposed. (If someone can find, please reply to this).

There are 2 things being discussed

1. federating out
2. open sourcing clubsall

I can give an update on both of these. As I mentioned previously, someone was helping me in doing some audit, implementing federation and then we could also open source. We were going to use “sublinks”, which would do a number of upgrades. So that seems the right choice moving forward. It will allow self hosting, federation, move to postgres, move to docker etc.

However during implementation we found that sublinks itself does not implement federation out. So we were blocked by that. I checked with developer just few days ago and I was told that since all developers are volunteers and they got busy, federation was delayed. The work will pickup again in new year.

I am not sure when they will be able to finish federation. I can quickly move there once done. However that seems months away.

In the meantime, can we have a discussion about a set of rules for clarification and fairness?

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.