Posted by Bettina Tizzy
The members of the Not Possible IRL group held two meetings and shared many thoughtful notecards and IMs today expressly to discuss Rezzable's BuilderBot, and reach a consensus. The conclusions are as follows:
- The overwhelming majority of those who participated in today’s two meetings agree that Rezzable’s BuilderBot appears to be a useful – even important - tool for serious/professional creators and contractors.
- NPIRLers denounced the death threats expressed in comments on Rezzable’s blog and expressed concern about the sanity of the people posting them, as well as the safety of the Rezzable employees.
- We were reminded that Second Life residents have been asking for viewer-side back- up tools for years, and statements made by Philip Linden on April 16th during Rob Linden's Open Source Viewer office hours were recalled:
[14:30] Philip Linden: NOT ok to copy stuff otherwise.
[14:30] Philip Linden: And I'd say we'll act as much as possible to protect folks rights in that.
[14:32] Philip Linden: full perms doesn't mean off-grid, because the creators may well not have understood the implications.
- Members concurred that most content creators in Second Life are at little risk of having their creations ripped by BuilderBot, largely because it is much easier to use a CopyBot instead of devoting hours to ripping a sim, importing it to one’s OpenSim, and then using a CopyBot to put it back into Second Life.
- Numerous members noted that Linden Lab did not anticipate or think through many of the issues we are dealing with today and that Second Life sits on and is as vulnerable as any digital content is on the Internet. It was remarked that even before the viewer went Open Source, it was not too difficult to hack the cache. Moreover, content is moving off of Linden servers and “joining the cloud.” How ownership is handled in the cloud needs to be determined now and the solutions to these issues, within the context of Second Life’s current infrastructure, are legal, not technical.
- A number of members suggested that Rezzable should code in an ownership check, and that including a pay method and a license key associated with each copy of an item created by the tool might be a reasonable way to track copies. “If (Rezzable) could find a way, others will too, but at least they will have the legacy of doing the right thing.”