It is, but the results are often AI generated junk, maxing out the SEO rules. For example, If I ask how do I trim a tree (I didn't check it, just an example), there can be several of the top results that are AI copies, for lack of a better word. Maybe that points to an issue with AI; it creates its own validity based on a consensus of responses. One could easily become a bogus authority by spending very little money buying junk domain names and reposting the same content several times. I'd almost bet if I created a bunch of sites, or more so pages in my existing domains maybe, stating that asteroid QX95-217 may hit the earth in six months, the search engines AI could create credibility. Especially so if the AI "farmers" post more sites with the same information. Sure, it was doable before AI, but it wasn't so easy and there really wasn't a way to create validity based on consensus.

It's fairly typical for cities in Florida platted in the 60's to 70's. A lot of the lots were bought site unseen by 'northerners'. In contrast, coming to SWFL from front range Colorado prairie, our 12k lot here can turn into a mini-jungle in 6 months :)

Hey Dave, You're a lifesaver :) VS had self-added (???) these to the main form: Imports MS.Internal Imports System.Windows.Forms.VisualStyles.VisualStyleElement Libraries in this haven't changed in two years, so I never thought to give this a look. Those two were responsible for all the errors. Where they came from? My only guess is that on Saturday, that computer was in 'update hell'; meaning it had downloaded an update but needed a reboot and I didn't notice it. For unrelated reasons, it runs 24/7. It took three times to get the update flag cleared, and I'm pretty sure I opened the project after the first update said it was done. I should have known better, since I know VS doesn't use the in-memory loaded libraries in update hell, but was doing a few different things on different computers so I missed it. Though in the past, I've never seen it add libraries on its own; it normally throws "missing" errors. Thanks again for the clue. Mike

Thanks for the head's up on the toner cartridges.

It wasn't Okta that was hacked. It was GitHub.