Objects for which scripts are an inherent part of their appeal have a better chance. A standalone OpenSim running on your own hardware would have the same effect. So if you own a full, isolated sim, you could turn off all access and be assured that nobody will copy your work. I think your claim about the public sandbox being a likely site to get copybotted could well be true, but not because the land settings make it easier, but rather because it's a location where a lot of people go, some of whom may not be much inclined to follow the rules and have little to lose if caught.īecause the mechanism is strictly viewer-side - basically, if it's rezzed, it could already be copied - there's pretty much nothing that can be done to prevent it, short of preventing anybody seeing the build. I welcome comments, insights and opinions from other Residents about the copybot topic. I created this Cobybot thread because I don't know anything about copybots and I'd like to check the information I've claimed to be facts. In a recent thread, I listed copybots as one of the reasons why building in the public sandboxes is not a good idea. If it is possible to explain "how did they do that" without getting into the exact details, that would be helpful to me. If I'm working on a build in a public sandbox can a copy-botter steal a copy? How would I know if a Resident was using the method known as copybotting to copy one of my builds?Ĭan a Resident use the allowed Land abilities on an adjacent parcel (in Region or in an adjacent Region) to operate the mechanisms required to copy?Ĭan locking the item or editing the permissions for the next owner reduce the desireability of copying the object? The residual effects have yet to be seen, due to some organizing a boycott of buying and selling in Second Life due to Linden Lab's response of CopyBot, as well as some items being effectively leaked to freebie form.On a scale from 1-10, with 1 representing the least amount of risk, and 10 representing the greatest amount of risk how would you rate the likelihood that an object will be unlawfully copied?Ĭan the Land settings prevent or encourage a copybot?Īre high prim count objects at the same risk as low prim count objects? (40 prim vs.
#Second life copybot dmas code
In addition, LibSL had experienced a complete restructuring of command, with several people moving to only programmer status, as well as moving of the source code to a site which allows tigher control of distribution. Also, it has disbanded a member who was seen to be discussing the more nefarious uses of the bot. In response to the leak of CopyBot, LibSL has now restricted access to its developer code. Others criticized Linden Lab for their support of LibSL. LibSL had received severe criticism from residents for the lack of ethics some of the developers had, as well as lack of control they had over their source code. In reaction to the leak of a potentially devastating tool, several shops closed doors in protest. On November 14, 2006, CopyBot was leaked to the public without LibSL's approval. It did not have the ability to copy the contents of objects, including any scripts that may have been used. Under its more famous features, it had the ability to copy the prims it sees on someone's avatar, or an individual free-standing object. CopyBot is a project by Libsecondlife in an effort to provide a tool for the end user to back up and download/upload one's own creations.
0 kommentar(er)
