2020 Simulator User Group week #14 summary

Villa Eirini, Calas Galadhon, February 2020 – blog post

The following notes were taken at the Simulator User Group meeting held on Tuesday, March 31st.

Simulator Deployments

Please refer to the simulator deployment thread for updates.

llTargetedEmail() Concerns

The llTargetedEmail() function has caused concern among users, partially due to a lack of any forewarning to users.  Specific concerns that have been raised since the deployment thread was published, with concerns such as the following being raised:

Example then. If someone make 10 alts, then get an item created by me that is modifiable (from Marketplace for example) and drop a script with TARGETED_EMAIL_ROOT_CREATOR in it that sends mails in loop… Even with 20 seconds delay that’s 3 emails per minute. 180 emails per hour. Per user. With 10 alts it’s almost 2000 messages per hour on my mailbox. Because owner of said alts can spam my mailbox via Lab’s servers without even knowing my SL-only email address for getting emails from grid.

In response to seeing these issues, Oz Linden stated at the SUG meeting:

That function was added as part of an ongoing effort to clean up how we send emails from SL… we wanted a way to send some of the emails that creators might want without having to have people put email addresses into scripts. It sends to whatever address you’ve verified. The concerns about the ROOT_CREATOR version are being discussed; exactly what we’ll do about that remains to be seen, but we’ll try hard to make it difficult to abuse.

In Brief

  • BUG-228399 “Script deletion disables vehicle controls until re-rez” appears to be an issue arising from a recent simulator update. The cause for the problem isn’t currently known, but the report has been imported by the Lab to their internal Jira for investigation.
  • BUG-228405 “Residents attempting to log into any region which use an SL Experience for access (Key Experience) get sent to welcome hub despite having allowed the SL Experience”. This appears to be the result of a region /parcel with access control via an experience removing an avatar that is being logged-in prior to all of the avatar’s data (including its permission to be in the region / parcel) having loaded – thus causing the region to assume avatar is not supposed to be there. It is an issue known to the Lab.