It also can be prompted to read the contents of a webpage, I have used it to help me craft a regex expression for removing junk utilizing invoke-webrequest to parse out CPU models compatible with 22H2 upgrades from Microsoft(that page did not exist in 2021).
No, I do not mean that. I provided it the URL and then asked it to use the contents of the CPU table from the invoke-request to strip away everything after the X and it not only did it, it even provided the example output of the array it modified.
Certainly! Here's the updated $compatibleCPUs array based on the list of supported Intel processors for Windows 11 version 21H2 from Microsoft's documentation:
Interesting, and certainly convincing. I have a paid account, I wonder if this makes any difference? It would make sense to me that it is basing it's 'reality' off of the prevous 21h1 page(which would have existed) and it understands the goal I am trying to achieve.
It's not accessing that page live (or recently cached). That's not part of how it works. It's possible the model was updated and has learned from that, but it's also very possible it's just made up the answer. The old model cutoff was 2021 I think, I don't know if/what newer training has been done.
Even Bing can't make outbound HTTP requests - it can only access cached snapshots of pages held in the Bing search index. I confirmed this on Twitter with one of the Bing execs: https://twitter.com/mparakhin/status/1628646262890237952
Cool, I really hope they open this up. It feels like being able to restrict it to either a subset of public pages or private data would immediately be extremely useful and only a small conceptual change from what's there.
I just built this locally over our RFCs and it's good but a properly integrated thing would be fantastic.