I can’t see the total number of active games I have on my main page anymore. I also can’t see the number of games pending my move on the top right after I scroll down to select the games to play. I use that to judge how many games to play so it’s a bit inconvenient. I still think that the widgets on the main page should be an option and not set for everyone.
5 Likes
I agree. I tried editing the open source code to fix it a couple days ago, but it felt like a mess. I didn’t understand the purpose of some things in the code (like the shouldRender() function) and I kept getting errors related to installation/setting up the development environment so I couldn’t even test my changes. They did not make it pleasurable to contribute to the open source code at all IMO.
I’m just going to work on my own website, and I’m sure I’ll fix UI problems like this within hours of receiving feedback. A few months later I might make my own Go server designed for playing correspondence games too. Having a small playerbase shouldn’t be much of a problem for correspondence games.
2 Likes
This is a couple of pages to help you get started like
but I think just reaching out to say @GreenAsJade or @benjito etc, I found that in my experience, and hopefully a few others, that generally contributions are very much welcomed, especially first contributors, and someone is happy to help you troubleshoot to get you up and running.
4 Likes
at all IMO
I have had a total opposite experience on this.
Sadaharu already linked to the relevant document for contributing guidelines. If you still have issue with something specific, I can help. You can DM me.
@Sadaharu Would you like something like this?
+1. I don’t promise the code will be clean or easy (it is a prod codebase, and I had issues getting started personally) but the community is helpful and welcoming in my experience.
do you have experience with AI tools? I feel like Claude Code may be able to blast through these for you.
If you’re not into AI, feel free to ask questions here of course 
it’s just a slower feedback loop.
I read the documentation fully and constantly jumped back and forth between it and the official Github documentation, why is everyone assuming I didn’t follow it? It wasn’t clear or streamlined enough. The fact that a “development environment quick start” is at the top instead of the section about forking and cloning is questionable, to start. I did that first and then had to delete and redownload everything to do the forking, cloning, branching stuff. And then there were still errors running `npm run dev`. On top of that, unclear/missing documentation on important functions like shouldRender() and the design system.
For a project that has been open source for so long, this is not what I consider welcoming. There was no direction to direct message anyone in particular either, so I don’t see why I should’ve done that. I’ve hosted my own React + TypeScript web app before, just not any open-source development experience, and I think I can make a better user experience in my own tech stack faster than I can understand this codebase.
This is something I offered out of my own good will to help.
I am not discrediting your frustrations. I am sure you had trouble.
This is what everyone feels when they have to work with legacy codebase 
1 Like
Yes the number was there before the upgrade and now it’s gone