
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Relates
|
|
|
|
This issue is related to by:
|
|
|
VWR-241 Can no longer sit through walls, or reliably on any object without a sit target.
|
|
|
|
 |
|
VWR-2525 More Privacy for Your Home (Anti to Identity Verification Policy)
|
|
|
|
 |
|
|
|
 |
|
SVC-4728 Instanced Parcels - Replacedment for "Ban Line" handling of parcel access
|
|
|
|
 |
|
SVC-2390 Enable an alternate access controlled "skybox zone" at 3328-4096 meters
|
|
|
|
 |
|
SVC-263 Offset terrain height from sim ocean level
|
|
|
|
 |
|
|
|
|
|
SVC-241 Meta-issue: Improved In-world Privacy
|
|
|
|
|
|
|
A landowner can request the creation of a "basement" zone for a parcel. The "basement" zone would be in the boundaries of the parcel, but isolated from anything else in the sim. The proposed implementation is a region between -1024 to -768 meters altitude, limited to the borders of the parcel, sharing the parcel's prim quota. Objects in this zone would not interact with anything outside the zone: the zone border would be a solid wall (like the edge of the void), agents in the zone would not receive any object data or chat from outside the parcel boundary, and so on.
- For physical objects, each zone would be a separate collision group.
- Non-physical objects would be blocked at the wall. Physical objects would bounce off it.
- Object data in the zone would only be transmitted to clients inside that zone.
- Chat in the zone would only be transmitted to listeners inside the parcel.
- LSL script calls like llGetPos() would return <x,y,z+1024>
- llgetRegionCorner() would return <region_x,region_y,-1024>.
Access to the zone should be through a script call "llZoneTransfer(key agent,vector position,integer zone)". If the zone value is TRUE, the agent would be transported to that location in the zone. If the zone value is FALSE, the agent would be transported to that location outside the zone. This call would fail if:
- zone == TRUE, and the script owner is not the parcel owner.
- zone == FALSE, and the script owner is not the parcel owner or the agent.
This would allow for zones that are apparently contiguous with the rest of the build by creating a portal using a volume-detect prim, zones that are entered using a magic word, zones that are "caves" in an open area, zones accessed by clicking on a switch, and so on.
A landowner could place a house entirely in the privacy zone, with a simple single-prim model on the surface using llVolumeDetect... walking through the door would transfer you to the "inside" of the house.
A landowner could place a single prim volume-detect door against a wall inside their house. Walking through it would transfer you to a "private room".
Allowing the agent to transfer himself out of the zone seems to be a useful safety feature that does not create security issues otherwise.
|
|
Description
|
A landowner can request the creation of a "basement" zone for a parcel. The "basement" zone would be in the boundaries of the parcel, but isolated from anything else in the sim. The proposed implementation is a region between -1024 to -768 meters altitude, limited to the borders of the parcel, sharing the parcel's prim quota. Objects in this zone would not interact with anything outside the zone: the zone border would be a solid wall (like the edge of the void), agents in the zone would not receive any object data or chat from outside the parcel boundary, and so on.
- For physical objects, each zone would be a separate collision group.
- Non-physical objects would be blocked at the wall. Physical objects would bounce off it.
- Object data in the zone would only be transmitted to clients inside that zone.
- Chat in the zone would only be transmitted to listeners inside the parcel.
- LSL script calls like llGetPos() would return <x,y,z+1024>
- llgetRegionCorner() would return <region_x,region_y,-1024>.
Access to the zone should be through a script call "llZoneTransfer(key agent,vector position,integer zone)". If the zone value is TRUE, the agent would be transported to that location in the zone. If the zone value is FALSE, the agent would be transported to that location outside the zone. This call would fail if:
- zone == TRUE, and the script owner is not the parcel owner.
- zone == FALSE, and the script owner is not the parcel owner or the agent.
This would allow for zones that are apparently contiguous with the rest of the build by creating a portal using a volume-detect prim, zones that are entered using a magic word, zones that are "caves" in an open area, zones accessed by clicking on a switch, and so on.
A landowner could place a house entirely in the privacy zone, with a simple single-prim model on the surface using llVolumeDetect... walking through the door would transfer you to the "inside" of the house.
A landowner could place a single prim volume-detect door against a wall inside their house. Walking through it would transfer you to a "private room".
Allowing the agent to transfer himself out of the zone seems to be a useful safety feature that does not create security issues otherwise. |
Show » |
made changes - 31/Dec/07 11:34 AM
| Field |
Original Value |
New Value |
|
Link
|
|
This issue is related to by SVC-205
[ SVC-205
]
|
made changes - 31/Dec/07 11:34 AM
|
Link
|
|
This issue is related to by SVC-241
[ SVC-241
]
|
made changes - 31/Dec/07 12:07 PM
|
Link
|
|
This issue is related to by VWR-241
[ VWR-241
]
|
made changes - 01/Jan/08 06:04 AM
|
Link
|
|
This issue Relates to SVC-599
[ SVC-599
]
|
made changes - 01/Jan/08 06:09 AM
|
Link
|
|
This issue is related to by VWR-2525
[ VWR-2525
]
|
made changes - 03/Jan/08 04:16 PM
|
Link
|
|
This issue is related to by SVC-263
[ SVC-263
]
|
made changes - 22/May/08 12:42 PM
|
Link
|
|
This issue is related to by SVC-2390
[ SVC-2390
]
|
made changes - 13/Nov/08 12:03 PM
|
Workflow
|
jira-2007-12-22a
[ 50919
]
|
jira-2008-11-14
[ 80560
]
|
made changes - 13/Nov/08 04:28 PM
|
Workflow
|
jira-2008-11-14
[ 80560
]
|
jira-2008-11-14a
[ 86517
]
|
made changes - 13/Nov/08 04:43 PM
|
Workflow
|
jira-2008-11-14
[ 86517
]
|
jira-2008-11-14a
[ 91341
]
|
made changes - 13/Nov/08 04:53 PM
|
Workflow
|
jira-2008-11-14
[ 91341
]
|
jira-2008-11-14a
[ 94727
]
|
made changes - 17/Nov/08 11:10 AM
|
Link
|
|
This issue is related to by VWR-10517
[ VWR-10517
]
|
made changes - 19/Aug/09 10:53 AM
|
Link
|
|
This issue is related to by SVC-4728
[ SVC-4728
]
|
|