claude MAX 20 fuckin X motherfuckerrrrr
-
@ariadne `these reports would almost always include "can you tell me more about your bug bounty program?"`
Most (if not all) random folks doing fuzzing on GCC/LLVM have resulted in academic paper rather than asking about a bug bounty program.Maybe that is because the first fuzzing done on GCC/LLVM was done by an university student/professor rather than say some company/random person.
So the motivation is different and most of the time both GCC/LLVM welcomes the fuzzers (even with duplicates filed). Though an ICE after an error is just pushed back to almost never want to fix line. And there was 2 weeks where these kind of fuzzing reports were being filed at rate of 10 a day. So it overloaded bug triagers (mostly myself).@pinskia I do welcome fuzzer reports, but I reserve the right to close them if they are nonsense.
-
@ariadne @whitequark Only "acceptable" if you disregard that the code they give you has no provenance. Their copyright claims on it and claims to be able to license it suitably for you aren't valid, and you have no idea who else might have copyright claims on it.
@dalias @whitequark in our world, this is applicable.
in the commercial world, it isn't, because they have lawyers who are OK with this, and that is ultimately what matters.
-
@ariadne I've watched competent engineers get less competent after spending a bunch of time vibe-coding, so I am not actually convinced that what you're saying is generally true except on the shortest timescales. But, again, this is in addition to what you're saying.
@whitequark oh, definitely. it is like any other skill, continuous practice is required to maintain it.
-
@dalias @whitequark in our world, this is applicable.
in the commercial world, it isn't, because they have lawyers who are OK with this, and that is ultimately what matters.
@ariadne @whitequark 10 years ago, Google's lawyers were so scared of clearly-non-copyrightable header files myself and the other authors declared public domain that they badgered me into reaching out to get explicit license grant from everyone.
Now they're fine with code of completely bogus provenance.
The world has been turned utterly upside down and I hate it.
-
@ariadne @whitequark 10 years ago, Google's lawyers were so scared of clearly-non-copyrightable header files myself and the other authors declared public domain that they badgered me into reaching out to get explicit license grant from everyone.
Now they're fine with code of completely bogus provenance.
The world has been turned utterly upside down and I hate it.
@dalias @ariadne @whitequark yep so much for their anti AGPL license stance.
-
as a reminder, i have a zero-tolerance policy for this garbage. you do not get to do shit work with an AI assistant, then sign off on it, and then blame the AI for getting it wrong.
I don't care.
you WILL be banned from my repos if you send me AI slop. end of.
@ariadne perfectly sane statement.
-
@starchturrets @ariadne "like"??? They are trying to get everyone hooked on this bullshit. I'm not convinced that the whole "AI psychosis" thing is actually a mistake.
@juliancalaby @starchturrets @ariadne
My company is forcing all of us to use AI or else.
They also wrotr scripts to track if people are using it or not, scripts built with AI... That obviously fail miserably at tracking the real usage metric.Freaking brilliant... Had to send an email today with my premium requests % in GH.
What was the saying when a metric becomes the target it seases to be a valuable metric?
The world we live in lately is... Brilliant.
-
@juliancalaby @starchturrets @ariadne
My company is forcing all of us to use AI or else.
They also wrotr scripts to track if people are using it or not, scripts built with AI... That obviously fail miserably at tracking the real usage metric.Freaking brilliant... Had to send an email today with my premium requests % in GH.
What was the saying when a metric becomes the target it seases to be a valuable metric?
The world we live in lately is... Brilliant.
@YvanDaSilva @starchturrets @ariadne I'm high enough up in the company that I work for that I'm able to tell the next level up that if they pull that sort of shit, I'm out, and that has enough weight that they haven't.
I am counting my lucking fucking stars.
-
@YvanDaSilva @starchturrets @ariadne I'm high enough up in the company that I work for that I'm able to tell the next level up that if they pull that sort of shit, I'm out, and that has enough weight that they haven't.
I am counting my lucking fucking stars.
@juliancalaby @starchturrets @ariadne my company imposed it on everyone regardless of seniority.
Yep. That bad. -
@ariadne @whitequark 10 years ago, Google's lawyers were so scared of clearly-non-copyrightable header files myself and the other authors declared public domain that they badgered me into reaching out to get explicit license grant from everyone.
Now they're fine with code of completely bogus provenance.
The world has been turned utterly upside down and I hate it.
@dalias @ariadne @whitequark Aaron Swartz died for nothing and it's so infuriating.
-
@ariadne @whitequark 10 years ago, Google's lawyers were so scared of clearly-non-copyrightable header files myself and the other authors declared public domain that they badgered me into reaching out to get explicit license grant from everyone.
Now they're fine with code of completely bogus provenance.
The world has been turned utterly upside down and I hate it.
the one constant thread in tech is that Google invariably fucks up everything it touches
CC: @ariadne@treehouse.systems @whitequark@treehouse.systems
-
the one constant thread in tech is that Google invariably fucks up everything it touches
CC: @ariadne@treehouse.systems @whitequark@treehouse.systems@khm @ariadne @whitequark Fortunately they only fucked up their own useless bugs-added-by-RIIC++ fork of musl (Fuchsia) that they seem to have eventually abandoned (like Google does with everything). They never had any access to upstream.
-
@khm @ariadne @whitequark Fortunately they only fucked up their own useless bugs-added-by-RIIC++ fork of musl (Fuchsia) that they seem to have eventually abandoned (like Google does with everything). They never had any access to upstream.
-
@whitequark @khm @ariadne I didn't follow it much but I think we're probably talking about different parts. It looks like there was a kernel/OS too, but the part I was familiar with them making a mess of was the libc that was a fork of musl but with gratuitous rewrites of parts in Google-style C++ apparently without an understanding of what things needed to be allocation-free, AS-safe, etc. It's been a long time so I might be misemembering exactly what was bad.
-
@whitequark @khm @ariadne I didn't follow it much but I think we're probably talking about different parts. It looks like there was a kernel/OS too, but the part I was familiar with them making a mess of was the libc that was a fork of musl but with gratuitous rewrites of parts in Google-style C++ apparently without an understanding of what things needed to be allocation-free, AS-safe, etc. It's been a long time so I might be misemembering exactly what was bad.
-
M meph@social.treehouse.systems shared this topic
