Automatic container privileges and new option

The new privilege is No Open ... effectively converting the container into a "Black Box".

The suggestion is this any container (ie object that in any sense contains others) should have privileges that are set with respect to its contents. That is to say Containers (without the proposed "No Open" property) would have their properties set by those of their contents. So if a container contains no "No Copy" items it itself would not be "No Copy" ... if it did contain a single "No Copy" item the container itself would be "No Copy". This makes sense for "No Copy" and "No Transfer" ... I'm not sure about "No Modify". Of course none of this would apply to "No Open" containers.

I've come across several "No Copy" containers where all of the items are copyable. Since you can create a new folder (or whatever) and copy the contents to it you may as well be able to copy the original container since you can effectively achieve that anyway.

What's the use of a box I can't look into?

What's the use? If the box took inut from you in some form, processed it and prduced output you could use you may not need to see the contents. Additionally it would mean that the contents are less likely to be accidently damaged. I know a container that is damaged simply by accidently opening it. This would prevent that.

So, it's some kind of black hole into which I can throw stuff and out of which an unseen script can give me things?

And if a box is ruined by r-click -> opening it, then the script is buggy and should be fixed.