Web/Marketplace Features

Description: Currently, when searching for products on the Second Life Marketplace, results often include numerous gacha items. While gachas were once popular, many users now prefer to purchase items directly without the randomness or resale nature associated with gachas. This can make finding non-gacha products time-consuming and frustrating. Proposed Feature: Introduce a simple filter or checkbox in the Marketplace search interface labeled “Exclude Gacha Items”. When enabled, this filter would remove all listings tagged as gacha from the search results. Benefits: Improved User Experience: Users can quickly find items they want without sifting through unwanted gacha listings. Efficiency: Reduces search clutter and saves time for shoppers. Marketplace Transparency: Helps buyers make informed choices by distinguishing between standard items and gacha resales. Community Alignment: Reflects the evolving preferences of Second Life residents who increasingly favor direct purchases over chance-based systems. Why It Matters: The Marketplace is a critical hub for Second Life commerce. Enhancing its usability with targeted filters ensures a better shopping experience, supports creators who sell non-gacha items, and aligns with Linden Lab’s efforts to maintain a fair and accessible economy. Would you like me to make this more formal and structured for submission to Linden Lab’s Jira system, or turn it into a persuasive email you can send to their support or product team? Or both? Provide your feedback on BizChatYou said: Make it suitable for Jira submissionCopilot said: CopilotHere’s a Jira-ready version of your feature request: Summary: Add an option to exclude gacha items from Marketplace search results. Description: When searching for products on the Second Life Marketplace, results often include numerous gacha items. Many users prefer to purchase items directly without the randomness or resale nature associated with gachas, making it difficult to find non-gacha products efficiently. Proposed Solution: Add a filter or checkbox in the Marketplace search interface labeled “Exclude Gacha Items”. When selected, this filter would remove all listings tagged as gacha from search results. Benefits: Improved User Experience: Easier and faster to find desired items without unwanted gacha clutter. Efficiency: Reduces time spent scrolling through irrelevant listings. Marketplace Transparency: Helps buyers distinguish between standard items and gacha resales. Community Alignment: Reflects current user preferences for direct purchases over chance-based systems. Impact: This feature would enhance usability, support creators selling non-gacha items, and align with Linden Lab’s commitment to a fair and accessible economy. Would you like me to also include acceptance criteria and example UI mockup descriptions to make it even stronger for Jira? Or keep it as a concise feature request? Provide your feedback on BizChatYou said: Include UI mockup descriptionCopilot said: CopilotHere’s the Jira-ready version with a UI mockup description included: Summary: Add an option to exclude gacha items from Marketplace search results. Description: When searching for products on the Second Life Marketplace, results often include numerous gacha items. Many users prefer to purchase items directly without the randomness or resale nature associated with gachas, making it difficult to find non-gacha products efficiently. Proposed Solution: Add a filter or checkbox in the Marketplace search interface labeled “Exclude Gacha Items”. When selected, this filter would remove all listings tagged as gacha from search results. UI Mockup Description: Location: Place the new filter in the left sidebar under “Search Filters”, alongside existing options like “Price Range” and “Permissions.” Element Type: A checkbox labeled: Exclude Gacha Items Behavior: When checked, the search query dynamically updates to exclude all listings tagged as gacha. When unchecked, search results remain unchanged. Visual Example: [ ] Exclude Gacha Items Positioned under other filters for easy access. Benefits: Improved User Experience: Easier and faster to find desired items without unwanted gacha clutter. Efficiency: Reduces time spent scrolling through irrelevant listings. Marketplace Transparency: Helps buyers distinguish between standard items and gacha resales. Community Alignment: Reflects current user preferences for direct purchases over chance-based systems. Impact: This feature would enhance usability, support creators selling non-gacha items, and align with Linden Lab’s commitment to a fair and accessible economy.

I hardly need to mention that there's a lot of feelings about ai-generated content, and LL has already heard quite a lot of feedback about it from residents. I'd like to suggest a thing we can do about it! Let me first admit that no solution is perfect and that an AI-using-creator could compile, train, and operate AI indpendently without the tech I mention below. But, the 99% use-case is that people generate content using ready-made solutions, and an enormous number of these ai-generating business have committed to a measure of transparency and accountability that I want to mention. If a person generates AI content--marketplace images, for example--using Midjourney, OpenAI (chatGPT), NanoBanana (Google Gemini), Firefly (Adobe), Runaway AI... or any of the myriad next-tier platforms implementing stable diffusion 3, then ALL of these tools automatically embed a content credential into the work. Cropping, resizing, or trivial modifications to the work do not alter the credential. Only significant human-made alterations to the content of the image result in the credential being changed. The presense of a content credential does not, I should note, mean "made with AI". It means "there's a content credential here." It's important because all major genAI tools do generate a credential that describes the origin of the work as a GenAI tool. The content credential carries a modification history with it. This means that even the creator of an original, handmade work could embed a Credential, and if their work was taken and modified by AI, then the credential would list out both versions. Again, all major genAI tools use this. The credentials are already there today. The credentials are not a value judgement, and they are not an ethical judgement. They are already within the ai-generated content, and they help us see what was done with a piece of content. The customer/end user makes the value judgement for themselves. LL has seen that customers want to know. The information is already within the file. The platform just needs to expose that information. A simple "CR" tag (using the established logo made with the c2pa standard) on the corner of any image on the marketplace, with a hover-tip to explain the content credential would go a long way. Further, adding a property for texture assets generated for use within SL itself would be a nice next-step (but less trivial to implement). For more info about the industry-wide standard C2PA (Coalition for Content Protection and Authenticity): https://c2pa.org/ The specification is avaialble here: https://spec.c2pa.org/specifications/specifications/2.1/specs/C2PA_Specification.html This isn't a fun, easy feature but it feels like an important feature.

For Members who are Premium Plus, offer the ability for them to change to a previously used/owned/purchased last name for free. If you buy a last name, as you own it forever, you should be able to switch into one of your already purchased last names whenever you'd like to (perhaps cap it at a 48 hours cool down period per switch). Just a thought!

EEP are a important part of the SL experience now. Could we get a category for them under Home and Garden or some other place? Right now they are all over the place and more difficult to find than they should or need be.

"Product is great! Love it! 3 stars only for now until you fit it for x body." "This is amazing! No x head fit though so 1 star :/" "Will add 5 stars when HUD has this niche complex script added to it." Please. Allow us creators to report reviews that are used as REQUEST forms for extra features. I don't feel like reuploading my entire 2$ product just to fit this obscure body that was specifically not listed on the product description. All of this can be resolved with a separate review report category dedicated to this issue.

I stopped paying for Land via Land Use fees, because out of four months Tilla only succeeded once, putting my account in arrears three times. Since switching to the more expensive route of paying for land by alt subscriptions Tilla has failed to process one of the subscription payments. Failure with Tilla is becoming so regular that LL needs to have a clear policy on accounts that Tilla's failures push into arrears. Currently neither the Billing Knowledge Base article, nor LL Billing Policies address this very frustrating issue. Policy details needed include how long will accounts be allowed in arrears before an account is placed on hold and land is sold or we are billed for land usage that was within the tier allowance. Also whether you will start emailing us to tell us that the payment has not been taken. And remedial action for payment failures that were not the user's fault.

Please add a required bool while creating a Marketplace listing that asks the creator to disclose if AI generative tools were used in part/all of the products creation. Add this bool to the 'Do Not Show' section of the Marketplace search filter. Allow listings to be reported if they do not honestly disclose this. ---- For the health of the market we need the use of AI tools to be disclosed by creators. I would prefer personally that no AI generation be supported. I understand that tolorance of it is an effort to avoid censorships slippery slope, and is complicated by the sheer variation of AI tools that currently exist. But regardless of opinions or complications, it's existance cannot be ignored. So lets focus on what can be done, by giving some power of choice to the consumer instead. Users should be provided a way to choose products with or without AI generation while shopping, and naturally creators who choose not to disclose or to lie should face the same reportability and moderation as any other creator that would choose to lie while listing. The moderation half of this should not necessarily focus on trying to prove the use of AI gen tools, it doesn't actually need to. Creators who have done the work to provide support and actually prepare the AI generated content for its use in SL are unlikely to warrent being reported, and should not need to lie about the useage anyway. It is products that blatantly lack support, have egregious LOD & LI values that would be inclined to lie, and would want to be reported by users, this is the same for ANY product currently listed. If you buy it, and you don't get what was described, it should be reportable, the same goes for AI generated products, AI generated should not get a pass because you have to 'prove' something first, when the fact remains that you didn't get what thought you bought. So do not focus on "did you use a tool?" focus on "can you fix & support the product?" If it can't be supported, then disclose it was made via AI generation and move on. This is a similar complication to full perm and gacha resales, but also ripped models, copybot etc, in they will all lack support due to not being made directly by the creator of the listing. There is a big difference between fullperm & gacha resale vs ripping & botting, and that difference is honest disclosure.

It has been nearly a year since this feature was 'completed', and there's still no documentation for how to use it. PRIM_COLLISION_SOUND has a value of 53. It was added, and marked as "COMPLETE" on January 17, 2025 It is not represented on https://wiki.secondlife.com/wiki/LlSetPrimitiveParams , and the constants tables are not editable by wiki contributors. See: https://feedback.secondlife.com/scripting-features/p/add-prim-collision-sound-function-to-llsetlinkprimitiveparams-suite

I've wasted so much time trying to feed an occasional scripting bug report into Canny. (Please see https://community.secondlife.com/forums/topic/528921-why-does-canny-plague-me-so/ for some background.) At the very least, we need to know which fields are public and which private, so we know enough to put everything in the public field(s) that would be needed for anybody to understand what the bug is about. Also, we kinda need to know whether all Lindens who work with Canny can see all the private fields; I hope so, but I'm not confident they actually can. Also, every time I've tried to edit an issue after it is submitted, I've gotten the "Uh oh… try again later" message, so if that just doesn't work, please get somebody to remove Edit so submitters don't waste time with that and go straight to adding a comment instead. If there's some way it does work, please add a hint for that, too. I realize actual user documentation is unrewarding to write because it mostly goes unread, but for a feature that (mis)behaves so unintuitively, we at least need such hints.

Each year Second Life Residents support numerous charities, and have close relationships with those charities. I would like to see the information/banners/hyperlinks of those charities on the official Second Life website, so not only can residents new and old know that they are supported by various means, but allow them to click through to learn more and possibly donate outside of Second Life. This could also be a quid pro quo situation where those charities also promote Second Life. My experience with Wigs for Kids and Hair Fair is that they are very on board promoting all we do to support them and promote us on their website each year and social media during our event. I would like this to become an all thing with all the events that do that kind of thing and their Charities, it could bring in a lot of new users.