ScanOSS spams OSS projects for using profanity
github.com
github.com
That could be handy to an already annoyed maintainer.
https://en.wikipedia.org/wiki/Intercourse,_Pennsylvania#In_p...
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.
</rant>
It’s open source, that means you do the work, and we get the outputs of your effort plus support when we require it, all for free, duh.
Clearly, if you didn’t want to do that, you wouldn’t have made it open source!
/s
> 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.
It’s almost as if it’s a school project, written by a student. “Write something on x topic with y constraints to get the grade”
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.
The next table summarizes our detections:
https://news.ycombinator.com/item?id=41712509
Word 3
fuck
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.
The next table summarizes our detections:
https://news.ycombinator.com/item?id=41712571
Entirety of line 6
fuck
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.
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.
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.
This should save some time hunting for the link in GitHub's UI
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?
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.
That project was https://github.com/VegaDeftwing/opinionatedguide in case you interested in fucking sponsoring me <3 I would really fucking appreciate it!
--- and ---
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.
They can, but they need to be logged in and manually click on 'show comment'.
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.
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.
...tho I also wish I can get a cookie with it too that would be nice