A 🧵: This morning, I was in a @lyft when a car accelerated and made an aggressive last second lane change, cutting off my driver. My driver had to slam on the brakes and honked his horn. By the next light, it was obvious the dangerous driver was an off duty NYPD officer 1/
I know this because he changed lanes again and held back in his lane so he could be parallel to our car. The driver was an officer in uniform who was yelling and wildly gesticulating out the window at my driver. He was clearly pissed to say the least. 2/
My driver immediately moved his hands high on the wheel and faced forward. He wouldn't look over at the now screaming officer who looked like he might get out of the car at any second (it looked like he unbuckled his belt). Thankfully, the light changed and we drove away. 3/
As we drove away, I thought "damn, he's going to call that in, we're getting pulled over, and I'm going to miss my flight."
Ladies and gentlemen, that's white privilege talking. It wasn't until a few minutes later that I realized my driver's demeanor had completely changed. 4/
My African American driver was visibly shaken and was clearly nervous the rest of the trip.
For him, this wasn't a possibility of some off duty officer causing him a travel delay. He reacted like it was a potential life and death encounter. I'll be reflecting on this a LOT. 5/
Now I have no idea if the off duty officer cared about the color of the driver's skin. He might just have some road rage and would yell at anyone for honking at him, because how dare you not bow down to his authority! I *can* say for certain the officer drove dangerously. 6/
I'm happy everything worked out, but it was a huge glimpse into how conditioned the driver was to fearing encounters with law enforcement. It's impossible to witness something like this and not realize we have a huge problem with this in the US. /FIN
I should probably add that this isn't about some random NYPD officer driving erratically or acting like an entitled asshole. That's NOT the point.
The point is that my driver has been conditioned to fear every encounter with law enforcement. It shouldn't be that way.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Given all the science denying, I mean "vaccine debates," I wanted to come clean about something:
At the beginning of the pandemic, I told my own daughter if they developed a vaccine in less than 12 months I'd be highly skeptical and probably wouldn't take it.
I regret that. 1/
A vaccine *was* developed rapidly and after looking at the science, it was undeniably safer than risking even an asymptomatic COVID case. Before anyone says "bah, you don't know the long-term risks of the vaccine" you're 100% right. Nobody does. 2/
But I'll counter that you don't know the long term risks of (even asymptomatic) COVID. I've looked at the science on both. On the vaccine front, there's nothing but anecdotes and fear.
But on the COVID front? There's a LOT there. Brain swelling is never good. Ever. 3/
Interview advice: if your Zoom/email/whatever avatar is any derivative of the Punisher logo, you're making a horrific* first impression. Even if the hiring manager doesn't care, they know others likely will. 1/
*unless you are interviewing for a job as a vigilante
This goes for all sorts of logos/backgrounds/whatever. But know that anything depicting skulls/death/violence is especially triggering for some folks. It's not for me, but I'm always thinking "will this potentially offend a customer?" If yes, you're fighting uphill... 2/
Feel free to explain why I shouldn't care, then go start your own business and connect back with me in a few years.
But forget the business side, think about people. You aren't likely to be more considerate to customers than a hiring manager. Hiring managers know this. 3/
If @GitHub (Microsoft) truly believes copilot isn't infringing on anyone's work, I want to offer them a chance to prove it: I'll donate $50k to a charity of their choice (or @EFF if we can't agree) if they release a Copilot version trained solely on Windows kernel source. 1/
This isn't a joke. It would be amazingly helpful for device driver developers. This in turn would ostensibly benefit Windows users through fewer BSODs. Add the charity money in and there's literally NO REASON not to do it. 2/
So let's set some ground rules:
Independent verification that the newly released model is only trained on kernel source
It's the full kernel source, from all versions (leave Win2k out if you want due to that pesky Java thing)
All kernel drivers owned by MSFT are included too 3/
If you're forcing someone to print and sign a document, understand that you're hurting the underprivileged who don't own or have easy access to a printer. I'm traveling this week and HAD to print something. My friend's printer is broken. This was the cost for ONE PAGE. 1/
Now that's not hurting me a bit, but also recognize it's not the total cost. The nearest place advertising self service printing was Staples, and thankfully I have a car. I'm still out just over an hour + gas costs all in. With public transit, double that (or more). 2/
The money doesn't matter. The time does though. And while my time is more valuable (measured by hourly rate), the time impact to someone underprivileged is much higher. "Pull yourself up by your bootstraps" only works if you don't rob them of time. /3
These newly disclosed vulnerabilities in tcpip.sys are a really interesting case study in why holistic security matters. Sure you should still be patching, but are your firewalls and IPs systems properly configured? If so, these probably aren't an issue 1/ msrc-blog.microsoft.com/2021/02/09/mul…
First, let's look at CVE-2021-24094/24086. Both involve the reassembly of packet fragments. If you've never dealt with issues IP fragmentation and never had to worry about the MTU across the network path, that's okay. It was a common thing many moons ago, but not much today. 2/
In IPv4 there are lots of variations in how fragments are handled, particularly for out of order delivery. It turns out the original standards weren't very clear on this so everybody did what was easy. But as IPv6 was being built, the standard is clear: no overlaps. 3/