Note that the locking connector OWC uses is a standard, not the standard. This is USB we're dealing with, so they made it messy: the spec defines two different mutually-incompatible locking mechanisms.
A few days ago I was trying to see if a anything new had taken over a vacant restaurant space yet, previous occupant had closed in July.
When I zoomed in, it would still only show me the Permanently Closed business listing for the old restaurant.
Searching by address, they do have a listing for its replacement. But they were prioritizing the dead restaurant on the map because why would I want to know current info from a map when they can be useless instead?
And it's not like this is a restaurant in the first floor of a tower with a bunch of businesses stacked on top of it competing for map space. It's a single floor, there's only one occupant.
The App Store is the walled garden that doesn't allow anyone else to ship a browser engine, except in certain markets where they have been forced by law to create a "Web Browser Engine Entitlement" that non-WebKit browsers can use with super special permission from Apple.
My favorite is when it bounces back and forth between the same two wrong answers, each time admitting that the most recent answer is wrong and going back to the previous wrong answer.
Doesn't matter if you tell it "that's not correct and neither is ____ so don't try that instead," it likes those two answers and it's going to keep using them.
The false info baked into its context at that point in the conversation and it will get stuck in a local minima trying to generate a response to the given context.
reply