I didn’t specify anything because half of the entire frontend needs to be fixed, starting with the home page. The alternative is to make a separate thread for the Play page, the logged out version of the home page, the logged in home page for returning users, the cockpit meme settings page, etc. I’m not interested in doing that. I intend to make one final push to fix a lot of the flaws with OGS’ frontend before I move on to other projects. It’s been a decade and OGS still has the reputation of being a strong backend with an outdated frontend, and that gap is only going to widen as time passes. To me, that warrants a discussion that prioritizes speed and holistic website improvements over being pedantic.
Feel free to disagree, but this is my contribution after playing Go exclusively on OGS since 2022 and I don’t want to debate it considering it feels like less than 20% of the things I want to change will be implemented within the next year.
In this community, you see people brushing off valid UI concerns like Private chat blocks game chat because “DM is such an infrequently used feature that it’s probably not a priority.” What do I stand to gain in meticulously separating my suggestions if this is the type of response they get? This community has gotten too used to UI/UX problems being swept under the rug and taking years to update after consulting with statistics, polls, etc.
When I ran my own website (not a Go server, a management platform for a niche video game), I usually fixed these types of concerns within 12 hours of them existing. There were some difficult UX problems that took me weeks to figure out how to fix, but I never ignored them. I’d rather go back to doing that than fit into this kind of rigid system and make highly detailed specifications have a ~30% chance of being implemented. In fact, this might be a reason why you see so many talented developers starting their own Go servers instead of contributing to OGS.