|
|
|
|
|
by rpdillon
4 days ago
|
|
What conversation are you trying to have? I don't even use Codeberg; I've spent years thinking about how the idea behind rules manifests when those rules are actually put in place and enforced. I think a lot about second and third order effects. That's my interest here: an org decided to put these particular rules in place, and based on my experience, I don't think it's going to age well. But I guess you're right, as far as you go: none of this is my problem. I'm just a curious observer. |
|
I did you wrong, and in general we shouldn't guess the motivations of others, but I'll still say that lot of the comments asking what is the exact meaning of that rule is, how it will get enforced precisely, strike me as seeking to undermine the validity of their decision rather than wanting to make sure they don't run afoul of it. Or even coming up with ideas to help them enforce that rule better. One even said maybe we should test if they actually can tell. I responded to you as if responding to that, and that was uncalled for.
Take the HN guidelines, for example. It's impossible to make them completely "clean cut" rules. But people know that if they genuinely think there's been a misunderstanding they want to clear up, they can contact HN. And with Codeberg it's probably like that, too. Not like Google, where the rules ideally should be 100% clear and mathematically accurate, because you just get nuked by algorithms with no recourse.
You might even say if people post on HN, they already understand what fuzzy rules are, by definition. They know language is fuzzy and that the letter of the law points at the spirit of the law. If someone doesn't want to understand that spirit, no amount of legalese detail will make them understand it. But of course that shouldn't be an argument to shut down discussion about it, either, and I didn't mean it like that.