It’s not a link to a sponsor. It’s a YouTube info page about what it means for a video to have the “Contains sponsorship” tag.

“…except as a punishment for crime” -13th amendment

Maybe “former” slave plantation isn’t an accurate description.

Those aren’t even real people. Those “usernames” are the names of custom emojis you can use in Twitch chat. Still weird in context, but I can see how it would be even more creepy if you didn’t know that.

The cars already have decent GPUs to process the camera data for driving assistance features, so someone at the company probably just thought it would be neat to do something with that computing power when it’s not being used for driving.

It’s fine to wash them with modern dish soaps. The reason people say not to is because dish soaps used to have lye in them, which would destroy the seasoning. Just make sure you wipe the water off instead of letting it air dry or it can rust.

I agree that’s what they want you to answer, but you can’t move it to a safe location without handling it, so C necessarily entails D. Unless there’s a designated firearm handler in the ER you can call over, which to be fair, maybe there should be.

What’s actually the answer though? I would think A, D, C in that order is probably best, but I’m guessing they just want C?

This depends on what navigation software you’re using, but I have some experience editing the Waze map. The way it works on Waze is that your phone sends the server your desired start and end points, and the server responds with a list of all the intersections you need to traverse in order. (This is actually a series of road segment junctions, wherever the map editors joined two road pieces together). These intersections can contain metadata on how to announce specific turns, but generally don’t because there’s an algorithm that looks at the angle the segments meet at and automatically decides how to describe the turn. The places I’ve seen it manually overridden include intersections where two divided highways meet at an angle far enough from 90° that it gets confused about how to announce a left vs a u-turn. I’ve also seen forks in the road where the side road requires less of a turn than continuing on the main road and the algorithm gives ambiguous instructions, like “continue straight” meaning turn onto the side road.

Edit: On your point about non-visually noticeable “blips”. This is also pretty common when roads change width right at an intersection (e.g. adding turn lanes). The Waze map doesn’t include road width in its data, so editors usually draw it down the centerline of the road. If the road changes width suddenly, you have to choose between keeping the line straight-ish, or faithfully following the centerline, which can mean that if you were to zoom way in there can be weird jumps and sharp angles that get smoothed out by the visual renderer