Tutorial

We have had quite a few reports in our support system about abuse and we wanted to share with residents on how to use Abuse reporting. Of course you still need to report to Zoha Islands support system so we can know about such abuse. Continued reporting Does help.

Raising Abuse Reports in Second Life

Griefing, be it through word, action, noise, or object (as seen here), etc., is one of the items covered by the Abuse Report

The following notes are drawn from a presentation Governance Team manager Tommy Linden and team member Corky Linden are making to various communities within Second Life as part of an initiative to better disseminate information about the Governance Team, and on filing Abuse Reports (ARs). The hope is that the information provided will give users a better understanding of what the Governance Team hope to see provided in an Abuse Report in order to fully investigate it.

 

Note that  official information on Abuse Reports can also be found in the Knowledge Base.

 

 

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.

A “good” Abuse Report, presenting all the information and making good use of a screen shot – click to open the slide in a separate tab for easier reading. With thanks to Corky Linden

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.

Abuse Report snapshots: click on the slide to open it in a separate browser tab for easier 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, Summary and Details
  • 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.

 

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

North Sea Open Regatta – July 31st 2024

The results for today’s North Sea Open Regatta have been posted Congrats to the winners. and thanks to the SLCG for helping with race duties.

Small boat fleet, from the left (in boats): Emileigh (Isard Mini Transat), Juicy (Bandit IF), Katey (Bandit 22 LTE), Mary (Shields Class), Rugger & Chaos (Bandit IF), Cole (Bandit IF), Di Si (Bandit 22 LTE), Kael (Isard Mini Transat), Jamie (Bandit 22 LTE), Aoife (Isard Mini Transat), Bea (Bandit 22 LTE), Kristaly (Isard Snipe), and Zimtzicke (Isard Mini Transat). On the Race Committee Boat: Cryptic. On the dock: Red, Daenerys, Zoe, Rossy, Josie, Caethes.

Small boat fleet, from the left (in boats): Emileigh (Isard Mini Transat), Juicy (Bandit IF), Katey (Bandit 22 LTE), Mary (Shields Class), Rugger & Chaos (Bandit IF), Cole (Bandit IF), Di Si (Bandit 22 LTE), Kael (Isard Mini Transat), Jamie (Bandit 22 LTE), Aoife (Isard Mini Transat), Bea (Bandit 22 LTE), Kristaly (Isard Snipe), and Zimtzicke (Isard Mini Transat).
On the Race Committee Boat: Cryptic. On the dock: Red, Daenerys, Zoe, Rossy, Josie, Caethes.

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.

Big boat fleet, from the left (in boats): Emileigh (Trudeau 12 Metre), Jamie (Trudeau 12 Metre), Juicy & Di Si (TMS I-Mocca 60), Chaos & Rugger (TMS Ushuaia), Kael (TMS I-Mocca 60), Aoife (Isard Machichaco), Kristaly (WildWind SC-40), Cole (TMS Ushuaia), Zimtzicke (TMS I-Mocca 60), and Mary (ACA33). On the Race Committee Boat: Cryptic. On the dock: Red, Daenerys, Leela, Rossy, Josie, Zoe, and Caethes.

Big boat fleet, from the left (in boats): Emileigh (Trudeau 12 Metre), Jamie (Trudeau 12 Metre), Juicy & Di Si (TMS I-Mocca 60), Chaos & Rugger (TMS Ushuaia), Kael (TMS I-Mocca 60), Aoife (Isard Machichaco), Kristaly (WildWind SC-40), Cole (TMS Ushuaia), Zimtzicke (TMS I-Mocca 60), and Mary (ACA33).
On the Race Committee Boat: Cryptic. On the dock: Red, Daenerys, Leela, Rossy, Josie, Zoe, and Caethes.

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.

Emileigh, in her Trudeau 12 Metre, sailing north of, instead of south of the green buoy in the Ziziphus region, on her second lap of the North Sea Long Loop course, during the big boat portion of the North Sea Open Regatta, on Wednesday, July 31st, 2024.

Emileigh, in her Trudeau 12 Metre, sailing north of, instead of south of the green buoy in the Ziziphus region, on her second lap of the North Sea Long Loop course, during the big boat portion of the North Sea Open Regatta, on Wednesday, July 31st, 2024.

 


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.

Skipper Best Finish Next Best Finish
Aoife Treeflame 1 10
JamieGawith Resident 3 8
Marousca Resident 4 7

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.

Skipper Best Finish Next Best Finish
KateyBeach Resident 6 11
juice651 Resident 8 9

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.

Skipper Best Finish Next Best Finish
Emileigh Starbrook 10 12
Diamant Siamendes 11 11

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.

Check Your L$ Balance Goes Live

On Second Life Mobile Alpha


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

How to Optimize PBR Era Firestorm

Many Second Life Merchants

Many Second Life Merchants Say the Virtual World Economy Seems Oligopolistic; How Should Linden Lab Intercede?

SL oligopoly 2024 survey

We should explore a key finding from my recent Patreon report, that nearly half the Second Life merchants surveyed believe the virtual world economy is dominated by oligopolies (see above). A solid plurality of merchants believe some SL brands have oligopolistic power over the virtual economy, while 37% are open to that possibility.

Anonymous comments by the surveyed merchants highlight their specific concerns:

There is a lot of gatekeeping in the SL creator’s world, especially when starting from zero. They limit too much the access to certain body devkits like [top brand A] or [top brand B] or to certain events so it is hard to grow as a creator when you are just starting with the brand, even if you have the knowledge or potential, it relies too much on followers rather than quality or original content.

All you have to do is look at the clothes market and how many bodies have come and gone and how much stuff is unusable without the outdated bodies. Folks have to keep up with what the body makers are doing, as well as making things fit multiple bodies, often with intentionally obfuscated devkits, it’s a mess.

Devkit gatekeeping is a huge hurdle to the health of the SL third party content creation ecosystem… you know what i’m talking about.

It’s so dependent on event companies, other creators, and ultimately… whether the audience has money to spend at all let alone log on, not just our work.

I think some of the negative trends occurring in the SL creator economy fall on the shoulders of choices made by other brands. The body brands really seriously impact how our market works, and the amount of brands and bodies and mods on the market has negatively affected the market in as many ways as it has positively. It’s turned customers at odds with creators more than ever.

Faced with growing oligopolies, real world governments tend to impose regulations or taxes on these powerful companies/coalitions, even breaking them up into smaller companies. As Second Life’s effective government, Linden Lab can’t exactly do anything like that.

I do see some potential in offering “carrots” that lessen the feeling of oligopoly power. Here’s three suggestions:

Publicize/highlight highly-optimized mesh body options. We’ve already written at length about how many (most?) of the top mesh bodies are way too triangle heavy. This creates an opportunity for Linden Lab to highlight — perhaps in a Top Optimized Body contest? — mesh bodies which are beautiful and streamlined to cause minimal lag. Good for the economy, good for the overall performance of the virtual world.

Hire a third party company to host shopping events on Linden land. The Linden-hosted events in-world tend to be highly non-profit, which is great; shopping events, however, would bring in a lot of fun traffic to the mainland. They could even be stretched out over many multiple sims to (somewhat) lessen lag. Trouble is, this would be difficult to pull off if it was managed by Linden Lab itself (drama, accusations of favoritism, etc.) So one solution is to hire a third party virtual world event studio — there’s many of these, doing events and marketing projects across many metaverse platforms — to pull it off. This would be a chance to present new brands as curated by people outside the main SL community.

Of course, the main way to lessen oligopoly is grow the economy, i.e. grow the active user base. With Second Life’s active shopping market so small — roughly 300,000 to 400,000 users are active shoppers — it’s inevitable that some brands will take on outsize power. An active user base that grows into the millions, however,  could create new markets and new niche categories.

No bad ideas in a brainstorm, like they say! What would you suggest, NWN reader?

 

Please support posts like these by buying Making a Metaverse That Matters and joining my Patreon!

Wagner James Au

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

New Updates!

New Updates Coming Soon For The Second Life Marketplace 2024/2025

Here are some new updates on what everyone can look forward to in the coming year for the Second Life Marketplace from the Second Life web team. See the whole meeting here which runs for 1 hour and 8 minutes. These new updates are from the monthly Second Life Web User Group meeting on 3rd July 2024.

First release of Second Life Marketplace being mobile responsive…

  • Mobile experience will display better pages like the product page for reviews etc
  • Expected within weeks and this roll out will be going slowly
  • A new confirm button when clearing your shopping cart is coming soon
  • MFA will be added to the Second Life Marketplace and this will be Opt in (the lab strongly recommends this). The plan is to add it on login
  • There will be more updates coming this year as well as the ones listed here

Other things on the Second Life Marketplace roadmap for this year…

  • Additional changes to Search on the Second Life Marketplace while working on MFA.
  • The lab will be working at how it changes transactions and merchant feedback on the feedback portal
  • After Search tweaks and MFA on Marketplace the lab will work on responsive marketplace for Search/Shopping Cart (likely to happen in 2025)

There is more discussion and related questions though the meeting (watch the video above). Below are some big updates that was said by the lab from SL21B…

  • The Marketplace design and UI will be updated real soon which will make it more accessible on smaller screens & in-viewer web browser
  • Marketplace integration roadmap with CasperVend is in the works now
  • Dark Mode on Second Life Marketplace – Not on the roadmap
  • And more!

Loads of improvements will be launching soon and some towards the end of 2024/early 2025. New experiences are coming soon which sounds really exciting.

Have a good week from all of us at Zoha Islands/Fruit Islands.