Update, January 10th: Subsequent to this post being published, the deployment plans for the RC channels were revised, and details have been add below to reflect this. My thanks to Kyouko for drawing my attention to the updated server deployment thread.
As always, please refer to the server deployment thread for the latest news and updates.
There are no planned deployments for 2018 week #2. All channels remain on the same server release 17#17.12.01.511131. However, the Main (SLS) channel was restarted on Tuesday, January 9th, 2018.
There was no deployment to the SLS Main channel on Tuesday, January 9th, 2018, leaving it on server release 17#17.12.01.511131. The channel was, however, restarted.
Following the original publication of this update, the server deployment thread was updated to indicate there would be a deployment to the major RC channels on Wenesday, January 10th: server maintenance package 18#18.01.08.511751, comprising internal logging improvements.
The Alex Ivy RC viewer was updated to version 18.104.22.1681732 on January 9th, 2018. All other viewers currently remain as per the end of week #1:
- Current Release version 22.214.171.1249906, dated November 17, promoted November 29th – formerly the “Martini” Maintenance RC – 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):
- Project viewers:
- Obsolete platform viewer version 126.96.36.1990847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.
No Copy Exploits Update
An area of concern / upset for content creators has been the use of server exploits to generate copies of No Copy items. While a long-standing problem, the issue has gained a lot more coverage of late due to the frequency with people have been using various exploits to illegal copy and then sell gacha items. In November, the Lab closed one exploit used in generating No Copy items, and reported this, and the steps they put in place to help recognise when someone might be attempting to use it (see: Exciting Improvements to SL Fee Updates to Enable Even More).
Since then the Lab has continued to work on issues (see my SL project update from 2017 week #47). However, there have been mistaken claims that the Lab stated it had resolved “the” exploit, which is not the case – see the Lab’s blog post above), which Oz and Simon sought to correct in the meeting, with Oz Linden stating:
We never said we were sure we’d fixed all possible exploits, and we won’t say that because we might not know about them all.
Simon then added:
I know that statement and we deliberately and clearly said it wasn’t done. There was more work but we were making progress. I know a lot of people reading it probably wanted it to say (and mean) we fixed everything. We know we haven’t.
In terms of what more is being done, Oz said:
If I were to tell you now that we’re working on “method X” for object copying, I’d be letting people who might not know about it that it existed, and telling those who know how to use it to hurry up while the getting is good.
- New Linden: the Simulator User Group meeting on Tuesday, January 9th was joined by Bugsly Linden. A new member of LL’s QA team, he joined the Lab around a month ago – and is a former Second Life resident.
- Group chat issues: there has been a noted uptick in group chat issues. Commenting on this, Simon Linden said, “We looked into group chat recently and did a few things that should have helped. [In the meantime] for group chat lag problems, please send in a support ticket – the group name is crucial as its most likely a specific server needs attention. Also [give the] time it happens, and the region you’re on. Sometimes it’s the region’s issue.”