- On Tuesday, February 5th, 2019 the SLS (Main) channel was updated with server maintenance package 19#19.01.25.523656, comprising internal fixes.
- On Wednesday, February 6th, 2019 the RCs are likely to be updated as follows:
- BlueSteel should receive EEP update server maintenance package 19#19.02.01.523934.
- Magnum and LeTigre should receive server maintenance package 19#19.02.01.523959, comprising further internal fixes.
- There is currently a small Cake RC on Agni that is being used to iron out some transient network issues with the newest server operating system update, prior to it being move to a full RC for testing. Cake may grow a little larger before this happens.
There have been no viewer updates at the time of writing, leaving the current pipelines as:
- Current Release version 220.127.116.112263, dated December 5th, promoted December 13th. Formerly the Spotykach Maintenance RC viewer – No Change.
- Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
- BugSplat RC viewer, version 18.104.22.1683335, January 23rd. This viewer is functionally identical to the current release viewer, but uses BugSplat for crash reporting, rather than the Lab’s own Breakpad based crash reporting tools.
- Estate Access Management (EAM) RC viewer, version 22.214.171.1243351, January 23rd.
- Love Me Render RC viewer, version 126.96.36.1993177, January 16th.
- Project viewers:
- Environmental Enhancement Project (EEP) viewer, version 188.8.131.523088, January 16th.
- Bakes on Mesh project viewer, version 184.108.40.2062127, December 7th.
- 360 snapshot viewer, version 220.127.116.115934, June 6 (see my hands-on update).
- Linux Spur viewer, version 18.104.22.1689906, dated November 17th, 2017 and promoted to release status 29th November, 2017 – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 22.214.171.1240847, May 8th, 2015 – provided for users on Windows XP and OS X versions below 10.7.
Name Change Issue
A creator preparing for the upcoming Last Names / name changing capability has encountered an issue that may have broader ramifications. In sort, one of their customers was forced to take a new user name (their original name was considered “objectionable” by the Lab). However, the creator found that when sending information to an external HTTP request (object UUID, object name, owner name of the object, etc.), the object (in this case a HUD) was sending the original (objectionable) user name, not the updated user name. This suggests the user name is being caches somewhere within SL, and not being correctly overwritten if replaced.
Effort are on-hand to try to trace down the issue, but the problem is also a demonstration if why agent UUIDs should be used to trace avatars now and going forward, and not user names, particularly in light of the upcoming Last Name changes.
Governance User Group
Governance User Group (GUG) meetings are generally held on alternate Tuesdays at 13:00 SLT. They are intended to provide a forum for the discussion and education of issues involving Governance. They are chaired by the GTeam supervisor, Kristen Linden and are open to the public. Details on dates, times and location can be found on the Governance User Group wiki page.
The Governance Team is responsible for dealing with Abuse Reports, in-world abuse, forum reports, Marketplace reports, etc. It is not responsible for issues with accounts being compromised, account subscription delinquency, fraud, IP infringement, etc.
- These matters cannot be discussed at the GUG meetings.
- Issues relating to them should be reported through the recommended channels (e.g. Support for account-specific issues, via the DMCA process for IP infringements, content theft, etc).
Similarly, individual cases involving Governance issues (e.g. the outcomes of abuse report filings), cannot be publicly discussed.
- The official SL knowledge base guide to abuse reports.
- My own Abuse Report tutorial, written with input from the Governance Team.
- Are weapons testing sandboxes given more lenience by Governance WRT reports of harassment? Generally, yes, simply because these are environments designed for testing objects that can affect others. However intentional attempts to harass or grief will be responded to.
- If someone is griefing / harassing a private region and is booted by the region owner, can they still be reported? Yes, just make sure the Abuse Report has all the necessary information as is correctly filed.
- Objectionable names / Display Names: Governance will handle reports of offensive / objectionable user names, but are slightly more relaxed on Display Names. The latter is because users can disable the displaying of Display Names in their viewers. However, reports of intentional offensive or objectionable Display Names will be investigated.
- Date of Next meeting: Tuesday, February 19th, 2019.