There are specific times when this might be appropriate. For example if I am turning off at the exit after where the car is joining from, I can see they're indicating to making a move around the inner part of the roundabout which is clear, and if I proceeded I would join a queue for my exit and block them. I'll usually stop short and gesture they move in.
But otherwise it's usually safer all round to stick to the rules.
You don't know how long C has been incorrectly yielding. There may well have been enough time for them both to move onward.
Also there's nothing to say that A isn't a yet undiscovered C.
I'm from the UK so roundabouts are second nature. I've been an accidental C before. Where I had to wait for a lot of cars that had priority over me. When it finally was open for me I was zoned out. Luckily the car behind me was very polite and just used a short beep of the horn to bring me back to reality.
But seriously, it's like chicken wings, without the bones. I'd not seen them until I went to the USA years and years ago. Now I see them over here in the UK too. Couldn't say when they arrived here for sure though.
Can Linux run programs that rely on frameworks like .NET or other Windows-specific libraries?
So this one I thought I'd answer because I've done development in both NET framework and NET core and how it works is different for each (although things will usually work one way or another).
For .NET framework applications, if the program is compiled for windows (the .exe) you can usually run it with mono (you generally don't need wine, but there's some caveats that mean sometimes you should use wine). This will include programs with GUIs. If the NET framework app calls other windows programs it is best to run it via wine, you will need to install the net framework within wine, but there's a winetricks command for that. There are a few things that are generally niche things that do not work in linux net framework's mono though. By niche the one I can think of, is serial port events. Very annoyingly they all exist, so the program will run but the events will never trigger an action in the programs. Very annoying, but luckily very rare/niche stuff.
For .NET core, you can build directly to linux targets, and if the project you are working on does target NET core, then you can run the binary natively (note: you usually cannot build applications using forms to linux native binaries, for these you should run the windows exe with wine). You can also run the .exe files for this with wine and I've rarely had a problem with it.
Note that if you develop .NET applications, you won't be able to build anything that uses the standard forms GUI under linux. There are other UI frameworks out there you can use that are multi platform. For this reason, for the projects that do use windows forms, I have a VM with windows on that I boot up for this reason.
In short, if you're just running windows binaries, you will be generally fine with mono for framework and wine for core. For development "it's complicated".
The problem is, this assumes that even if the kind of AI creators that are scraping relentlessly (and there's a fair few that do) took this data source directly, that they'd then put an exception in their scrapers to avoid wikipedia's site. I doubt they would bother.
There are quite a few April Fool RFCs, but this one is definitely one of my favourites. This one and RFC 1149 (A Standard for the Transmission of IP Datagrams on Avian Carriers).
As an outsider looking in, everything this regime does is testing the waters to see if they can get away with that, and if so how much further can they push it.
If someone doesn't actually take real action to stop it soon, it may become unstoppable.
All hypothetical of course. Not convinced things will go that far without some more clear indicators.
The root servers are already spread over the globe. Enough of them are operated by non US orgs too to handle things initially, I suspect that the localised anycast servers located outside the US for those USA based operators would probably go on serving.
It'd be trivial to replace them anyway, and frankly we traffic would be much lower anyway since a lot of the Internet is run by us based organisations.
For domain registration on tlds not run by the us, they should continue to operate fine.
Well, I'd expect that if they allowed 5v through but with a low current limit (I think the default 5v standard states quite a low current allowance). They could catch anything drawing too much and shut the port off until it detects disconnection/other reset.
I mean, if they're thinking about protecting a downstream device, adding this logic would make more sense than just not supplying any power unless a negotiation is made.
In any case, since standard USB ports on a computer will output 5v without anything being negotiated, then it's really no less safe than any other USB port in that regard.
But wait. Doesn't this make them both dumb? I'd expect a modern USB-C charger to still support basic 5v low current lazy devices too. If there's a USB-A to C cable that works, it must also still be possible to send the basic 5v down a C-C cable.
I also think there's always going to be a balance between how much a device needs to make and/or how much it needs fast charging to make sense to add the charging circuit for PD/PPS. Even $1-2 on top of the cost can ruin margins in the current electronic market.
I've been to the US twice since 9/11 and neither time was I asked for my phone. Not to say it didn't happen before now. It happens in many countries if they decide they have even a tiny bit of suspicion.
But, frankly right now I would not travel to the USA for any reason.
There are specific times when this might be appropriate. For example if I am turning off at the exit after where the car is joining from, I can see they're indicating to making a move around the inner part of the roundabout which is clear, and if I proceeded I would join a queue for my exit and block them. I'll usually stop short and gesture they move in.
But otherwise it's usually safer all round to stick to the rules.