I am somewhat less disappointed, because resistance is *hard*, especially when you're not prepared.

Dan Sugalski

I am somewhat less disappointed, because resistance is *hard*, especially when you're not prepared. This is why you *should* be prepared in advance, rather than having to try and work out your limits and means of resistance on the fly.

Think ahead. Consider your likely situations and your options now, when you're not directly under stress.

Scott Francis (@[email protected])

incredibly disappointed in the folks who have the technical skills to be sand in the gears here, and instead are collaborating. https://infosec.exchange/@josephcox/113941826255934073

Infosec Exchange (infosec.exchange)

Random Geek

@wordshaper not to mention the fact that a non-zero proportion of people behind those Git commits have been planning on how they'd collaborate.

which you know – F them.

Dan Sugalski

@randomgeek oh, yeah, collaborators can fuck off into the sun. Still, though, a lot of people will freeze when pushed for bad but not too horrible thing and start going, and once you start you tend to follow through. Those are the people (including possibly me, which is why I have thought about this kind of thing already) who need to plan in advance.

Random Geek

@wordshaper yep, same. It's inescapable, but one delaying tactic I've used is trying not work where I know I'm gonna have bad problems.

which has not worked in my favor on moving to an area where the primary tech employers are defense contractors