They could have easily implemented autosave and versioning on your local machine. They chose to gate it behind keeping your documents in the cloud for profit-motivated reasons.
Plot twist: OP would not stop talking throughout the show and them ruining the finale was the last straw.
What the hell does this say
This was actually a decent skim. Microsoft did not think that one through.
Companies paying for a corporate copilot instance to train on their SharePoint documents can inadvertently reveal the contents of those documents to anyone in the company who asks Copilot about them, even if those documents were made highly restricted - in their example, a document full of service account passwords permissioned to only be accessible by a select few members of IT (although sensible IT would be using a password manager right?)
Quite the oversight! That's sure to slow adoption in any shops with a zero-trust or principle of least pivilege model in place, or even anywhere big that segments their teams to cut down on noise.
It's always satisfying when someone I have tagged later confirms that tag.
It would be cool if this evolved into some sort of decentralized internet archive.
The trick is not to read the usernames. I imagine myself surrounded by millions of mostly sensible people!
No Egress
A good decompiler and an auto-formatter might leave them with a nicer copy of their source code than they had in the first place.
"brown" has left the chat?
I appreciate you exploring your sense of humour, but let's stop using gay as an insult.
Big C#14 addition I've been wanting since they added extension methods. I think this finally lets us create stateful mixins, and solve some niche use-cases where multiple-inheritance would really be preferable over composition.