I strongly agree with the sentiments expressed by Laura, as well as the follow-ups by Kyoko, Han, and Emilia. At this time, I remain firmly opposed to the very concept of security orbs on the ground level. All of my parcels are completely open and I welcome visitors. Those who desire orbs may do so over 1000m.
In my experience, orbs address a problem which I feel we do not have in CDS. Instead, I use a completely free solution, called Hello Visitor. With "Hello Visitor", I IM or Chat a nearby guest with a friendly greeting. This usually results in a friendly conversation; on rare occasions, the embarrassed guest TPs away on his own.
I may entertain obs at the ground level, under specific conditions, including but not limited to:
* A very tight affected volume of area
> Interior spaces only
> What is the technical granularity of this volume?
- Parcel dimensions are limited to a crude, 4x4 grid
- Many spaces, particularly in NFS, have an irregular shape
- The ground floor of spaces may be commercial, and must not be restricted in any way
- Airspace should not be restricted
* Warnings set to "nudge" not "shove"
> A simple notification, not an eject or TP home is sufficient for reasonable people
> There are other, less invasive Land tools to specifically exclude the unwanted
* A single, standard, CDS-approved orb make/model
> Ensures compliance with CDS-orb technical capabilities
> Reduces training required for EMs who will be called upon to help configure orbs and ensure policy compliance
* The orb is provided by CDS, configured by EM
> A one-time charge for a CDS-owned copy version, paid by "CDS"
- Ensures parcel owners use the approved model
- Eliminates wasteful spending by parcel owners, buying the same device
> A nominal per parcel "setup fee", perhaps 100L, may be applied to offset the CDS cost for the device
> The orb should be owned by a permanent land management account, ie. Rudeen
- Certifies that the orb will always be accessible to CDS management, regardless of EM availability or membership
- Allows the EM to assist and validate the proper configuration of the orb
^ Adds to the EM workload
^ Only way to be certain that the orb is configured correctly, per policy
^ Included as part of the EM's on-boarding process: welcoming the owner, certifying building compliance, and configuring orb
Changes to the orb policy will require a change to the general covenant and may also affect region-specific covenants as well.