I really dislike the attitude that open source maintainers should adapt their code to comply with any bullshit requirements from random companies just so they can use the code.
Be grateful that someone wrote code for you to use freely.
On the plus side, adding profanity once it is scanned for sounds like another way to weed out some commercial use without explicitly weeding out some commercial use..
That could be handy to an already annoyed maintainer.
And I suspect that it is not an accident, and that the founders were well-aware that "Peor(ia)" carries negative connotations not only for Jews and Christians (Nm 23-25, Dt 3), but also for anyone who spoke Spanish--it would be like "Let's move to Shitty Heresy-Scandal Town? No thanks!"
If it's open source everyone is allowed to create derivative works. That includes companies with a stick up their ass. They should get their shit together and god damn fork it themselves. Or if everyone able to do it left because of this type of bullshit they can put their money where their mouth is and fucking pay someone to maintain a 'cleaned up' fork on their behalf.
> For your information, bad language is banned in most organizations and, therefore, if you are interested in having adoption of your Open Source, it is good practice to avoid such language.
> If you are not willing to receive contributions from the community, if you are not interested in your Open Source contribution gaining adoption, or if you prefer people to sign special agreements to make contributions, perhaps you are better off closing down your repository, making it private.
How about, if I release something for free, that I made on my own time, anyone can feel free not to use it if they don't like how I've written it.
I don't think I've even sworn in a public repo. I try to keep it professional. But if I did, and someone has a problem with it, they can write their own fucking software. They're not paying me to cater to their whims.
I hope this message finds you well. From ScanHN, we are constantly reviewing Hacker news comments and noticed the use of language that could be considered vulgar or inappropriate on one of your repositories.
As you have posted your comment as Public Comment, it's important to maintain a professional and respectful tone throughout the discussion. We kindly ask that you refrain from using such language and update your submission accordingly.
Your contributions are valuable to all HN community, and we appreciate your understanding and cooperation in this matter. If you have any questions or need assistance, please feel free to reach out.
I hope this message finds you well. From ScanHN, we are constantly reviewing Hacker news comments and noticed the use of language that could be considered vulgar or inappropriate on one of your repositories. As you have posted your comment as Public Comment, it's important to maintain a professional and respectful tone throughout the discussion. We kindly ask that you refrain from using such language and update your submission accordingly.
Your contributions are valuable to all HN community, and we appreciate your understanding and cooperation in this matter. If you have any questions or need assistance, please feel free to reach out.
This is managerware. The company behind this focuses on generating bills of materials for software projects. They're targeting checklist based management.
Some people got upset that the default dictionary for some compression standard, I believe Brotli, which you practically have to use and ship for compatibility with standard servers, contains words like "fuck". That's the kind of people that would like their software chain to be swear-free, just in case a customer hits ctrl+u on their React application and reports seeing all kinds of naughty words to upper management.
I try to use profanity rarely in public writings, and then usually to demonstrate a specific point.
Anyone who goes through the trouble of implementing a profanity filter that would prevent them from seeing something I've written is probably someone I wouldn't want to deal with anyway. That is, if a rare cuss word offends their delicate sensibilities, other things I say would likely give them an aneurysm. Ergo, me occasionally cursing may be good for both parties if it keeps me off their radar.
I don't understand. ScanOSS has a bot that scans ScanOSS's own repo, so what's the issue?
What I see is that the bot was badly programmed and it did not ignore quoted text, so the first automated report triggered another bot response which quoted the swear word which triggered the bot a third time.
They are/were scanning random public projects and creating unsolicited bugs in those projects to chide them about profanity in their source code. The linked thread is just a bunch of the victims of that spam having some fun with the format.
Exactly. When I made that comment I never thought It'd go this for or that the CTO of a ScanOSS would be this dense, so the opening of the thread is admittedly a bit confusing. I still had the email from the bot's original issue being opened, so I thought I'd point out their hypocrisy.
Who asked for this? Who demanded this? What is the problem that these people are trying to solve? What I'm trying to say is what the fuck is wrong with these people?
"As you have marked your project as Open Source, it's important to maintain a professional and respectful tone throughout the codebase."
The only proper response to this is: "No. It's not. Fuck you. Fuck your mother, and fuck the fucking horse you rode in on, may you eat shit for the rest of your days and choke on it."
I mean, who even comes up with notions like this? What law of universe is there that dictates what attitude I must have when marking my software as open source?
I'm not sure if others can see the comments of mine "marked as abuse"
Those are
---
Oh! Looks like I still had my response to your bot open, so here was my raw, unfiltered, and (Oh no!) vulgar original thoughts, before I toned it down to comment here:
@scanoss
OOPS! Did I swear in my own repo? My bad.
Cursing, and how the open source community represents itself, are - and I can not stress this enough - not a business-polite thing. You're welcome to fork (Within my license terms) and remove them, but given part of open source and a healthy hacker ethos is the counter-culture vibe that made the technology I'm sure even you yourselves use possible, you can
[in fancy unicode text, unsensored] Go F* yourselves
What you're doing is not helpful to the OSS community, it's helpful to your business partners that profit off open source, and given the trend in industry, do so typically without giving back. You want to do something meaningful? Drop a recurring sponsorship of my website so I can take more time to write guides and cool things using whatever language I choose to best convey my intent and feelings.
Hey @agustingroh it looks like you're the most frequent committer on SCANOSS repos, thought I'd nudge this to get some attention brought to it. Still awaiting an apology myself, though at this point needing to ask for it makes it rather moot personally, it would still be nice for everyone else SCANOSS spam'd.
---
How they decided that second one is "abuse" is beyond me, but as you can see, while a bit less vulgar, I was, indeed, pissed off.
> "No. It's not. Fuck you. Fuck your mother, and fuck the fucking horse you rode in on, may you eat shit for the rest of your days and choke on it."
That's the quiet part you're not supposed to say out loud on Github, because the language police that made the issue will get salty and get your account restricted.
reply