Conversation

Notices

1. Embed this notice
   akkoma flavored lizzy (fleckenstein@lizzy.rs alt) (lizzy@social.vlhl.dev)'s status on Thursday, 17-Apr-2025 00:08:06 JST akkoma flavored lizzy (fleckenstein@lizzy.rs alt)

   • azure
   • kimapr
   @kimapr @azureazure yea xnfm is why i didn't just block it right away (and got pretty confused) but that opinion combined with the 4chan talk just struck me as a certain type of shitty being. I'll await whatever it will say about it tho
   • Johnny Peligro likes this.
   • Embed this notice
     a bean (coolbean@linfan.moe)'s status on Thursday, 17-Apr-2025 00:08:54 JST a bean

     in reply to

     • azure
     • kimapr
     @azureazure @lizzy @kimapr honestly i think i kinda get it. its a very formalised way to deal with bad actors that maybe kinda probably dont deserve that level of effort. conditional acceptance ("so long as you dont do this within the realm of this project") when really you should just tell them to get bent out of principle
     
     but then again. i actually like sqlite style development (a core team of privileged devs actually doing development with informal coordination instead of a core team of maintainers coordinating development amongst strangers) specifically because you can avoid those situations outright
     Johnny Peligro likes this.
   • Embed this notice
     azure (azureazure@social.xenofem.me)'s status on Thursday, 17-Apr-2025 00:08:55 JST azure

     in reply to

     • kimapr
     @lizzy @kimapr ????? whats wrong with thinking that codes of conduct kinda suck i dont get what youre on about
   • Embed this notice
     a bean (coolbean@linfan.moe)'s status on Thursday, 17-Apr-2025 00:09:07 JST a bean

     in reply to

     • azure
     • kimapr
     @lizzy @azureazure @kimapr fun fact: this is based on the rule of saint benedict. they are benedictine software monks
     Johnny Peligro likes this.
   • Embed this notice
     akkoma flavored lizzy (fleckenstein@lizzy.rs alt) (lizzy@social.vlhl.dev)'s status on Thursday, 17-Apr-2025 00:09:08 JST akkoma flavored lizzy (fleckenstein@lizzy.rs alt)

     in reply to

     • azure
     • kimapr
     • a bean
     @coolbean @azureazure @kimapr sqlite has this tho, lmao https://sqlite.org/codeofethics.html
   • Embed this notice
     EmoDagda (dagda@netzsphaere.xyz)'s status on Thursday, 17-Apr-2025 00:10:22 JST EmoDagda

     in reply to

     • azure
     • kimapr
     • a bean
     @lizzy @coolbean @azureazure @kimapr
     I see it often used to police views someone holds privately. Free software will become less resilient if contributing to anything means terminally cop-brained activists will search through anything you ever said anywhere. Let's be down to earth here: most tech-minded people, especially high-achieving ones, have some form of neuro- or personality quirk. Isaac Newton would immediately be cancelled today.
     Also most big tech firms have CoCs by now, do you seriously think anything at Oracle will improve by them saying "we the good beans btw 🫶🏳️🌈🏳️⚧️"? It's cop-and corpobrained as a concept
     Johnny Peligro likes this.
   • Embed this notice
     akkoma flavored lizzy (fleckenstein@lizzy.rs alt) (lizzy@social.vlhl.dev)'s status on Thursday, 17-Apr-2025 00:10:24 JST akkoma flavored lizzy (fleckenstein@lizzy.rs alt)

     in reply to

     • azure
     • kimapr
     • a bean
     @coolbean @azureazure @kimapr i see CoCs mostly as a signal to people that you're a community that cares about this. your project might have a good track record of keeping bad actors out, but how will people know that if there's no documentation or record of these efforts?
   • Embed this notice
     a bean (coolbean@linfan.moe)'s status on Thursday, 17-Apr-2025 00:10:25 JST a bean

     in reply to

     • azure
     • kimapr
     @lizzy @azureazure @kimapr i get the intent, the problem is that this logic doesnt actually hold up. no moderation actions are taken until someone violates the coc, this allows bad actors to remain present in the community and potentially victimise people anyway through simple rules lawyering
     
     on alternatives: not having a (public) code of conduct doesnt proclude you from taking action moderating the community therefore the existence of codes of conducts is primarily to shield maintainers from criticism when they take action or leverage criticism against them when they dont.
     
     do take note that i specified "(public)". keeping internal guidelines for consistency and potential coordination with other moderators does have merit. tldr: rulebooks dont keep out bigots, you do
   • Embed this notice
     akkoma flavored lizzy (fleckenstein@lizzy.rs alt) (lizzy@social.vlhl.dev)'s status on Thursday, 17-Apr-2025 00:10:26 JST akkoma flavored lizzy (fleckenstein@lizzy.rs alt)

     in reply to

     • azure
     • kimapr
     • a bean
     @coolbean @azureazure @kimapr
     
     > bad actors that maybe kinda probably dont deserve that level of effort
     
     justice is not supposed to be about the perpetrators, but about the victims. a project having some sort of code of conduct or rules / behavioral standards or whatever in place is a safety guarantee people who are often the subject of harassment, for example for marginalized people. maybe it's not the ideal form, but what even is the alternative for projects that *are* community driven? of course stating explicitly that assholes will not be tolerated shouldn't even be necessary in the first place but the reality is that in many places they are tolerated and even celebrated and such an explicit pledge is a thing that genuinely makes people feel more safe
   • Embed this notice
     Johnny Peligro (mischievoustomato@tsundere.love)'s status on Thursday, 17-Apr-2025 00:10:52 JST Johnny Peligro

     in reply to

     • azure
     • kimapr
     • a bean
     • EmoDagda
     @dagda @coolbean @lizzy @azureazure @kimapr it could be simple stuff like "dont stir shit" i suppose but I'm very laid back