• 2 Posts
  • 14 Comments
Joined 4 months ago
cake
Cake day: October 12th, 2024

help-circle




  • You have a reasonable argument that it is not possible for everyone to come up with common rules.

    The issue is that there are numerous posts instigating and encouraging everyone to defederate. But without a clear definition of what is acceptable. In other words, this approach makes it very hard for anyone from building anything new and participate in federation. So this seems against the goal of “open network” and discourage others from doing anything new.

    If that is the goal, then I cannot really win here. If that is not the goal, then I ask not to make such posts and not to encourage everyone to defederate. Anyone who has an issue can reach out to me and I can address their concerns.

    Is that reasonable?


  • We fixed the attribution. Now usernames show up as /u/<user>@<server> (rather than earlier /u/<user> and no server). Also the server name can be seen in the right bar. Let me know if this fixes the main issue you had.

    Also for a deadline of federation will you be ok if I commit to doing it before we have 100 active users a month? (since our comments are federated out, it is easy to see how many active users we have. I can also report whenever someone asks).





  • Hi there, I am creator of clubsall. We absolutely do care about community.

    There were many discussion few months ago. There were also private discussions with some admins. Because we are not lemmy based, so our development takes time (plus my developer left, plus we were trying to move to sublinks which itself has federation issues). So federation for us is not a config setting. Also, we are a very niche site with almost no traffic.

    Additionally, different admins feel different rules are fair, so it is hard for us to know how to be good community members. I request a common set of rules, preferably based on traffic, so any newbie can get the breathing room to develop and participate. Does that sound fair?





  • 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.