There are significant drawbacks with that: Many applications offer different paste actions via menu entries and/or different shortcuts, and sometimes via macros. (I use such non-default pasting all the time.) So there would have to be a mechanism to manage the ways an application is allowed to perform pasting, and to have the user selectively permit or forbid the various ways.
Additionally, the clipboard is often used to copy items within the same application, a mechanism which again can be involved in a multitude of application commands; or else the user must be burdened with having to distinguish between an application-level and the system-level clipboard. This can be partially solved by always allowing pasting of content copied from the same OS process, but multi-process applications would still face hurdles.
Another variation of that is scripting. I have various scripts and CLI aliases that take the current clipboard contents and do something with it.
While the clipboard can be made more secure than it traditionally is, these security measures come with the usual trade-off of making things more annoying for the user.
You have entirely misunderstood/misread the comment.
streetfighter64 said “ event initiated by the user.”
Copy/paste can be initiated multiple ways, including through many entries. That does not matter. What matters is , the application has zero knowledge on what is on the clipboard. It can’t read/modify/delete. It can only allow the user to trigger an action, and the result of that action is transparent to the user.
It would be the US taking a 25% cut in the form of tariffs:
“Under the scheme, Nvidia chips manufactured in Taiwan could be sold to Chinese companies if they were first imported into the United States for a security review, which would require payment of a 25% tariff under Section 232 of the Trade Expansion Act of 1962, a trade law designed to address imports that threaten national security. Then the Commerce Department would grant Nvidia an export license to sell the chips to Chinese companies.”
The way it works is that it is a completely made up reason just to require the chips to cross the US border so the administration can use this as a bullshit reason they don't have to follow the constitution.
Being a billionaire is a choice to continue to hoard resources that could be put to useful purposes instead. Yeah, I don't have much sympathy for people who choose to squander our society's resources like that.
Does a billionaire who became billionair by marrying a person who became a billionaire also bears the responsibility of hoarding because they choose to marry that person and not divorce early?
No, not morally. If she divorces, she should also be subject to that proposed the wealth tax, which she won't mind because according to your frame she didn't choose to hoard.
Tangentially related, the only way for a Java properties file to be invalid is if it contains an invalid Unicode escape sequence (“\u” not followed by four digits, and not preceded by an odd number of “\”). After resolving Unicode escapes, any character sequence is a valid properties file.
I've had a program where some R code stuffs some input in an URL, fires it at a server, then reads the returned CSV. No error handling or validation is attempted.
As it happens, basically anything is a valid CSV.
If the input is wrong, the server responds with an XML error. This got interpreted as a CSV. Every line became a record, but no column headers were found so every expected field is null/NA. All these nulls get nicely sorted and processed, which causes more string errors, etc ... Mayhem ensues when thst stuff ends up in a database.
Can't agree more. I've dealt with a CSV where multiple CSVs were cat'ted together, but the originals were not in the same dialect and differed even in charset encoding. Wrote a statistics based parser that decided which part of the file had to be decoded which way. Interesting technical challenge, but my god the reasons for its existence were dumb.
Falsehoods programmers believe about CSV: "Yeah, sure it's a mess and there are like, a gazillion different dialects of it, but at least once you know the dialect of a file, you can decode it"...
My god. I love CSVs because the lack of any standardization makes them incredibly flexible, but combining CSVs is just a wild idea. What was that person thinking?
Nobody was thinking anything. A bunch of managers of a group of frenemy corporations was condemned by the governement to share date. Every company sent the data to a trusted third party. This party removed the source company, anonymangled things a bit, taped them all together, and sent the result back to everyone. Managers wanted CSV as it was easy to open in excel, and they were going to let their underlings process them manually. Then it turned out to be a few 10s of millions of records and excel couldn't yet deal with >64k rows, so IT got to deal with it.
People keep bringing up Zitron because they are wishful-thinking that he’ll eventually be right. But yeah, it seems that he’s been plenty wrong so far.
Additionally, the clipboard is often used to copy items within the same application, a mechanism which again can be involved in a multitude of application commands; or else the user must be burdened with having to distinguish between an application-level and the system-level clipboard. This can be partially solved by always allowing pasting of content copied from the same OS process, but multi-process applications would still face hurdles.
Another variation of that is scripting. I have various scripts and CLI aliases that take the current clipboard contents and do something with it.
While the clipboard can be made more secure than it traditionally is, these security measures come with the usual trade-off of making things more annoying for the user.
reply