If shame worked, then slop reports would've stopped being made already. Public ridicule only creates a toxic environment where good faith actors are caught up in unnecessary drama because a maintainer felt their time was being wasted. Ban them, close your bug bounty program, whatever, but don't start attacking people when you feel slighted because that never ends well for anyone (including curl maintainers)
We will ban you and ridicule you in public if you waste our time on crap reports
51–60 of 653 posts
Re: We will ban you and ridicule you in public if you waste our time on crap reports
#52I've been helping a bit with OWASP documentation lately and there's been a surge of Indian students eagerly opening nonsensical issues and PRs and all of the communication and code is clearly 100% LLMs. They'll even talk back and forth with each other. It's a huge headache for the maintainers. I suggested following what Ghostty does where everything starts as discussions - only maintainers create issues, and PRs can…
Re: We will ban you and ridicule you in public if you waste our time on crap reports
#53Earlier quoted context omitted.
>Indian students How do you know this?
Because their usernames are Indian and profiles have links to Indian universities, and sometimes descriptions of the 101 classes they're currently taking. That doesn't stop them from saying things like "I see this sort of vulnerability all the time"
Re: We will ban you and ridicule you in public if you waste our time on crap reports
#54Earlier quoted context omitted.
To be clear, no, it is not, because of the opportunity cost of all the other slop. That's what this is all about.
Then no bug reports and no fixes. Sounds good enough.
Re: We will ban you and ridicule you in public if you waste our time on crap reports
#55And then maybe they will give you money.
Re: We will ban you and ridicule you in public if you waste our time on crap reports
#56I've been helping a bit with OWASP documentation lately and there's been a surge of Indian students eagerly opening nonsensical issues and PRs and all of the communication and code is clearly 100% LLMs. They'll even talk back and forth with each other. It's a huge headache for the maintainers. I suggested following what Ghostty does where everything starts as discussions - only maintainers create issues, and PRs can…
[flagged]
Re: We will ban you and ridicule you in public if you waste our time on crap reports
#57I've been helping a bit with OWASP documentation lately and there's been a surge of Indian students eagerly opening nonsensical issues and PRs and all of the communication and code is clearly 100% LLMs. They'll even talk back and forth with each other. It's a huge headache for the maintainers. I suggested following what Ghostty does where everything starts as discussions - only maintainers create issues, and PRs can…
>Indian students How do you know this?
Re: We will ban you and ridicule you in public if you waste our time on crap reports
#58I've been helping a bit with OWASP documentation lately and there's been a surge of Indian students eagerly opening nonsensical issues and PRs and all of the communication and code is clearly 100% LLMs. They'll even talk back and forth with each other. It's a huge headache for the maintainers. I suggested following what Ghostty does where everything starts as discussions - only maintainers create issues, and PRs can…
>Indian students Resume glorification and LinkedIn / GitHub profile attention do that. I am seeing a lot of people coming up with perceived knowledge that's just LLM echo chambers. Code they contribute comes straight out of LLMs. This is generally fine as long as they know what it does. But when you ask them to make some changes, some are as lost as ever. Torvalds was right, code maintenance is going to be a headache…
Thanks to their LLM reliance they'd soon not know what it does, and forget even the little they know about coding
Re: We will ban you and ridicule you in public if you waste our time on crap reports
#59> We will ban you and ridicule you in public if you waste our time on crap If shame worked, then slop reports would've stopped being made already. Public ridicule only creates a toxic environment where good faith actors are caught up in unnecessary drama because a maintainer felt their time was being wasted. Ban them, close your bug bounty program, whatever, but don't start attacking people when you feel slighted bec…
Shaming does not work, you look like an idiot, people will start to despise you and then you end up ostracizing yourself from the rest of the community and the only ones left within your bubble, are circle jerk assholes.
It's one of those cases where you end up causing more harm than the ones you were complaining about.
Just pathetic behaviour.
Re: We will ban you and ridicule you in public if you waste our time on crap reports
#60I've been helping a bit with OWASP documentation lately and there's been a surge of Indian students eagerly opening nonsensical issues and PRs and all of the communication and code is clearly 100% LLMs. They'll even talk back and forth with each other. It's a huge headache for the maintainers. I suggested following what Ghostty does where everything starts as discussions - only maintainers create issues, and PRs can…
volume of low quality content, dsa/leetcode, etc. is so high, good people/content gets left out. networking, connections, nepotism so much high. getting job based on actual talent very rare.
MNCs which are good outside are so much sh8t here; well capitalism doesn't give a f8ck anyways.