Comment The EU probably won't like that. (Score 1) 78
They'll likely haul them in for deceptive practices...
> At the very least, they could have continued to accept cash transactions.
Nobody uses cash in Denmark. It's all MobilePay, Apple Pay, plastic or apps. It's been years sine I last saw cash.
Trying to partition which bits of the internet are the organisation or partners to the organisation sounds like a nightmare since most things are hosted within three main outsourcing organisations.
It's the browser or mail client that taints the file with it's "Internet origin" mark. Download a file using a browser or save a file received through an email and it will be tainted, unless you use some obscure mailclient or browser which does not follow the guidance.
Why do I have a hunch that "trusted location" means "some server on the internet with a valid certificate" or similar bullshit that won't keep a single infection from happening but causes heaps of headaches for legitimate users?
The "from Internet" taint of files in Windows rely on the user agent. Mail clients and browsers are expected to "taint" files downloaded using the application. All browsers respect this, and I believe that all mail clients do so as well. But it really comes down to the program you use to download the file.
This ability to "taint" a file has been in Windows since Vista (at least).
Oh, you can still "automate". This takes away the ability to run macros for *files from Internet*. It does not take away the ability to run macros in documents you have authored yourself or retrieved from within your organization.
And you can still use them. This change is about *files from Internet* or other untrusted locations, such as a file share accessed through an IP address.
For files retrieved from *trusted locations* this will not have any effect. Macros will still be able to run.
What struck me about Blazor is how *simple* it really is. MS had a pre-existing template engine Razor, and Blazor is almost just the shadow-DOM layer on top. It compares the current rendering to the shadow DOM and updates the DOM with the changes (Blazor Webassembly), or ships the diff to the client (Blazor Server).
They added some support for state (like cascading properties, event binding and expression binding) and that almost it!
To make it work they had to compile the
I can attest that it works beautifully. Being able to share the DOM classes (and even the service signatures) between BFF API and the client eliminates the friction between serializing to JSON from one language (e.g. C#) and deserializing from another language (e.g. Javascript/Typescript). No more date/time string mangling where time zones are off
Why would that matter with regards to football fields? You should ask font size instead.
... and also specify if we are talking about an American football field or what the rest of the world calls a football field.
Donald, don't you have your own social media platform?
Having to confirm running the macros every time would be a nuisance in those situations.
Eh? The current state is that you *will* be prompted before execution of macros from any document downloaded from Internet or received through a mail program. That's how it works now.
You need to unblock (remove the "from Internet" taint) the document before you can run macros. Until then, a document with the "internet taint" is also opened in a sandboxed version of the application (low integrity mode strips away writing permissions to the file system and more).
This change is that you will not be *prompted*. The macros will silently be blocked. No prompt. Which is better, because social engineering techniques can be deployed to make the target *want* to unblock the document.
So more meltwater in the rivers. Indian farmers will be able to grow more crops maybe even crawl out of poverty? No we cant have that
Great idea! They just need to find a suitable gorge, build a dam and store that glacier meltwater before it goes to waste. But I bet they are too lazy for that, and that all the meltwater will have spilled into the sea before they decide to build a dam. Well, then at least it's not our problem. They had their chance. It's their glaciers and if they let them melt without using the water, shame on them.
More information:
It appears that you have indeed run into a current issue: https://github.com/PowerShell/...
If you want to auto-complete parameters, then type a dash *before* hitting ctrl+space. That way the powershell host will know that you are only interested in parameter names.
I don't know what type of host process you are running powershell in. It seems that it may have to little buffer space for displaying a large completion list. It works fine in Windows Terminal, ISE or VSCode.
Which sounds great until you try it, and find yourself always writing a novel in PS to replicate what would be a haiku in bash.
Want to provide an example?
Real Programmers don't eat quiche. They eat Twinkies and Szechwan food.
