A preference feature to make it so that users can opt out of seeing other userās css modifications is a front-end thing. Anyone suitably motivated could contribute that.
I was thinking about this yesterday. This seems most reasonable solution. User A gets to express themselves through their CSS. Meanwhile User B chooses to opt out of css-mod so that they donāt have to put up with bad UI. Win-win for both.
One suggestion I have, this opting-out should be the default setting.
Hmmm ⦠Iām no so sure. Youāll never discover the world of wonderful custom pages if youāre opted out automatically. Why not have it so that you can opt out when you find it objectionable?
Then you should stop asserting how easy or hard something would be to implement.
Itās easy to say āthis should be relatively easy to doā when you have no intention of helping do it.
Saying āthis should be easy to implementā is like putting up your hand to do it.
Actually, itās totally different to voice, and it is very easy to police: someone reports it, you see it, and you remove it. This is like obscene avatars, which pop up from time to time. Very easy to police: itās right in our face.
I saw voice as difficult to police when I was envisaging it being a āopen relayā for the voice, with little if any trace of what was said. It we did voice-over-chat, that would be different, because the voice would persist (and interestingly would be there for everyone to listen to!)
Youāre definitely on to something here.
It strikes me that this possibility would have to make us think about removing the capability.
It might also apply to custom avatars, which get objectionable content in them from time to time as wellā¦
Very much disagree. Defaults matter, and that default would result in most players never seeing the work people put into these
I think more reasonable would be a text-box in settings for a line-separated list of players you donāt want to see the custom css for, so you can just block a player with bad UI (though Iāve not encountered that)
Why do you have so many fears? Online is not a perfect world, even players can still easely cheat their ranks on OGS.
Did you ever see a profile here with a porn picture?
Relax, take some holiday I dunno. What matters is to trust a bit more in the qualities of the users, bad attitudes are like unavoidable but still manageable without having to put cameras and police everything.
This sounds like kind of question that asserts the answer is obvious
But itās more subtle than that: it comes down to āwhat is the nature of the objection, and how many people experience itā.
It might be true that most people like encountering some user customisation, and only a few people find it objectionable.
Why then would you put the onus on everyone to have to try it out by turning on some obscure settting?
TBH, I feel like if the feature is worth having, itād be worth having it turned on by default.
Personally I think we should not have it at all. I have yet to experience āvalue addā arriving at someoneās profile and finding it all āartisticā. Iām typically going to someoneās profile to find something out, and having the layout appear in an unexpected way just get in the way⦠but I can see how someone finds this fun.
I just remind people about their fears. I agree it is not fair.
OGS want to be over moderated. I mean they want potential ability to police everything. I am of the opposite opinion. Moderation is necessary. But potential difficulties with moderation should not be an obstacle for new features.
Nevertheless it is good motivation to prohibit custom CSS.
I donāt think you should feel obligated to contribute to a project, but I also donāt understand why you go on crusades about features like this. Like if you really care about it that much, why not submit a PR?
Uhm, I think Mikhail already said that heās not a coder ā and I believe that one should not be required to be an expert in the field in order to have a strong opinion.
How does user interface design relate to coding? Coding is easy. Unfortunately perfect knowledge of CSS specifications will not give you anything in this field.
The only valid CSS could break the UI. Invalid do nothing. Coding is nothing here. Coding skills are required but not enough.
I donāt get it. Iām not an expert in UI (please donāt mix UI and coding skills). It is true. But why canāt I have a strong opinion? Reasons may be different.
Even you have a great reason to support the ban of CSS.
As you said, it is based on imagination, not expert skills. So being an expert is not necessary.
Mikhail clearly knows enough to get started coding a preference to disable a feature if he were inclined: he keeps sharing detailed opinions about implementation details of this and other features, and his impression about how easy it all is. How can you say ācoding is easyā if you donāt know how to do it.
He is ājust a userā by choice. Which is absolutely fine.
What I personally feel is not fine is someone who is ājust a userā when it is convenient in a discussion, but also wants to be a developer when they want to influence the choice of what is implemented by pointing out how easy it is. āThis is easy, you should do it (but Iām not going to)ā simply rubs me the wrong way.