FLOSS community concerns about the Linden Lab policy on third-party viewers

From Second Life Wiki
Revision as of 12:02, 20 April 2010 by Gigs Taggart (talk | contribs) (removed some that are resolved)
Jump to navigation Jump to search


Note. Also see Linden Lab Official:Third Party Policy and Viewer Directory FAQ that was published after the TPV policy publication.

Preamble

"any Third-Party Viewer or any third-party software client that logs into our servers"

  • This could read as applicable to any software that has the capability to log into the service.
    • If this is the case, then people who have written clients years ago are suddenly and retroactively covered by this policy.
    • There is no way to create a client that is unable to log into Second Life and yet is compatible with OpenSim
    • Is a disclaimer that a client "should not be used with Linden Lab's service" enough to make someone not subject to this policy? Is a developer responsible for what their users do with the software?
    • This policy becoming "agreed to" by developers through the vicarious actions of end users is probably weaker than the weakest "browse wrap" agreement. There is no meeting of the minds... the developer may not even be aware this policy exists.

1 "Required Functionality and Disclosures" [1]

a

"compatible with the protocol of Linden Lab’s viewers as it is documented in our source code"

2 "Prohibited Features and Functionality" [2]

b

"You must not use or provide any functionality that Linden Lab’s viewers do not have for exporting content from Second Life unless the functionality verifies that the content to be exported was created by the Second Life user who is using the Third-Party Viewer. [...]" This must be done for all content in Second Life, including content that may be set to “full permissions.”"

  • This is one of the most objectionable requirements.
    • Megaprims are all created by other people, so you can't export them
    • Invisiprims, same deal
    • Automated building assistants which use their own primitives. (There are quite a few of these.)
    • Can't collaborate with someone on a project and then export it to other grids, since it will fail the creator check
    • Can't build on an alt and then export it on your main... less of an issue since you can export on the alt but still very annoying.
    • Can't use textures uploaded on alt when building on main, and vice versa.
    • Effectively bans all export, since it's impossible to check the creator of textures, which are referenced only by UUID.
  • Probably effectively bans all CC-SA-By licensed content, since such content forbids the imposition of restrictions on the right to redistribute the content.


8 "Policy Changes, Enforcement, and Termination" [3]

c

"You acknowledge and agree that we may require you to stop using or distributing a Third-Party Viewer for accessing Second Life if we determine that there is a violation."

  • How is this reconciled with the new clause that this doesn't limit the rights under the GPL?

d

"If we believe that your Third-Party Viewer is not in compliance, we may request that you add, modify, or remove features, functionality, code or content, and you agree to comply with the request within a reasonable timeframe specified by Linden Lab."

  • No developer is going to allow Linden Lab the power to assign them development work that must be completed in a certain timeframe. That's a basically unlimited liability for the developer.

9 "Definitions" [4]

c

"By “Third-Party Viewer,” we mean any third-party software client on any device that logs into our servers that support Second Life. Third-Party Viewers include software for viewing Second Life, any chat clients, utilities, bots, and proxies as well as applications that may not be listed in our Viewer Directory."

  • This goes back to the preamble. Apparently just creating software compatible with Second Life makes you liable for this agreement/policy. Keep in mind that the Second Life protocol has been submitted to standards bodies for standardization. The only way to opt-out of this agreement seems to be to somehow break compatibility with the Second Life service.
  • The policy never defines what "third-party software" means. Presumably, "third-party" refers to a person or entity who is neither Linden Lab nor the person who must agree to the policy. So, does "third-party software" it mean software distributed by such an entity? Or is it software created by such an entity? (In which case, both the official SL viewer and Snowglobe would be third-party software, because parts of them were created by non-LL contributors.) Or does it mean something else? This ambiguity needs to be resolved; no one can be certain that they are complying with the policy, if they aren't sure what software the policy applies to.
    • Update: Joe Linden has said in IRC that it means "not released by Linden Lab".
Retrieved from "https://wiki.secondlife.com/w/index.php?title=FLOSS_community_concerns_about_the_Linden_Lab_policy_on_third-party_viewers&oldid=871963"