Quote:
Originally Posted by Gigs Well, I'm not proposing that. I'm saying we should keep the permissions that work, and get rid of the ones that don't.
It's critically important to continue enforcing the "mod" flag on prims, at least in the short run, not to prevent their parameters from being modified, but to prevent insertion of spy scripts that can snoop link messages. That could be broken out into a better named flag like "Modify object inventory", though. In the open grid scenario, this flag goes away too though. People who run stuff like web services need a lot of notice before changing this behavior though.
Likewise, script mod/transfer is enforceable for now, and can remain so in the short run. In an open grid scenario, script transfer is meaningless, but script mod is meaningful. The source code to scripts can be secured, however the compiled CIL bytecode must be shared with people that run grids (i.e. everyone). This creates a lot of challenges when hard coded passwords are in scripts, as those will carry through to the CIL.
Anyway, if all the broken permissions were removed, but all the effective ones were kept, I'd say the net effect on the SL economy would be near zero. People that sell textures already do so full perm. The same is true with many people that sell pure assets. |
The copy permission is not broken.
It is, moreover, illegal to go around it.
What you mean is, there is a way (and a limited, time-consuming way, is my understanding) to copy something that is marked no-copy.
"Imperfect" is different from "broken."
"Broken" would imply it doesn't work at all; not imply that it can't be circumvented by illegal hacks.
coco