[sldev] 3rd party viewer policy post on blogs.secondlife.com

[Domino Marama]

Avoiding making the ultimate copybot is one of the problems I face with
Primstar. With the Primstar scripts written in Python, any attempts at
content security with direct login options would be trivially bypassed.

So far I've just avoided the issue by not adding direct login support to
the scripts for either building or export to Blender despite how useful
they would be.

The only option I can see which would balance my needs as a "build only
viewer" developer and content security issues is if there was an
alternative login / api option which would only supply the content that
I was allowed to take offline for editing.

That way implementing content security in such a tool becomes trivial
rather than showstoppingly impossible. Bypassing the security would
become non-trivial as the core api calls would be different in the
server to client communications.