|
|
|
How about a separate option flag to allow/disallow these type devices unless in the group or owner at both parcel and region level?
I.e.; can drop a box to open it for a minute but not if that box has URLS. I.e.; the entire primitive that supports http be a separate primitive type that can be selectively allowed, by individual, group, parcel, and region level permissions. I don't want anyone but me dropping URLs in my region ever. Not ever. Not after reading how it will certainly be abused. It is bad enough they come in wearing stuff that communicates with the outside world to scan and catalog the sim contents without permission. LL needs to be thinking about how selfish people think when considering new features and implement ways to prevent bad behavior before it is released. Banning after it happens? it will keep happening over and over, and you know it will, until the gray goo fence style coding is in place so may as well code it in from the outset. Ann I think you got the wrong impression of what the URLs are. They are simply URLs that provide access to the prim's script data from the outside world (the internet). A sample URL would be: http://sim123.agni/cap/f23b4b94-012d-44f2-bd0c-16c328321221
This URL is only provided to the script. and then the script can send it to whatever service needs to know and gain access to the prim. What people have a concern about are people using a script to allocate all the URLs and somehow prevent them from using services that would need those URLs to function. Using no build or autoreturn is a simple and effective way to preven this. However to be more proactive, it would be good for a paracel owner to see that, say, the cube a visitor rezzed is using 75 URLs for no good reason, and then they could return it. Or at the very least, ask them why they need 75 URLs, assuming it was even blocking their service. I expect most portable applications will use the 38 personal URLS anyway, which does not affect the parcel limit. It certainly couldn't be used to advertise a store. The evolution of the new functionality is described more in
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I agree with providing any tool we can to help owners identify sources of lag on their land.