topham
It's often an echo chamber, and this will kill it, the only question is the timeframe. And no, I don't mean 20 years, I mean weeks/months.
Perl 4 specifically of course though.
Electromagnetic noise can trigger them, it could feed back from the power supply.
I don't care if the guy threatened a lawnmower, I do care if he started spouting off about killing kids.
Context matters, but that's what the evaluation is for, not you our I deciding that a rant with potential violence towards children is just a rant at an LLM, or a premeditated act in advance of a violent crime.
I don't know. Do you know for sure? What happens if you're wrong?
Seems there's a line and this is well past any reasonable line.
/sarcasm
I watched a significant portion of that video, it represents what I expect well. You can't bury your head in the sand because an AI reported a bug, it's, potentially, still an exploitable bug. They can however raise the standard. They can require that reporting a bug comes with a fix, even if they reject the fix provided, it gives them an opportunity to evaluate that the bug is real, that someone put some effort in resolving it for the community (even if an LLM provided the fix); it gives something to evaluate the can benefit rather than only being a determent to the community.
I've sent a half dozen patches over the year to projects, I've always provided my perceived fix for the issue, occasionally they've been implemented as-is, and sometimes they were replaced outright with an alternate solution. I never really cared about the solution, just that the issues was resolved.
The first was a commercial library that dealt with multiple modems (interrupts and daughter cards)on dos based machines. They took the fix and integrated it and provided me with an updated library. Not much of a thank you, but the library was fixed.
More recent ones was another commercial library, open source but proprietary, and they sat on it for 3 months waiting for me to fix it their way, before the accepted it as-is and released appropriately adjusted patch. (I'm not their employer or employee, their complaints were tedious undefined rules. I fixed the bug and had working code. I waited them out.)
Good responses, bad responses, none of them mattered, what did matter to me, and others, is the developers involved cared enough to eventually implement the right fix for their codebase. The bugs need to go. Set the ego aside and fix it.
Honestly, seeing people go from concern trolling to what I like to call _concern farming_ has been utterly disappointing.
_concern farming_ is when people build entire crops of concerns with no intent to do anything other than fertilize them.
Yes -then no, you cannot trust it won't make that decision.
Couldn't happen sooner.
Air temperature is only one contributing factor for comfort in a home. Surface temperatures take longer to achieve and the larger the gradient the longer it can take.
There are multiple factors to take into account, including the highest temperature the home gets to, that is dependant on location and weather patterns.
If you keep the temperature in the home to 28-30 degrees then later cooling to lower temperatures before bed time you can reduce costs and energy expenditures than if you let it rise to 34 degrees or more and only lowering it when you get home. Or, what you save in costs you expend in otherwise like poor sleep.
Lowering it advance, on a schedule makes more sense if you want surface temperatures to also be reduced.
The blanket disabling of air conditioning when not home is not the only solution, and often is sub-optimal.
That's often substantially more inefficient than keeping it at the temperature desired, or adjusting the desired temperature to mitigate it somewhat.
Commercial plugins are a thing, next.
I've had an AI reproduce astronomical formula functions without difficulty in whatever programming language I want. Graphical algorithms aren't even a challenge.
Might be time to reconsider the business model entirely, because Pandora's box is already opened.