My pc, maybe because of the external keyboard I'm using, occasionally decides that Scroll Lock is On and then Excel becomes unusable ... The solution is to bring up the On Screen Keyboard and toggle the virtual scroll lock key ...
I wonder how that happens? Do you press Ctrl-Home a lot (to go to the very start of a document), and maybe you missed and hit Fn-Home, if you have a Dell OEM keyboard https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2F... , Fn-Home toggles Scroll Lock...
> gws doesn't ship a static list of commands. It reads Google's own Discovery Service at runtime and builds its entire command surface dynamically
You're not exactly describing rocket science. This is basically how websites work, there's never been anything stopping anyone from doing dynamic UI in TUIs except the fact that TUI frameworks were dog poop until a few years ago (and there was no Windows Terminal, so no Windows support). Try doing that in ncurses instead of Rataui or whatever, it's horrendous
But on most of them the power setting just changes the percentage of time the magentrotron is 'on', but while it is on, its full power. So something like 'low for 40s' becomes a game of russian roulette
This is fascinating because I remember this era when Microwave ovens were a new thing and my parents got one, along with a glossy cookbook with a roast chicken on the front. All of that 'roasting things in the microwave' gor quietly forgotten about in the late 80s, along with the idea that CDs were 'indestructible'.
But somehow modern microwaves always have a button on the front with a picture of a roast chicken. Why are microwave UIs so delusional? Just need power %age and time.
Microwaves are good for making porridge (oatmeal) though. And I've had some success with scrambled eggs, if you get the method right results are very consistent.
I'd like to think that they should have reasonable security with my best interests in mind, but I really have no way of investigating what the baseband is or is not doing.
The central paragraph of this is still really hard to parse:
"At its core, OAuth for delegation is a standard way to do the following:
The first half exists to send, with consent, a multi-use secret to a known delegate.
The other half of OAuth details how the delegate can use that secret to make subsequent requests on behalf of the person that gave the consent"
This paragraph has a bunch of words that need defining (the word delegate does not appear on the page until then) and a confusing use of 'first half', 'second half' .... First half of what?
The sentence is correct and accurately describes OAuth.
Delegate is just a standard word, look it up on a dictionary. If anything its internal technical definition is precisely in that sentence.
>"First half of what"
The spec, the standard, half of it deals with X, the other half of it deals with Y. Namely one half being how user grants permission to a third party, and the other half being how the third party makes requests to the main data holder.
If you need another definition: OAuth is a three way protocol between users, a service provider, and a third party. A user gives specific permissions to the third party, so that the service provider can share specific resources with the third party, who acts on the user's behalf.
Op didn't say that it's incorrect. I read the article myself as well and wasn't much smarter than before. For better or worse, llms did a much better job explaining it on a high level and then giving technical details if I still wanted to know more.
Reads to me like it is not accessing other users mailboxes, its just accessing the current user's mailbox (like its meant to) but its supposed to ignore current user's emails that have a 'confidential' flag and that bit had a bug
I think that Microsoft would rather not acknowledge that one. It's much easier to hide behind a simple "bug" than to admit to such a massive security breach.
Because hype makes money.