But it still has to be Jimbo and Ned defending the town.
But it still has to be Jimbo and Ned defending the town.
Oh wow, I wonder what the next excuse the greens will give me when I point out that they’re a joke spoiler party, now that we have evidence that they’re a joke spoiler party.
Agreed, but that’s hasn’t stopped people before…
Bots can view content without being able to post, which is what people are aiming to cut down. I don’t super care if bots are vacuuming up my shitposts (even my shit posts), but I don’t particularly want to be in a community that’s overrun with bots posting.
Usually by tying your real world identity to your screen name, with your ID or mail or something.
26% of advertisers are begging PG to sue them.
It’s very unlikely, given the lack of evidence, and the immense technological base requires to make it across the distances required to get to other systems. The physics of the universe as we understand them alone is a massive mark against the possibility.
LLMs likely have no good role to play in education and I wouldn’t be surprised if banning them outright in what may become a harshly fought battle isn’t too far away.
While I agree that LLMs have no place in education, you’re not going to be able to do more than just ban them in class unfortunately. Students will be able to use them at home, and the alleged “LLM detection” applications are no better than throwing a dart at the wall. You may catch a couple students, but you’re going to falsely accuse many more. The only surefire way to catch them is them being stupid and not bothering to edit what they turn in.
They always break rule 1: never get high on your own supplies.
Hey, Steve and Drake are some of the bosses favorite tools!
Don’t pay by credit card.
This is bad advice for anyone with good credit and spending habits. A credit card with rewards is just free money if you’re responsible with it. I haven’t paid interest in over a decade and have made thousands from rewards.
Microsoft gave CrowdStrike unfettered access to push an update that can BSOD every Windows machine without a bypass or failsafe in place. That turned out to be a bad idea.
They have to give that access by EU ruling:
Microsoft software licensing expert Rich Gibbons said: “Microsoft has received some criticism for the fact that a third party was able to affect Windows at such a deep technical level. It’s interesting that Microsoft has pointed out the fact this stems from a 2009 EU anti-competition ruling that means Microsoft must give other security companies the same access to the Windows kernel as they have themselves.”
It’s not really criticism, it’s competitors claiming they will never fuck up.
Not in all cases [podcast warning], sometimes it’s just them pointing out they’re doing silly things like how they test every update and don’t let it out the door with <98% positive returns or having actual deployment rings instead of of yeeting an update to millions systems in less than an hour.
It’s reasonable to criticize CrowdStrike. They fucked up huge. The incident was a fuckup, and creating an environment where one incident could cause total widespread failure was a systemic fuckup. And it’s not even their first fuckup, just the most impactful and public.
Clownstrike deserves every bit of shit they’re getting, and it amazes me that people are buying the bullshit they’re selling. They had no real testing or quality control in place, because if that update had touched test windows boxes it would have tipped them over and they’d have actually known about it ahead of time. Fucking up is fine, we all do it. But when your core practices are that slap dash, bitching about criticism just brings more attention to how badly your processes are designed.
But also Microsoft fucked up.
How did Microsoft fuck up? Giving a security vender kernel access? Like they’re obligated to from previous lawsuits?
And the clients, those who put all of their trust into Microsoft and CrowdStrike without regard to testing, backups, or redundancy, they fucked up, too
Customers can’t test clownstrike updates ahead of time or in a nonprod environment, because clownstrike knows best lol.
Redundancy is not relevant here because what company is going to use different IDR products for primary and secondary tech stacks?
Backups are also not relevant (mostly) because it’s quicker to remediate the problem than restore from backup (unless you had super regular DR snaps and enough resolution to roll back from before the problem.
IMO, clownstrike is the issue, and customers have only the slightest blame for using clownstrike and for not spending extra money on a second IDR on redundant stacks.
HA!