I did understand, but my point still stands: what we have may not be ideal, but it works well enough. The developers volunteering their free time, harmonizing their contribution with the demands of their personal lives and professional careers, it’s understandable that they choose their fights, so to speak, and prioritize.
I don’t know the inner workings of OGS, if it’s facing any Pressing Issues, but I can think about stuff I would categorize as more pressing than implementing the option to disable the profanity filter. There are 199 open issues at the moment, and glancing at the list I see a number of items that others might find more frustrating:
Anyway, I doubt the devs are even aware of the matter you’re pointing out—at least I haven’t seen it mentioned before, so there’s that. You can always start a thread at the development section or submit an issue of your own.
But the beauty of it is that we don’t even have to wait for a change to take place. OGS’s interface is open source, anyone can contribute. If we’re really keen on a particular improvement, and if we’re willing to put some time it, there’s always the option of implementing ourselves.
…while using a netbook dating from the Mesozoic Era, one that turns itself off whenever someone sneezes in Japan, literally requires a screwdriver to be turned on again, and seriously considers melting should I use it for anything more elaborate than running Nethack, working during stolen hours between putting down metaphorical fires, starting a business, studying, and occasionally making a few absurd moves in correspondence Go matches.
If nothing else, I can say I understand the constraints OGS’s developers have to deal with, working and making do with limited resources, which is why I took the time to write this in the first place. But more importantly: if, despite my own limitations, I was able to do a little bit to fix an issue that bothered me, others can do even better. I mean, this community is filled with some rather amazing individuals.