Simulator User Group
Not a lot to report this week; some discussion on documenting throttles on various LSL requests (i.e. updating wiki entries to indicate those functions that have throttles, rather than providing specific throttle information), and the inevitable region crossing chatter.
Server Deployment Plans
- On Tuesday, October 2nd, the SLS (Main) channel was updated with server maintenance package 18#18.09.20.519894, comprising the simulator update for Bakes on Mesh.
- I believe this update still requires a Bake Service update (support for 1024×1024 textures).
- On Wednesday, October 3rd, the three main RC channels should all be updates with service maintenance package 18#18.09.24.519940, comprising internal fixes.
The following two viewers were updated on Friday, September 28th:
- Estate Access Management (EAM) RC viewer, to version 184.108.40.2060057, first RC release.
- Spotykach Maintenance RC viewer, version 220.127.116.110059, first RC release.
At the start of week #40, all other viewers remain as follows:
- Current Release version 18.104.22.1689298, dated September 5, promoted September 26. Formerly the Rakomelo Maintenance RC viewer – NEW.
- Release channel cohorts:
- BugSplat RC viewer, version 22.214.171.1249462, September 10. 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.
- Animesh RC viewer, version 126.96.36.1998949, August 24.
- Love Me Render RC viewer, version 188.8.131.528751, released on August 20.
- Project viewers:
- Linux Spur viewer, version 184.108.40.2069906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 220.127.116.110847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7. This viewer will remain available for as long as reasonable, but will not be updated with new features or bug fixes.
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.
- General comment on L$ reclaims: somewhat related to fraud, despite notes above. If someone receives L$ amounts as a result of fraud or similar issues, when those amounts are reclaimed via the Lab, they will show up as a transaction record in the user’s account transaction history.
- Visitor trackers – are these a violation? the Governance Team is aware they exists, and generally do not action reports relating to them (radar systems report more-or-less the same information, available from the mini-map).
- Similarly, the Governance Team tends not to get involved with tar jars that record tippers names / amounts. The suggestion for those who do not wish to have their name recorded when tipping is to tip directly, avatar-to-avatar.
- Warnings / Suspensions / Termination: Tommy Linden pointed out that the reason someone is receiving a warning or a notice of suspension / termination will receive “a specific reason” on why the action is being taken in the e-mail notifying them of the warning / suspension.
- Bans and Termination: the Governance Team only ban / terminate as a result of in-world issues related to platform governance. However, users can be banned / terminated by other LL teams (e.g. fraud, legal / IP), depending on the nature of the infraction / activity.
- Can SL users be banned for things placed on external blogs, etc? As far as the Governance Team is concerned – no. It is recognised that the team have no jurisdiction over mediums and services outside of those owned by Linden Lab.
- Users who believe their personal data is being incorrectly publicised via the likes of blogs, etc., on other services, or believe they are being defamed, are advised to go through the complaints process native to the platform in question, and not file an Abuse Report with the Lab.
- Issues the Lab have with external services, websites, etc., that are felt to be violating things like the company’s brand usage, trademarks, or which might be seen as defamatory, are dealt with by the legal department.
- Personal questions: asking personal questions – even repeatedly – is not actionable as an AR. No-one has to answer questions, and other avatars can be muted / block if they persist. However, if someone does repeatedly harass a user with personal questions, etc., even beyond blocking, the an AR for harassment can be raised.
- 24/7 coverage: the Governance Team is “not totally” active on a 24/7, but are deliberately unpredictable in hours kept so that times when Governance may not be available can be easily calculated by potential troublemakers.
- Does the GTeam track those banned from regions / parcels? No. The region / parcel capability is there for region / parcel holders to use. However, ARs can be a means to identify serial griefers.
- Does the simulator save a copy of the simstate when an AR is filed? No, however, the logs, etc are available for review during an investigation – providing the AR is filed within a reasonable time of the incident occurring.
- Should specific sections of the TOS / Community Standards be quoted in an AR: they can be, but it is not a requirement. A clear description of the incident, with all relevant information and an accurate AR category filing is far better.
- ARs against copybotting, IP infringement: these are not investigated, but attempts are made to educate on how to file a DMCA.
- Nudity on Moderate regions: generally considered OK, but nudity with sexual connotations (e.g. sexual acts or a naked male avatar with an erection, in public places) can be AR’d.
- Region / parcel holders are free to specify no nudity and / or no sexual acts on their regions, regardless as to the rating.
Subject to confirmation on the Governance User Group wiki page, the next meeting should be on Tuesday, October 16th, 2018. However, the location may change.