[sldev] P2P Web Textures now in demand to enable lossless image downloads to viewer

Dzonatas dzonatas at dzonux.net
Mon Jul 9 09:34:47 PDT 2007


Simon Nolan wrote:
>
> On Jul 9, 2007, at 10:38A, Tateru Nino wrote:
>
>> sldev at catznip.com wrote:
>
[...]
>>> * are there any legal issues? What happens if a texture is being 
>>> infringed
>>> upon and someone overzealous decides to subpoena everyone who is
>>> distributing the texture, or worse, if the textures are highly illegal
>>> pictures. The liability doesn't just have to be remote or 
>>> theoretical, it
>>> has to be non-existent since no one but LL can claim a common 
>>> carrier status
>>>
>> Whew. This has happened before - I believe the case is still in court
>> after nearly 8 years.
>
> Oh my! That could be very sticky, especially if my client peers with 
> someone in a country where certain content is illegal, but isn't here.
...
As the licenses and term of service currently are, there really is no 
reason to hold it up in court. What is uploaded to LL is sharable. That 
doesn't state that you can just use the shared textures in any 
publication, but being that a service that extends the original 
functionality of LL is not illegal. That type of extension in service 
has been done since day one of the Internet.


>
>>> * clueless on this one, but what happens to the low, medium and full 
>>> detail
>>> texture "streaming" we currently have? Torrents download pieces 
>>> randomly as
>>> far as I know.
>>>
>> It doesn't have to be torrent style, it can be straight HTTP or packeted
>> llsd or any other arbitrary entity encapsulation.
>
> I'm thinking torrent-style is seeming less and less like the best way 
> to share textures.
>
...
The overall idea is a bit more clear I hope. If it is easy as just an 
extra install for the squid setup and an extra button in SL's 
preferences to enable "reverse proxy," we'll see what we can do to keep 
it that simple. If you don't enable "reverse proxy" in the SL viewer (or 
likewise), then SLSquid would just act like a forward proxy... an extra 
cache... without all the other features spoken about.

These are still "would" type statements. I want a proof-of-concept and 
go from there.

-- 
Power to Change the Void


More information about the SLDev mailing list