Jump to content

Disabling an experience


You are about to reply to a thread that has been inactive for 2518 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

  • Lindens

Let's say, hypothetically, you end up with a rogue contributor who makes a bunch of abusive scripts for your experience.  Is there any way to do damage control for something like that?  Or once those scripts are out are you doomed and you need to reset your experience?

Link to comment
Share on other sites

  • Lindens

Currently, the only action you can take is you disable the Experience (the setting is available on the profile editing page). This can be used for shutting down the Experience temporarily for damage control or other reasons, but there isn't any way to find or get rid of bad scripts after they are out there.

Link to comment
Share on other sites

Governance is capable of blacklisting any scripts.

Since experiences are compiled components of scripts, maybe SOP's could be revised to allow governance to honor requests from experience owners to blacklist a script in the rare event of abuse from third parties.

This would be favorable especially if the creator already has an entire product line devoted to the experience or a significant amount of user data assigned to the associated database or if the experience has quite a following of users as well.

Without this option, there would be no temporary damage control with the rare event of bugs, exploits or rouge contributors as the risk would always be present if the scripts were still available and/or active.

Link to comment
Share on other sites

A work-around for all cases other than a rogue contributor is to add a blacklist version check in the KV store: if the script finds its version number in the value of the blacklist it either shuts off, removes itself from inventory, deletes the object, or tries to update - whatever the application demands.

Link to comment
Share on other sites

  • 4 weeks later...

Correct - my solution was for all other cases than a rogue contributor - a rogue contributor can be solved by making sure you only add people you know you will be able to implicitly trust for the lifetime of the Experience.  But that's not a technological solution, only an interpersonal one.

A tech fix for a rogue contrib would require facilities for being able to blacklist Experience scripts created by a specific account.  To prevent accidents and further abuse, the given account would have to have been removed from the Experience.  However, the workaround for the rogue would be to have other, not as script savvy, members of the Experience copy & paste code into new scripts.  So the tech fix still requires an interpersonal fix. :P

Link to comment
Share on other sites

  • 2 months later...
You are about to reply to a thread that has been inactive for 2518 days.

Please take a moment to consider if this thread is worth bumping.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...