SL project updates 40/2: TPVD Meeting; e-mail verification

Mitsumi-Town in Tokyo; Inara Pey, September 2017, on FlickrMitsumi-Town in Tokyoblog post

The majority of these notes are taken from the TPV Developer meeting held on Friday, October 6th 2017. The video of that meeting is embedded at the end of this update, my thanks as always to North for recording and providing it. time stamps in the text below will open the video in a separate tab for ease for reference to the relevant points of discussion in the meeting.

The meeting was chaired by Rider Linden, who was filling in for Oz, and was somewhat foreshortened.

SL Viewer

There were no updates to the current crop of official viewers during the week, leaving the pipeline as:

  • Current Release version 5.0.7.328060, dated August 9th, promoted August 23rd – formerly the Maintenance RC
  • Release channel cohorts:
    • Voice RC viewer, version 5.0.8.329250 on Friday, September 29th
    • Maintenance RC viewer, version  5.0.8.329115, dated September 22nd.
    • Wolfpack RC viewer,version  5.0.8.329128, dated September 22nd – this viewer is functionally identical to the release viewer, but includes additional back-end logging “to help catch some squirrelly issues”
    • Alex Ivy 64-bit viewer, version 5.1.0.508209, dated September 1st
  • Project viewers:
  • Obsolete platform viewer version 3.7.28.300847, dated May 8th, 2015 – provided for users on Windows XP and OS X versions below 10.7.

Quick notes:

  • [4:35-4:52] Work is continuing to fix the texture crashes in the 64-bit Alex Ivy RC.
  • [5:25-5:40] There is a reference to Voice changes, however, the question is non-specific, and it is unclear if it refers to the current Voice RC (updated at the end of week #39) or to further updates, the question is deferred to Oz (who is directly involved in the Voice project).

E-mail Verification

[2:56-4:00] As noted in part 1 of this week’s report, the Main channel deployment saw an update to IMs-to-e-mail as part of the Lab’s move to only handling verified e-mail addresses.

The sending / forwarding of messages to unverified addresses is not blocked – as yet. However, once a viewer-side changed has been deployed, accounts with unverified emails will no longer be able to request that IMs be forwarded to e-mail; attempts to enable the viewer-side setting will fail, and result in a message advising the account holder to verify their e-mail address.

Potential Interest List Change

[15:52-18:40] (with a lengthy silence)] There is a potential simhost change to the Interest List under discussion at the Lab. This will in essence reduce some of the aggressive culling of updates from objects behind an avatar (particularly useful in the case of light sources, moving objects, etc). If it goes ahead, this update could also benefit the 360-snapshot viewer.

Other Items

 

Estate Tools Update

[6:07-10:40 (ish) and 13:10-14:20] There is a lengthy on-off exchange, in Voice and text (with some long pauses in both) regarding the Estate Tools updates in the viewer. In short: updates to the estate ban lists (see BUG-8883 and BUG-40676 as examples of requested changes), have resumed. however, as Alexa Linden, who is running this project, was unavailable for the meeting, no detailed update was possible.

Viewer Build Issue

[10:50-12:00] There is “progress” in fixing an incorrect viewer build update involving a change to the Cmake files which results in a forced rebuild of the Windows version of the viewer (the “-z0” issue).

In-world Posing

[20:48-end of meeting] NiranV Dean has been experimenting with a means of in-world posing an avatar through the viewer (e.g. for things like photography), which would be visible to the person posing their avatar (as it would require server-side support to be visible in all viewers). There may be interest from the Lab in accepting as a proposal / contribution, if the details of what is required can be agreed between the Lab and Niran.

There were concerns among those attending the meeting (and raised largely in text) on what Niran is trying to achieve and how it might related to content ripping. If nothing else, the conversation underlines the need for a clearly thought-out proposal outlining the idea, its purpose, how it might be implemented, potential issues which will need to be considered and addressed, etc., rather than requesting people “try” the idea and give feedback.

Date of Next Meeting

The next Third-Party Viewer Developer meeting will not be until Friday, November 3rd, 2017.

 

Advertisements

Have any thoughts?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s