HSOrb 13.036 Medium:Clearer Attack & Age msgs+profile links;Pop-ups when add/del names;Faster Update;Avatar Script Time checks #secondlife

SUMMARY:

• Experimental third parameter added to /8slw and /8slt for checking avatar script CPU time usage.* Click for more. (Initial testing shows that a newly arrived avatar can have a large spike in script time usage before it drops down. The Orb may need further refinement to ignore this initial spike. See v13.037+ above)
• Floating text display shows script memory/CPU time usage in µs (micro-seconds).*
• UpdateDisk must be within 10m of an Orb to update it (was 20m)
• Clearer messages about why someone was attacked.
• Add/Del’ing names causes a pop-up dialog reply because many people are now using Orbs from far distances due to one Orb covering a whole region.
• Notifications now include SL Time (SLT) and link to profile.
• Updates after this one will back up and restore names 7 times faster.
• Script memory check uses decimal point numbers.
• Log records attack reason also.
• A single attack notification sent now. Not two.
• Web page shows Script Limits, Teleport properly.
• Visible/Invisible fixes.

* A simulator under ideal circumstances produces 45 frames per second ≈ 22,222µs (micro-seconds) per frame. A portion of this 22,222µs is devoted to running scripts. An avatar who has a script time of 1000µs would be using 4.5% of the simulators processing time.

DETAILS:

PDS HomeSecurity Orb V13.036:

• Web page shows Script Limits, Teleport properly.
• Visible/Transparent minor bug fixes (/8visible)
  • Visibility of floating text and texture transparency will be preserved in the scripts memory for all updates following this one.
  • Turning off/on/updating the Orb obeys the Visibility state.
  • If your Orb has visible floating text and invisible prim try /8visible (or /8v) a couple of times to clear it.

PDS HomeSecurity Orb V13.035:

• Removed obsolete Twitter code from VLog.
• Fixed minor bug where Script memory checks were using integer rather than float. i.e. ignoring numbers after the decimal place.
• Improved AvLimits menu to show decimal memory usage.
• VisitorLog records attack reason along with attack type.
• VisitorLog no longer sends unneeded Attack messages to Operator when Scanner>VisitIM is on. (Weapon only should send messages to the Operator about a Target being attacked when Weapon>NotifyOp is set to IM or Menu.)
• Changed Script Limit, Warning pop-up to say “Preferred <” and Script Limit, Teleport to say “Limit”
• Script Limits checks avatar’s running script count now rather than total script count. i.e. Stopped/crashed scripts are ignored.
• /8slw and /8slt now accept a third parameter for scripttime in µs (micro-seconds) per sim frame.*
  The new format is: /8slw scriptmb [scriptcount] [scripttime]
• Floating text display has replaced avatar script count with avatar script time in µs (micro-seconds) per sim frame.*
• Added “script_time_warn” and “script_time_teleport” to Settings notecard. NOTE: these use decimal point seconds (not micro-seconds).

PDS HomeSecurity Orb V13.033 beta:

• Removed some debug code from Command Log script
• Changed UTC Time to SL Time for Weapon Attack messages (IM or Pop-up).
• Changed UTC Time to SL Time for Visitor Log IMs.
• Adding a name causes one notice not multiple notices. e.g. Adding an Operator causes a notice and also adds to Friends List, however only adding to Operator causes a message.
• Name backup and restoring, during updates, now 7 times faster. (yay!) This won’t show until the updates following this one.
  Unintended  consequences:
  • Settings notecard could take multiple comma delimited friend=, target=, operator= and network= values on the same line. e.g. “friend=psyke.phaeton,another.name“
  • /8add[f|g|o|n] commands could take comma delimited names. e.g. /8addo psyke.phaeton,another.name
  • Using comma delimited names is not recommended because sanity checking is not done. (For example; adding someone as an Operator/Friend/Guest will not remove them from Target List and vice versa, checking for duplicate names does not occur, etc.)
  • You cannot delete multiple names at the same time.
• Moved Friend/Guest backup to before Target backup so that should there be a memory shortage a Target is dropped rather than a Friend/Guest.
• Added “Full” message to pop-ups when adding names but memory is full.

PDS HomeSecurity Orb v13.031 beta:

• Over time the Orb’s tasks have moved on from the simple black-list/white-list. The Orb can also remove people because of display names, script usage or avatar age. However attack messages have remained unchanged and therefore unclear. I have changed the Notify Target and Notify Operator messages to clearly state what has occurred and why.
• Since 1 Orb now covers a whole region, shouting commands to add and remove names is more common. Since the Orb only llSay‘s back (20m range) Operators past 20m get no feedback. Now the Orb llSay‘s and sends a pop-up to the Operator. These new pop-ups only apply to adding and removing names/networking.
• Changed messages regarding Avatar Age to more obviously show: less than and equal to X days old avatars are removed.
• New command: hide “Operated by: Name” in Notify Target pop-ups: /8nthop on|off 
• Tidied up Weapon script to avoid duplicate messages.
• (Weapon) Notify Operator by pop-up now has a “Name (user.name)” and a link to target’s profile (shows in version 2+ based SL clients).

UpdateDisk:

• Time-out now 10mins because names can take longer than 5 mins now to backup or restore.
• Will now update the first Orb to reply to it and ignore any other subsequent Orbs in range. Previously a different Orb could steal the UpdateDisk focus from an Orb during the update. Oops!
• The Orb must be within 10m of the UpdateDisk (was 20m). Updated initial float text to reflect this.
• The UpdateDisk now shows in the floating text which Orb ID is being updated as well as the particle effects.

Thanks to teqi.falta for the reports, suggestions and testing.

Web:

• Changed WordPress “Documentation” link to point to V13 documentation.
• Added /8v short-cut to the /8visible entry in v13 documentation.

To Do:

• Update bulk packs at store and MarketPlace once it is clear this version is stable.
• Forum announcement.

HSOrb 12.030: Bug Fix Minor: ListNear added names incorrectly. OLS setting lost when updating.

v12.029 – ListNear updated to handle user.names correctly.

v12.030 – additional fixes for ListNear

2012-01-27

v12.030.1 – Update process did not record and restore Other Land Safe setting. Updates were causing OLS to turn off. This fix will be incorporated into the next Orb update. There is no point sending out an update to update the update process only. Thanks Lance Corrimal for the report.

HSOrb 12.026: Bug Fix Minor: Script Limits Menu not updating

The Avatar Script Limits menu text was not updating (memory and script count allowed) when the settings were changed. Fixed.

HSOrb 12.022: Minor fixes to Age settings

Changes:

1. Fix: Added turning off Age Limits when /8reset is used. Fixes my past mistake where I accidentally left Age Limits set to 100 days by default from happening in the future.
   
2. Fix: When command /8age off is used the Security script also takes note of the change. This will stop Updates from restoring a pre-”age off” setting.
3. Added a chat warning when Update sees, or a command activates, Age Limits. This helps alert the Operator to the above bugs so they can correct the setting it if they wish.

HSOrb v12.020: Includes ban by age for X hours

Working on adding optional ban for all avatars under a certain age for X hours only or forever. The idea being if someone is alt-griefing you continuously using new avatars you can ban all avatars under, say, 2 days old, for an hour then let the age banning lapse when the hour ends. This walks the fine line between solving alt-griefing without causing undue limitations to new users. The idea for the limited time option comes from reading a post from Jezzybelly.

I will update this post when it is ready.

Changes:

• Added ban, for X hours (or permanently), any avatar under X days old.
• Update causes: Backup / Restore of those settings
  
• New: SETTINGS / AvLimits sub-menu:
  • Move Script Limits Warn
  • Move Script Limits TP
  • Move DispProt (Display Name Protection)
  • Add Age (Minimum Age and hours until lapse)
• New command: /8age daysold [hours]
• Rename Limits button to VRange (Vertical Range)
• Fix: DispProt, Age and Script Limits obey NoAttack mode by not attacking.
• Add Settings Notecard parameters (not needed)
• Update: failed message should point to information web page (Thanks Couldbe Yue)
• Documentation
  

HSOrb 12.016beta: Testing Avatar script limits

Released: 3 January as v12.018.

Avatar Script Limits

• Changed float text top line to (34㎅) rather than (34000b)
• Added 7㎆/8 to avatar line. Means 7MB of script memory in 8 scripts.
• Menus: Show script warn/TP limits in Scanner Menu if active.
• Changed the command from /8sl to the two shown below.
• Script Limit Teleport Home: /8slt [script usage MB] [script count] - Both can be zero for no scripts allowed, or both -1 to disable, or positive numbers. (Won’t TP Orb Friends)
• Script Limit Warning pop-up: /8slw [script usage MB] [script count] – Both can be zero to warn that no scripts allowed, or both -1 to disable, or positive numbers.
• /8tp [name or key] – TP Home command
• Logging
• Fixed Orb web page text
• Documentation: Settings notecard example gets “script_memory_warn” and “script_count_warn”
• Documentation: Settings notecard example gets “script_memory_teleport” and “script_count_teleport”
• Documentation: Commands page updated: slt, slw, tp
• Beta Testers: Fixed attacking people who have no display name set.
• Beta Testers: Fixed TP/Script warning triggered regardless of weapon option chosen
• Removed unneeded chatter from 9Backup script during updates
• Thanks to Janey Humphreys for testing and bug reports.

Other

• Shortened some lines in the Scanner menu to make them fit on Viewer 1
• Improved memory efficiency when making changes to lists of names.

To do:

• Update MarketPlace description (Land Ban and Script Limits)
• Update Home Page description (Land Ban and Script Limits)

HSOrb 12.015: New-Land ban individuals for X hours plus more

• New command: /8lb [hours] [name or key] to land ban an individual for X.X hours. Max 144hours, 0 means permanent ban. The Orb does not remember who was banned it simply passes the request to SL. It does not add them to the Target List. Use the SL client and About Land / Access to remove the ban. (12.014beta2) – Thanks Janey Humphreys
• llGetEnv() on Orb web page (12.014beta3)
• Added error IM if Orb can’t add names to ban list. (12.015)
• Add user.name on rez not needed if Full Name exists. (Not worth the extra memory usage)
• Cosmetic – Offline float text not refreshed after update completes therefore showing old version number temporarily. (12.015)
• Stopped Settings Notecard reload when VisitorLog script was updated. No impact. (12.015)
• Scanner script settings restore was, when updating, changing all settings to lower case (warning messages included). Fixed. (12.015.1)
• Changed Upgrade to Update on the menu. (12.015.1)
• Added a reminder to deed the UpdateDisk if needed to the ‘Disk being sent’ pop-up. (12.015.2)
• Orb web page shows Region software version number. (12.015.4)
• Update documentation with new lb command.

Future:

• llGetObjectDetails(id,[OBJECT_SCRIPT_MEMORY]) – Avatar script and memory usage monitoring. (12.016)

HSOrb 12.011: TP/Ban Display Name Protection obeys NotifyOp/Target settings

Check for NotifyOP IM/Menu and NotifyTarget settings when attacking impostor Display Name. Thanks Janey Humpheys

Low priority to-dos:

• Consider better Server UUID change methods

After 2010-12-08 Region deploy:

• llGetEnv() on Orb web page (12.014beta)

HS Orb to Twitter has stopped working.

Twitter has been making noises about stopping the simple and insecure method of sending messages to Twitter for some time. When this suddenly occurs the HS Orb tweets will stop working. I do not know when this will happen.

The replacement method is more secure, more CPU intensive and much more involved when done in SL scripting. I do not know yet if it will be practical to include the new method in the HS Orb. I will look into it when Twitter forces the change.

More..

UPDATE 2010-09-10: Twitter’s new system unreliable.

Twitter and Second Life make Tweeting unreliable:

• Second Life does not allow twitter.com responses to come back through its gateway/firewall because JSON, XML etc are “415 Unsupported or unknown Content-Type.” See: JIRA SVC-636
• Twitter.com OAuth is also unreliable. See: http://dev.twitter.com/status
  I have seen response times of up to 7 minutes and also no responses at all.

Between these two situations I can’t see if a tweet worked or not, nor can I trust it to work. At this stage it is too unreliable for testing. I will have another look next week when Twitter OAuth may not be so overloaded.

UPDATE 2010-09-07:

I am working on new code to use the OAuth system. You can see my testing here: http://twitter.com/hsorb

To do list:

• Learn and test the techniques needed
• Impliment into HS Orb (customise script, add menus, link_message, backup access tokens, update script)
• Work arounds (Shorten to In and Out, Remove unnecessary twitters)
• Testing (FAIL: Twitter unreliable, see above)
• Clean up code
• Option to not IM/Tweet Allowed visitors.
• Consider menu icons again.
• Final QA

UPDATE 2010-09-04:

The old method has stopped working. From Twitter:

beginning on August 17th, 2010, basic auth rate limits will decrease by 15 requests/hour on each week day;

on August 19th, 2010 at 5pm PDT, basic auth will be shut off temporarily for 10 minutes;

on August 23rd, 2010 at 8am PDT, basic auth will be shut off temporarily for 10 minutes;

on August 26rd, 2010 at 5pm PDT, basic auth will be shut off temporarily for 10 minutes; and

on August 31st, 2010 at 8am PDT, all basic auth requests will be served with a HTTP 401 error code.

Source: http://dev.twitter.com/pages/basic_auth_shutdown

Looks like I have some investigating to do on my days off.

HS Orb 11.047: Minor fix – HS Orb Tells RemoteDisplay when it is sleeping.

HS Orb was not announcing to the RemoteDisplays when it had gone to sleep. Fixed.