|
Malachi Petunia
Gentle Miscreant
Join date: 21 Sep 2003
Posts: 3,414
|
10-04-2007 12:06
When a discussion has reached the point of conflating texture theives and terrorists, all useful discourse has ended.
*locks*
|
|
Angle Thunders
Registered User
Join date: 16 Jun 2006
Posts: 30
|
10-04-2007 12:13
I will not argue the TOS as I just don't know with the other comments posted. This is what I get:
1: You do not own your own avatar.
2: You do not own the data uploaded to your account (that isn't yours anyway)
3: Anything you upoad you give SL, 3rd parties, and anyone using SL the right to use it anyway they see fit.
4: You do maintain the rights but it is irrelevant if you upload them to the SL servers.
Could be and probably are wrong but that is how I read it.
As far as GLIntercept I would think people would be happy to be able to back up their expensive skins and other textures being SL's databases seem to be having issues. As far as keeping that info from everyone I find that a little strange. People that are interested in ripping textures will find a way. All you are doing is keeping that info from people that could use the information for good. Like not wasting a lot of time and money on texture business or backing up textures they bought.
I was not aware of the UUID thing. That seems like something LL could fix in the server code.
Anyway back to work...
|
|
DanielFox Abernathy
Registered User
Join date: 20 Oct 2006
Posts: 212
|
10-04-2007 12:21
Angle, there's no 'fixing' it as its not a bug. Its the basic design of SL. llSetTexture() would have to somehow reverse-lookup the owner's corresponding inventory item for a texture UUID and check permissions on it before applying... thats not going to happen for a few reasons:
What do permissions really mean outside of the inventory system? Say I have your texture UUID and you think I shouldn't be able to put it on my own items for sale, but how do we make that work through permissions? Set it no modify? Well, i'm not modifying it. I'm just using it. Okay, set it no copy? Well i'm not 'copying it' because that again, only makes sense when you're talking about inventory items. So the only thing left is 'no transfer' ... but thats talking about transferral of ownership. The owner isn't changing... again, i'm just using it.
The only thing we could do is make llSetTexture() require an inventory name, like is done for rezzing objects. However, that would require every object that switches textures on a face to have all its textures in its own inventory. This is a large increase in asset load, and it wouldn't be backwards compatible with the gajillions of objects already out there using llSetTexture() with UUID's
-You can upload a texture without generating an inventory entry (SLImageUpload, libsl uploader), so what happens to these textures?
|
|
Darien Caldwell
Registered User
Join date: 12 Oct 2006
Posts: 3,127
|
10-04-2007 12:31
Considering Linden Lab paid someone to make a tutorial on how to use GLI to grab textures, I think its kind of naive to act like it's some taboo, forbidden thing. LL endorses it.
|
|
Void Singer
Int vSelf = Sing(void);
Join date: 24 Sep 2005
Posts: 6,973
|
10-04-2007 14:36
/me raises her hand... Imma good person... I'd still want those bomb plans.... because I love to know how things work... I wouldn't enjoy SL half as much if I didn't.... nor would I script, run my own server, run my own net radio.... etc ad nauseam.
on the flip side, I'd rather people that want to blow ME up didn't have them.... so I wouldn't make em easy to find... and I'd use personal judgment in handing them out
someone says " I wanna blow people up"
I say "good luck with that" (and then GTFOD)
someone says "I wanna make fireworks"
I say "Oh hey I have some info that might help"
it's not perfect, but it helps
so uhm... about those fireworks? =)
|