After weeks of waiting Patch Linden has announced the final results on the Second Life Forums under the Linden Homes section.

The next Linden Homes theme is Tiki/Water Theme after having the most votes in a recent poll. The runner up was Alpine Style Theme (Snow).

The lab are currently deciding on which theme will be in line with Premium or Premium+. Work is due to start very soon if not already.

The team at the lab have been doing off-site training recently which is probably one of the main reasons for the delay. The team has fallen behind apparently but is now focused on catching up which may take days/weeks.

Here is the full announcement below from Patch Linden on 5th August 2024 via Second Life Forums….

The winner:  Tiki/Water Theme

Runner up:  Alpine Style Theme (Snow)

Owing to our offsite training, the team has fallen somewhat behind and is now focused on catching up. We have yet to determine which theme will be in line with Premium or Premium+, but we expect to make this decision promptly.

Thank you to everyone who participated in the poll and helped decide the upcoming themes for Linden Homes!

Can’t wait to see the new Tiki/Water Theme developments take place in the months ahead.

Have A Great Week From All Of Us At Zoha Islands Fruit Islands

Governance Team: Quick Facts

• The team is relatively small – under a dozen in size – but handles an average of 400-500 Abuse Reports per day
• All Abuse Reports get reviewed as the first stage of an investigation, with priority given to those seen as critical (such as an in-progress griefing attack).
• All ARs that can be investigated are investigated. However:
  • How far the investigation goes largely depends on whether the AR is filed against something Governance is empowered to investigate, and how much meaningful information is supplied in it.
  • The Governance Team intentionally does not report back on the outcome of their investigations for a number of reasons. Just because the outcome might not be visible to the reporter / match their expectations when filing an AR, does not mean the report was ignored.
• One of the biggest issues with incoming Abuse Reports is that they often lack the basic information required in order for an investigation to be properly carried out.

What is an Abuse Report?

The Abuse Report (AR) is for reporting any individual or group of avatars or any in-world object engaged in an activity deemed inappropriate under the Second Life Terms of Service  / Community Standards and/or is in contraction to the maturity rating for a region.

ARs apply to: griefing, spamming, age play, assault / pushing / disturbing the peace, disclosure of personal information, fraud, harassment, indecency and Skill Gaming violations. In addition, there are Welcome Area Guidelines governing places like Infohubs, which contain restrictions on what should not be done in those areas with any violations also subject to ARs. Report.

There are also certain things that do not apply to ARs. For example, being banned from a particular group or region or parcel, or a dispute over rental payment between residents are not actionable via AR.

ARs can be filed by anyone suffering abuse, or by those directly witnessing an abusive act. However, this does not mean teleporting multiple people into a location and having them file reports as well. Rather than “speeding up” any investigation, it can actually slow down the entire process by forcing Governance to spend time reviewing dozens of additional (and possibly contradictory) reports.

What Is The Governance Team Looking for in a Report?

The Governance Team is looking for clear, concise and consistent information in an Abuse Report, as summaries in the image below and expanded upon in the following sections.

Accessing the Abuse Report Floater

The AR floater can be accessed via:

• Menu bar > Help > Report Abuse.
• By right-clicking on an avatar or object and locating / selecting Report Abuse from the context menu / pie menu.
  • Make sure you have the right avatar / object selected when doing this.
  • Launching the AR floater using either of these two options will auto-complete parts of the form.

The following guidelines are intended to help with filing an AR.

Screen Shots

Where possible, try to include a screen shot of the situation you are reporting. It can be the most effective means of illustrating what is going on, and gives the Governance Team clear visual proof / evidence of what has happened. It can also make up for information missed from the rest of the report.

The slide below outlines some of the key points to remember when using the AR floater to capture a snapshot – click to enlarge it in a separate browser tab for ease of reading.

Note that most viewers do not have a refresh button for the snapshot preview, so try to make sure all the information you wish to capture is on your screen. If you are unable to get a screen shot for whatever reason, it is important you provide clear, accurate information in the Summary and Details section of the report (see below).

Object Picker

The Object Picker allows you to identify an abusive object (e.g. a particle / noise spammer, a weapon, etc.), and include its name and owner in the body of your Abuse Report. Instructions on how to use it are included in the AR floater, and this section will be auto-completed if you launch an AR by right-clicking on an abusive object. Remember you can further verify the item by including it in a snapshot with the Edit floater open to show the object name & owner.

Report Categories

The Abuse Report floater includes a pre-defined, drop-down list of categories which should be used when filing a report. Notes on the *valid* categories can be found here. Note that filing under the wrong category doesn’t prevent a report from being investigated, but it can slow things down, particularly if there is insufficient information provided elsewhere in the report.

Abuser Name

This allows you to grab the name of someone causing abuse from those around you. If you launch an Abuse Report by right-clicking on an object or avatar, this section will auto-complete (make sure you have selected the right avatar), otherwise click the Choose button and follow the on-screen instructions.

• Location should be the SLurl of the location where the griefing took place. If you were forced to leave the location before filing an AR, use your teleport history to obtain the region details. If you are taking a screen shot of a situation, make sure the region details are visible at the top of your viewer window as further verification.
• Summary should include a clear summary of the situation.
• Details should include a concise and clear explanation of the situation and any steps you may have taken to rectify it (e.g. asking someone who has littered some land if they would come and clear it up). Be as specific as possible, particularly if you cannot include a screen shot.
  • Do not cut and paste chat or IM text in this section, as this cannot be accepted as evidence, due to the fact it may have been edited. Text should be shown by Including the relevant chat / IM tab from the Conversations floater in any screen shot you take.

What Else Can or Should Not be Filed with a Report?

• You can include anything else provided as a part of the official viewer which might be used to help investigate a report (e.g. the Bumps, Pushes and Hits  floater (Help > Bumps, Pushes and Hits) could be displayed to indicate physical abuse in a “safe” area).
• The following cannot be accepted by the Lab as part of an Abuse Report:
  • Chat or IM text which has been pasted in to the Details section of the AR. Copied text can be too easily altered after-the-fact, and so is not seen as acceptable evidence by the Lab.
  • Voice or other recordings – again due to risk of post-editing or dubbing.
  • Screen captures outside of those taken by the AR tool.

Other Items

Profile Violations

All information within a profile should be G rated. With the general exception of Picks, anything which is not G rated can be AR’d, this includes:

• Nude or sexually explicit images (flesh or avatar)
• Profiles with sexually explicit language in the About descriptions
• Profiles demonstrating intolerance, hatred, etc., in any text they contain can be (including text and images associated with Picks)
• Profiles which “out” the Alt(s) of another avatar
• Profiles which explicitly advertise sex may also be subject to AR, although this is a grey area (e.g. “IM me for a good time” isn’t explicit, and would not be actionable; however, a list of sexual acts and prices could be considered actionable).

Offending profiles should be featured in the screen shot submitted as a part of the report /a>.

Note: Disclosure of personal information in a profile by anyone other than the profile owner can also be AR’d, regardless of the fact it appears in the profile owner’s profile. See Disclosure > Real World Information in the Abuse Report Category notes accompanying this article.

Exploits

If you have a strong suspicion someone is using an exploit to grief (e.g. to crash a region), the preferred method of reporting is via a SECurity category JIRA. However, if you have never used the JIRA system, or are uncomfortable in using it, you can file an Abuse Report instead / as well. Use the Disturbing the Peace categories.

Calm seas, with a nice fleet turnout, highlighted the last North Sea Open Regatta for July, 2024. The North Sea regions were well behaved with one DNF (Did Not Finish) recorded on the day. The lone DNF came during the small boat portion as a skipper deleted her boat after getting lost and wandering five regions off the course. The crowds that gathered on the beaches of the islands in the Ziziphus, and Genip regions, and along the Poseidon Centre Spectator Pier and small race dock in the Eden Jakana region, savored a great display of fleet racing from this weeks skippers.

This weeks small boat fleet, sailing on the North Sea Bowline Reverse course, was made up of a split majority of four Isard Mini Transats and four Bandit 22 LTEs. Three Bandit IFs, two sailing single-handed and one crewed respectively, one Isard Snipe, and one Shields Class rounded out this weeks small boat fleet. Meanwhile, the big boat fleet, sailing a two lap affair on the North Sea Long Loop course, was made up of a majority of three The Mesh Shop (TMS) I-Mocca 60s, two sailing single-handed and one crewed respectively. Two Trudeau 12 Metres, two TMS Ushuaias, one ACA33, one Isard Machcichaco, and one WildWind SC-40 rounded out this weeks big boat fleet.

Race Director: Cryptic
Assistant Race Director: Daenerys
Wind: SW (225°) 18kts

Note:
Did Not Finish (DNF) = number of finish +1
Did Not Start (DNS) = number of start +1

Today’s winner was Kristaly (kristaly Resident), with Kael (Kael Decosta) second, and Cole (ColeBatriani Resident) in third place. Congratulations to all of you. Thank you to everyone who came to sail and spectate and the SLCG for helping with race duties.

Race Notes:
Rugger (ruggeromare Resident) and Chaos (OnechanbaraChaos Resident) registered as a team prior to the start of the race, therefore their points are accredited together.

Emileigh (Emileigh Starbrook) was disqualified (DSQ) during the big boat portion for sailing an incorrect course, sailing north of the first mark, the green buoy in the Ziziphus region, on the second lap, instead of south as indicated for the course.

Aoife (Aoife Treeflame), Jamie (JamieGawith Resident), and Mary (Marousca Resident) all finished tied with 11 points. Rule A8.1 of Appendix A, Scoring, 2021 – 2024 World Sailing Racing Rules of Sailing is used to break this tie:

“If there is a series score tie between two or more boats, each boat’s race scores shall be listed in order of best to worst, and at the first point(s) where there is a difference the tie shall be broken in favour of the boat(s) with the best score(s). No excluded scores shall be used.“

With the race results rearranged in best to worst finish order, per A8.1, the tie breaks in Aoife’s favor with having a first place finish over Jamie’s third, and Mary’s fourth place finishes as their best.

Katey (KateyBeach Resident) and Juicy (juice651 Resident) both finished tied with 17 points. Rule A8.1 of Appendix A, Scoring, 2021 – 2024 World Sailing Racing Rules of Sailing is used to break this tie:

“If there is a series score tie between two or more boats, each boat’s race scores shall be listed in order of best to worst, and at the first point(s) where there is a difference the tie shall be broken in favour of the boat(s) with the best score(s). No excluded scores shall be used.“

With the race results rearranged in best to worst finish order, per A8.1, the tie breaks in Katey’s favor with having a sixth place finish over Juicy’s eighth place finish as his best.

Emileigh (Emileigh Starbrook) and Di Si (Diamant Siamendes) both finished tied with 22 points. Rule A8.1 of Appendix A, Scoring, 2021 – 2024 World Sailing Racing Rules of Sailing is used to break this tie:

“If there is a series score tie between two or more boats, each boat’s race scores shall be listed in order of best to worst, and at the first point(s) where there is a difference the tie shall be broken in favour of the boat(s) with the best score(s). No excluded scores shall be used.“

With the race results rearranged in best to worst finish order, per A8.1, the tie breaks in Emileigh’s favor with having a tenth place finish over Di Si’s eleventh place finish as her best.

The Second Life Mobile App team have now added your current L$ balance on the Second Life Mobile Alpha app. To view your L$ balance go to the Menu > Settings > Developer Tools then press on the Check L$ Balance button.

This is very exciting indeed to see this finally added. The mobile app team are now “testing the basic functionality of WebRTC voice on both desktop and mobile”. Soon it will go live on Second Life Mobile Beta.

To see what’s new please see below…

What’s New – As of 22nd July 2024.

Dear Alpha Testers,

We are excited to announce several new updates and features for the Second Life mobile app! Your feedback has been invaluable, and we’re committed to improving your experience. Here’s what’s new:

WebRTC Voice Integration:
We are testing the basic functionality of WebRTC voice on both desktop and mobile.

To test this feature, find the settings in the developer tools. Enable voice settings and follow the steps to verify audio between desktop and mobile in WebRTC-enabled regions.

Typing Progress Messages:

Typing animations are now available in Nearby, DM, and group chats to enhance communication visibility.

Check L$ Balance:

You can now check your L$ balance directly within the app.

Navigate to Menu > Settings > Developer Tools and hit the “Check L$ Balance” button to verify your balance.

Fix Push Notification Settings:

We’ve addressed bugs with push notifications. Friend and non-friend IM settings should now be saved consistently.

Direct Message Option in Multi-User Chats:

The “…” icon above chat messages now includes a “Chat” option in Nearby Chat or group chats, allowing for easier navigation to direct messages with participants.

Custom Dropdown Components:

We’ve replaced browser-native dropdowns on the login screen with custom react components for a consistent look across devices.

Feedback

Your participation in testing these features is crucial. Please provide feedback on any issues or suggestions you encounter. If you experience any difficulties or need assistance, don’t hesitate to reach out to our support team at support.secondlife.com.

Thank you for your continued support and patience as we work to improve the Second Life mobile app!

Have a Great Week From All Of Us At Zoha Islands/ Fruit Islands