this post was submitted on 05 Aug 2024
23 points (100.0% liked)

TechTakes

1493 readers
143 users here now

Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.

This is not debate club. Unless it’s amusing debate.

For actually-good tech, you want our NotAwfulTech community

founded 2 years ago
MODERATORS
 

Need to let loose a primal scream without collecting footnotes first? Have a sneer percolating in your system but not enough time/energy to make a whole post about it? Go forth and be mid: Welcome to the Stubsack, your first port of call for learning fresh Awful you’ll near-instantly regret.

Any awful.systems sub may be subsneered in this subthread, techtakes or no.

If your sneer seems higher quality than you thought, feel free to cut’n’paste it into its own post — there’s no quota for posting and the bar really isn’t that high.

The post Xitter web has spawned soo many “esoteric” right wing freaks, but there’s no appropriate sneer-space for them. I’m talking redscare-ish, reality challenged “culture critics” who write about everything but understand nothing. I’m talking about reply-guys who make the same 6 tweets about the same 3 subjects. They’re inescapable at this point, yet I don’t see them mocked (as much as they should be)

Like, there was one dude a while back who insisted that women couldn’t be surgeons because they didn’t believe in the moon or in stars? I think each and every one of these guys is uniquely fucked up and if I can’t escape them, I would love to sneer at them.

(page 4) 50 comments
sorted by: hot top controversial new old
[–] [email protected] 5 points 4 months ago* (last edited 4 months ago) (12 children)

Summary of the recent crowdstrike report: 🧵https://infosec.exchange/@munin/112916974811882522

Munin wonders if the weird writing style of the report might be because crowdstrike used an LLM to generate a summary of several source documents, which would be funny-yet-depressing if true.

The actual causes of the incident probably won’t suprise anyone… “didn’t bounds-check, didn’t test parser on bad data, didn’t stage rollouts” in order of should-have-done-this-first-ness.

load more comments (12 replies)
[–] [email protected] 2 points 4 months ago
load more comments
view more: ‹ prev next ›