Why are they plowing money into this garbage? I don't understand it. I guess it is because Google is lagging behind in the AI race but the roi of this bs must be close to zero. Clowns.
Yeah, I’m really mixed on this story. Why are they so insistent on not just blocking the sites? I don’t even really think a slippery slope is at play here. This is a very specific legal circumstance that doesn’t seem to have any chance of expanding to other forms of censorship.
Quad9 already states that they strongly oppose piracy, so just block the sites. The piracy sites will be fine.
I don’t think DNS is as neutral as Quad9 believes it is. DNS is like the sign for a business on the road and the domain registrar is like the building permit you get to build the sign. DNS is a way to find a website or business without even bothering with a search engine. Try typing in stamps.com, office.com, booking.com, weather.com.
The thing is that in most parts of EU any muppet can go about and find anything between fairies to wood peckers to stop deforestation. So if you own the land act first ask later is the correct way.
I am not claiming that it is right. Hardly Google that came up with this plot. Local people knowing how stuff actually works advised on this as it is not that uncommon.
Log4shell did not get that bad because it was only the less used version 2 that was effected.
The standard way hackers go about today is data theft and extortion. I think we would have heard about it if was a big problem.
People should off cause keep their servers up to date no matter what. The total panic that was yesterday with people posting all kinds of random AI slop was pathetic.
One of the few corps I applied for a job at that did not even reply. Also known for being a bit of a crappy employer as well even long before EA bought them. Many other studios was also out of line back then to be fair.
People should stop reading AI slop on X and other social media. The exploit is advanced and took some effort to fix. If there really was an open RCE in PHP for anyone to use the impact would be massive.
We don't know yet. Not sure how that changes things either way. Impact goes far beyond getting exploited and the leak wasn't ideal in that regard either.
State hackers and others prepare how to use exploits long before they happen. If there was an opened known RCE in PHP they would have caused havoc immediately. Clearly that did not happen.
The cyber filter blocks really basic stuff all the time. People who are pro that bs should be forced to only eat with a spoon for the rest of their life.
For me it refused to move Claude transcripts from point A to point B on my local machine. It kept getting flagged as reasoning extraction or something. The line of "It's my machine, I can move files wherever I want" shouldn't be crossed. Someday file managers are going to go extinct and LLMs will organize everything, and they shouldn't choose what files you can and can't access on your own computer.
I think a code review should be just that. A review of the optics of code itself not the solution or anything like that. If that is important it should be done earlier in the process before coding. Even more important when coding with AI. The reviewer is not a tester. I've heard horrible stories from friends who mainly works with fixing AI generated code that junior devs pushes at a rapid pace.
reply