Dynamically Updatable Landmarks
tracked
Sterling Ronzoni
It doesn't take long in SL for 1 type of inventory item to grow in quantity beyond any other. And, not much longer than that for the majority of them to become utterly obsolete. I'm referring to Landmarks.
To address the ongoing growth of obsolete Landmarks all across all of our inventories, I propose the idea of dynamically re-pointable landmarks.
The following are the basic rules for how it would work:
- Every user would have 6 separate personal LM entries that they can add to their viewer, numbered 1 to 6.
- A user can enter any SLURL into any of the 6 positions, and any Landmarks created by that user that he associates with one of his/her 6 entry positions will cause those LMs and copies of them to always lead to that corresponding SURL entry.
- At any time, the creator can update or change any of his 6 SLURL entries in his viewer, and all previously provided associated Landmarks and all copies will auto-redirect to the new corresponding latest entry based on the creator's current SURL entry for the same entry position in his viewer list.
- This same LM system should also function within MP listings, for those sellers who want to allow customers to view their product outside the MP, in their in-grid store.
Log In

Spidey Linden
Merged in a post:
📌 Experience-Linked Smart Landmarks
Bambi Bubbles
Users in SL have LONG lamented the issue of landmarks dying when a store, club, or other favored destination relocates. Landmarks die if a region is moved on the map as well. MANY Jiras and Feedbacks have been posted over the past ~23 years, asking for some way for destination owners to edit downstream landmarks.
I have an idea.. Leverage Experience Tools.
This suggestion is to create a sharable inventory asset, that acts like a landmark, but pulls it's data from an experience key.
Let's start with some basic idea of how this asset might be set up.
* On creation, the asset is full permissions for the creator.
* Next owner permissions are pre-set to ✅ Copy ❌ Modify ✅ Transfer.
* The Next Owner ❌ Modify is greyed out, and unable to be changed.
On double-clicking:
* If the current owner has modify permission, a UI floater is displayed, allowing the user to set the experience, specify the 'lookup' field for this landmark, and potentially a password field. It will also have a field that allows for viewing the current value in that field ( if the password is needed, only if it is correct)
* If the asset owner does NOT have modify permission, the owner is immediately teleported to the destination.
In terms of scripts:
* The asset should appear (for LSL purposes) to BE a "INVENTORY_LANDMARK".
* If a script is 'reading' the asset like a landmark using https://wiki.secondlife.com/wiki/LlTeleportAgent or any similar function, it should read the destination value and attempt to use it as expected.
In all other ways it should act like a landmark, allowing sharing, etc. Perhaps an exception can be made allowing the placing of this no-modify asset into a notecard, as landmarks are OFTEN shared as notecard attachments.
--------------------
If the permissions thing can't be done, perhaps a secondary approach to this is simply that ONLY the 'creator' of a smart-landmark asset, can edit it's experience data, password, destination, etc.. and that information would simply not be presented to "owner != creator" asset owners.. allowing the asset to otherwise work exactly like every other landmark for every user, except it's creator.
The existing UI for "Landmark Properties" has lots of space for expansion related to experiences, and could serve as the basis for the interface for this new asset.
The existing "About Landmark" UI even has some "Edit" functionality already in place. Though I'll be honest, I have no idea what "Landmark Location" means on this dialog.
UI for changing the destination of a parcel's "Landing Point" or changing the destination of a "Pick" or a "Classified" already exist, and perhaps the UI design language and behind-the-scenes mechanics for these functions can be mined for a consistent user interface.
-------------------
Perhaps a warning notice should appear when editing this new Experience Landmark .
"Note: Editing this will edit all copies of this experience landmark that have been shared. If you would like to create a new Experience Landmark using this one as a template, click here: Create a New Experience Landmark".
I'm sure someone else can figure out better phrasing.
Photo Viewer
View photos in a modal
AlettaMondragon Resident
Wouldn't this cause the same "problem" some people have with calling cards? Of course if the landmark points to a public place it wouldn't matter, but let's say someone gives one of these experience-driven landmarks to a friend, to find their home even if they move, or to their current partner (a lot of people move very often in SL). Then this friend or partner becomes their worst enemy two months later (sadly this happens too often) and they have the perfect tracking tool as long as the creator of the landmark doesn't change it, I suppose by redoing the experience or linking the new location to a new "smart landmark". How exactly would the linking / location tracking be done and how exactly could it be terminated when needed?
Bambi Bubbles
AlettaMondragon Resident
I mean, this is why we have banlists on land. Just because someone knows where your land is, doesn't mean you have to let them in.
Deleting the key that the landmark was linked to, would result in the landmarks that had been previously distributed not finding a destination in the lookup. "Unable to find destination"
Alternatively the creator could change it's destination, sending everyone with that old landmark to an 'I've moved" skybox, with a 'click for new landmark' button, or a script that automatically offered a replacement landmark to anyone who arrived on the "I've moved" parcel.
The scripts and banlists could be set not to allow certain problem people to enter, or not give the landmarks to those people..
Of course nothing stops someone using an alt to get the new landmark... but if we're looking for SUPER SUPER PERFECT PRIVACY the answer is always "don't own land in SL", as it is relatively simply to deploy a bot to visit every region in SL, index every parcel's land owner, and 'find' the new home in a matter of days.
If someone is facing this level of harassment, this is a matter that Trust and Safety should be addressing, not the architectural solutions of a 'slightly less decrepit landmark'
AlettaMondragon Resident
Bambi Bubbles Sure, because the so-called Trust and Satety does such a great job. No, the problem is simply that if certain safeguards are not implemented, or poorly, or the users won't know how to use them (similarly to not knowing how to keep their land safe), you just give abusive people a new tool that they can use against others. Besides, updating a landmark manually can't be so difficult. Then people would still just lose or misplace their landmarks. Interestingly the groups where I see the "can I have the LM?" question the most are those stores that have been at the same place for many years and the region name is the store name. Added bonus when the location is also in the group description.
These "smart landmarks" are not a bad idea, but they won't substitute reading and thinking, so I'm not sure it would be a very useful feature in practice.
Bambi Bubbles
AlettaMondragon Resident
Why would you think that any proposed feature request would be intended to 'substitute reading and thinking?'
This was simply intended to allow a store, club, or other venue, to have a type of landmark that they could use (assuming they have a paid account or experience editing rights), that could have it's destination updated as part of a move... allowing customers, fans, etc to 'follow them' even if they used a pre-move smart landmark.
This edge case about stalking is kind of out of left field.. and not really relevant to the feature as I've described it.
The land owner creates the 'smart landmark', points it to their experience, and a certain data field in that experience. Should the store/club/land location 'move', they land owner can choose to update the field that all those smart-LMs are referencing... and update 'all the old smart-LMs that people already have' so they keep working.
If someone doesn't WANT to do that because reasons.. they have the option to decomission the LMs by deleting the field in the experience data, or if there's a bad apple out there that follows them to their new location, there are existing tools for banning and blocking residents..
This doesn't make traditional landmarks use this system, it augments them with a second 'smart landmark' that creates a new option for those who want to deploy them.
AlettaMondragon Resident
Bambi Bubbles Some of us are just more security-oriented than others, so we look for possible risks in everything. Here I'm just asking you about safeguards for possible issues because you didn't include them in the suggestion. I think I understand the concept of your smart landmark idea, except maybe the part that if it's not entirely hands-free for the landmark creator / experience owner to maintain this, I wonder why it would be more convenient than simply putting the new location's SLURL in the group description, their profile, Discord, etc.

SL Feedback
Hello, and thank you for your feature request regarding dynamically updatable landmarks. This idea was actually brought up in the past and is documented in our previous bug tracking system under issue number BUG-229673. We are merging your comments with the existing issue to help us address it more efficiently. While we don't have an estimate on when this feature might be implemented, please keep an eye on future updates. We appreciate your input and hope you continue to share your ideas to help improve Second Life. Thank you!

SL Feedback
updated the status to
tracked