Notices by Todd Knarr (tknarr@mstdn.social)

@aral This is breaking down, though. The last decade I've noticed developers are less and less interested in understanding their code and working on it. They want to just get something that passes tests and move on to the next thing, and if it breaks in production they'll put that in the queue to fix.

@glynmoody Now aim them at C&C elements instead of front-line soldiers.

@dalias @bedast The servers involved belong to Tesla and are part of the sysadmins' responsibilities. This is something too many people fail to grok.

And in too many cases the sysadmins aren't just allowed to look, they're legally required to look and to act on what they find.

@bedast It goes back a lot further. Rule #1 as far back as the age of mainframes is that the sysadmins can see *everything* you do. That's pretty much their job. It's just that, for the most part, we didn't care that much. Your porn was, frankly, nothing we hadn't seen dozens of times before and as long as you weren't interfering with normal operations we had more important things to do with our time.

@glynmoody I'm not sure they have the physics of that right. It's pressure differential that drives the flow, and it sounds like they're handwaving away the pressure from the water column in the output line. They may be depending on the siphon effect, but I'd want some independent analysis of the math behind this. If just running a vertical pipe to that depth doesn't result in flow out the top of the pipe, I can't see how this is going to work the way they say it does.

@glynmoody And if he can't do it, he'll claim he can and do it anyway.

@hrefna I understand the term quite well. When I dealt with it, "collateral damage" meant "block all email from entire ISPs and all their customers". And I was fine with that, because measures that didn't go that far had been tried repeatedly for years and weren't working. Email spam was still a massive problem even with individual anti-spam measures in place. So, massive collateral damage it was. And you know what? It worked. ISPs started to clean up their acts.

@hrefna And yes, we were called unreasonable then too, for many of the same reasons. We noticed patterns in the people who called us unreasonable, too.

@hrefna Yes there's collateral damage. That's the point, and I want it to happen. I'm using that list because their being a transphobe is enough of a hard nope for me that I don't want to interact with them on any other subject either except under exceptional circumstances.

@hrefna As someone who'd use such a list, I'd disagree. JKR is a canonical example of who I'd expect such a list to block. If the list doesn't block her, what other well-known transphobes will it also not block? If I want transphobes automatically blocked, having the most obvious ones not blocked limits it's utility to me.

@glynmoody I'd love to see that. Maybe they can solve the unit-price problem with it?

@glynmoody Methinks they're too optimistic and will find most of the time-consumers on the tail end are intractable: determining print run size, printing, binding and distribution.

Watching the news about the protests of the war in #Gaza reminds me strongly of the protests of the Viet Nam War.