On 9 September 2013, stock content provider Renderosity followed the example of CGTextures and responded to LL’s recent ToS change by announcing that it prohibits use of its products in Second Life. This, of course, triggered yet another round of “LL IS TRYING TA STEAL MAH STUFFZ” drama, including various snarky comments from Renderosity users against Second Life users and content creators. In my original post on the ToS change, I have also quoted their announcement verbatim (in case they decide to rephrase or delete it). In that original post, I also quoted CGTextures’ announcement verbatim and commented on it, so for my thoughts on CGTextures’ announcements, this is what I’ll refer you to.
In this post, I’m going to focus on Renderosity’s announcement. As a reminder, you can find it on their website and here. What I wrote about CGTextures’ announcement holds in the case of Renderosity too. Determining how extensively a texture has been modified is not impossible at all. A .PSD (for Photoshop users) or .XCF (for GIMP users) file contains all the layers that were added to the original image, and it is really not impossible at all to determine if a whole texture or a small part of it has been used, or if it has been mixed with other images (either originally created by the user or bought from other sources and adapted to suit). However, this would need a thorough analysis, which could be costly to stock content provider that would want to take legal action against a customer that decided to use a texture of theirs in an SL build. This is something that holds true for both announcements.